No. 23 of 30 ยท Heatmaps and session replay
LogRocket
Session replay with the console, the network log and the Redux state attached.
It replays the session next to the JavaScript errors and network requests that happened during it, which is why engineers rather than marketers buy it.
The verdict
LogRocket is session replay aimed squarely at the engineer who has just been handed a bug report that says the button did not work. Alongside the recording it captures console output, network requests and responses, and application state, so instead of trying to reproduce the fault you watch it happen with the stack trace beside it. For a front-end team that is a genuinely different tool from Hotjar, despite the surface similarity.
It has grown outwards into product analytics and frustration detection, but the engineering context remains the reason to choose it and the thing nothing else here does as well.
What you actually get
The free tier of 1,000 sessions a month is small, enough to evaluate but not to run on, and paid tiers start around $69 a month and scale by session volume. That puts it above the marketing-focused tools and well above free, which is defensible given the audience: it is priced as a developer tool rather than a marketing one.
The privacy position needs care and the reason is specific to what it captures. Recording network requests and application state means recording whatever those contained, which on an authenticated application is very often personal data, tokens or both. LogRocket documents privacy controls and they work, but they are opt-in configuration on a tool whose default value proposition is capturing more rather than less. On a public marketing site that is a manageable risk. On a logged-in product handling customer records it is a review item, not a checkbox.
Best for
Front-end and full-stack engineering teams debugging real user problems in production, who need the network log and the application state as much as the video.
Getting it running
An npm package and an initialisation call, with framework integrations for React, Redux, Vue and the rest. Configuring privacy controls is the part that needs deliberate attention on any authenticated app.
What to watch out for
The free tier at 1,000 sessions a month is an evaluation allowance, not a usable one. It captures network payloads and app state, so privacy configuration is a real task with a real failure mode. Heavy script. Cookies and consent obligations apply.
Pricing and practicalities
Free at 1,000 sessions a month, with paid tiers from roughly $69 a month scaling by session volume and retention. EU data residency options are available. Prices read 2026-09-11.
Who should go elsewhere
Marketing teams who want to know why a landing page underperforms, who will be better served by Hotjar or Microsoft Clarity at a fraction of the cost. Also not for sites where a consent banner is unacceptable, where the in-browser masking of Absolutely Analytics is the different bargain.
How it compares
Against FullStory the split is audience: FullStory indexes sessions for analysts, LogRocket instruments them for engineers. Against PostHog, which bundles replay with everything else, the question is whether the engineering context is worth a separate subscription.
The ten measures
Each measure is scored 0 to 10 and weighted. The overall figure is the weighted mean, and it is relative to the other 29 tools on this list rather than absolute. How this works.
What this rests on
LogRocket's own pricing and product pages and its documentation on privacy controls, network capture and framework integrations, read 2026-09-11.
Desk research against published pricing and documentation. The privacy characterisation follows from what the vendor documents it captures by default; I have not audited a live implementation.
This is a desk review. I have not been given access by the vendor, I have no commercial relationship with them, and everything above is my opinion rather than a statement of fact. If something here is wrong, tell me and I will correct it.