Usero Journal
Session Replay Tool: How to Pick the Right One (2026)
Before you pick a session replay tool, answer one question: what do you actually need to watch? The answer splits the whole category, and picking wrong means paying for a research platform when all you wanted was to see one bug.
A session replay tool reconstructs what a user did in your web app, capturing the DOM and events on the client and replaying them as a timeline in a dashboard. (If that mechanism is new to you, here is what session replay is and how it works.) Almost every tool on the market does that part competently. They are built on the same open-source engine, rrweb, more often than the marketing admits. Where they differ is what they wrap around the recording, and that is the part that should decide your choice.
Most teams skip the question and reach for whatever name they have heard, usually FullStory or Hotjar, and end up either overpaying for analytics they never open or scrubbing through hours of recordings to find the thirty seconds they cared about. The tool is fine. It was the wrong tool for the job they actually had.
The question that picks the tool for you
There are really only three jobs people hire a session replay tool to do, and each one points at a different product.
- Broad research and funnel analysis. You want to watch many sessions, slice them by segment, find where a funnel leaks, study how a cohort behaves. This is the digital-experience-analytics job, and it wants a heavyweight: FullStory, or PostHog if you also want analytics and flags in the same place.
- Debugging with engineering context. You want the console errors, the network waterfall, and the Redux or state tree sitting next to the timeline, so a Sentry alert becomes a replay in two clicks. That is LogRocket's lane.
- Triaging the specific bug a user just reported. You do not want to watch arbitrary sessions. You want the thirty seconds before one person hit submit on a complaint that says “the export button does nothing.” This is the narrowest job, and a general replay tool is the wrong shape for it, because the recording lives in one product and the report lives in another.
The first two jobs are well served by the big tools and you should buy one. The third job is where most small teams actually live day to day, and it is the one the category serves worst. A dedicated replay tool records everything and leaves you to find the relevant moment yourself, matching a feedback ticket in one tab to a recording in another by timestamp. That is manual archaeology, and it is the reason replay tools get installed, used hard for a week, and then ignored.
A session replay tool that records everything makes you the search engine. The useful version hands you the one recording that matches the report you are looking at.
Session Replay Tools Compared
Starting prices are monthly USD, checked early 2026. Replay is usually bundled with analytics, error tracking, or feedback, so a straight price comparison is rough. Confirm on each vendor site, these change.
| Tool | Starts at | Free tier | Wrapped around replay | The job it fits |
|---|---|---|---|---|
| FullStory | Custom (enterprise) | No | Experience analytics | Broad research at scale |
| LogRocket | $99 | 1k sessions/mo | Error tracking, perf | Engineering debug loop |
| PostHog | $0, then usage | 5k recordings/mo | Analytics, flags (open source) | Product engineers |
| Hotjar | $32 | Yes (35 sessions/day) | Heatmaps, surveys | Marketing and growth |
| Microsoft Clarity | $0 | Yes (unlimited) | Heatmaps | Free baseline coverage |
| Usero | $0, paid from $19 | Yes (real) | Feedback widget, AI PR | Replay tied to the bug report |
The tools worth shortlisting
FullStory
custom (enterprise)The research heavyweight
The category leader for breadth. Retroactive search across every session, sophisticated frustration signals, deep funnel work. If you have a research or CX function whose job is to study behavior at scale, this is built for them.
Pricing is quote-based and the platform is overkill below a few hundred thousand monthly sessions. A two-person team that gets told to “just use FullStory” should decline.
Mid-market and enterprise teams that want digital-experience analytics, not just recordings.
LogRocket
from $99/moThe debugging pick
LogRocket sits closer to Sentry than to Hotjar. The viewer puts console errors, network requests, and state changes alongside the timeline, so the loop from “error fired” to “here is where in the journey” collapses to one screen.
Heavier SDK and pricier than the analytics-leaning options. Worth it for an engineer-heavy team, less so for marketing.
Engineering teams that want replay sitting next to errors, network calls, and app state.
PostHog
free, then usage-basedThe open-source value pick
PostHog bundles replay into a wider analytics suite, is open source, and is self-hostable end to end. The free tier (around 5,000 recordings a month) is real, and pricing scales with usage rather than seats. If “open source session replay” is your search, this is usually the answer with a product around it.
The viewer is good rather than best in class. The trade is breadth and price against the polish of FullStory or LogRocket.
Product engineers who want analytics, flags, experiments, and replay in one self-hostable stack.
Hotjar and Microsoft Clarity
from $32/mo, and freeThe marketing and free-baseline options
Hotjar leads with heatmaps and surveys and treats replay as a companion feature. A small marketing team can run it without an engineer, and the free tier (35 sessions a day) is enough to evaluate.
Microsoft Clarity does heatmaps and recordings for free with no session cap, which makes it the obvious zero-cost baseline. Neither surfaces engineer-grade console or network detail the way LogRocket does.
Marketing and growth teams, or anyone who wants free coverage before paying for anything.
Usero
free, paid from $19/moReplay tied to the bug report
The tool I work on, so weigh that. Usero records the session in the user’s browser, with or without its feedback widget on the page, built on rrweb like most of this list. The difference is what it wraps around the recording: when someone submits feedback, the report deep-links to the exact moment in the replay where they hit submit. The complaint and the recording arrive in the same view, so you stop matching them by timestamp.
The unusual bit is what happens after. That recording becomes context the AI reads when it opens a draft GitHub pull request from the report, so the loop runs from feedback to a diff, not from feedback to a backlog row. The PR opens as a draft. You review it and merge it yourself, nothing auto-merges.
This is narrower than FullStory or LogRocket on purpose. If you need to watch arbitrary sessions from arbitrary users for research, pick one of those. If you want every bug report to arrive with the recording attached, this is the cheapest way there.
Small teams whose real use for replay is “watch what the user did right before they reported the problem.”
When you do not need one at all
The honest answer for some teams is to skip the purchase. A session replay tool earns its keep when you have enough traffic for the recordings to be representative and a real question they answer. Below that, it is dead weight you will stop opening.
- Under 1,000 monthly active users. The volume is too low to spot patterns. DM ten users and watch them work over a call for an hour. You will learn more than a month of replays gives you.
- A static marketing site. Heatmaps and scroll depth from Microsoft Clarity, which is free, cover most of the value at a fraction of the setup.
- Regulated data and no time to configure masking. Replay is one of the strictest categories under GDPR and HIPAA. If you cannot spend an afternoon masking sensitive fields and auditing the result, do not turn it on yet.
If the third job is yours
If you nodded at job three, watching the bug a user just reported rather than studying behavior at scale, that is the case Usero is built for. Replay is on the free tier. Drop the widget into a React app in three lines, or start recording with no widget at all via @usero/sdk/replay, and the next bug report you get will arrive with the recording of the exact path the user took. Spin up a workspace and see what your real bug reports look like with replay attached. The session replay feature page covers how it feeds the PR step, and the setup docs cover install and masking.
Related reading
- What Is Session Replay? (And How It Works)Read
- Best User Feedback Tools (2026 Comparison)Read
- Stop Building a Feedback PortalRead
- AI Code Fixer: From Bug Report to Pull RequestRead
Frequently Asked Questions
What is the best session replay tool?
There is no single best one, because the category splits by what you need replay for. For full digital-experience analytics at scale, FullStory leads. For replay glued to error tracking, LogRocket. For product analytics with replay bundled in, PostHog, which is also the open-source pick. For heatmaps plus lightweight recording, Hotjar or Microsoft Clarity (Clarity is free). If your real use case is watching what a user did right before they reported a bug, a feedback tool with replay attached like Usero is cheaper and lands the recording next to the report.
How much does a session replay tool cost?
It ranges widely as of early 2026. Microsoft Clarity is free. PostHog is free up to about 5,000 recordings a month then usage-based. Hotjar starts around 32 dollars a month. LogRocket starts around 99 dollars a month. FullStory is enterprise and quotes per company. Usero has a real free tier with replay included and paid plans from 19 dollars a month for the workspace. Confirm current pricing on each vendor site before you commit, these move.
Is there a free session replay tool?
Yes. Microsoft Clarity is fully free with unlimited recordings and heatmaps. PostHog has a free tier of roughly 5,000 recordings a month. Usero includes replay on its free tier. The trade-off with the free options is usually data retention, sampling caps, or a narrower feature set, so read the limits before you standardize on one.
Is there an open source session replay tool?
The recording engine most tools build on, rrweb, is open source, and you can self-host it. PostHog is open source and self-hostable end to end, which is the usual answer when someone wants open-source replay with a real product around it. Usero is built on rrweb and its widget SDK is open source on npm, though the backend that stores and replays sessions is hosted.
Do I need a dedicated session replay tool if I already have a feedback widget?
It depends on the gap you are trying to close. A dedicated tool lets you watch arbitrary sessions from arbitrary users, which is what you want for funnel analysis and broad UX research. If your only real need is seeing what a user did right before they hit the feedback button, a separate replay product is more than you need and leaves you stitching the recording to the report by timestamp. A feedback tool that records the session and links each report to the exact moment of submission closes that gap directly.
Will a session replay tool slow down my site?
A well-built recorder adds roughly 30 to 80 KB gzipped and uses about 1 to 3 percent CPU during active sessions, with uploads batched and throttled. On modern devices the impact is usually invisible. On low-end mobile or pages with very heavy DOM churn, sample a fraction of sessions instead of recording all of them.
Continue reading
Feedback API: Collect Feedback From Any Platform With One HTTP POST
A feedback API lets you collect feedback from Swift, Python, a server, or a CLI without a JavaScript widget. How a good feedback REST API works, with copy-paste curl, Swift, and Python examples, plus how reports cluster and can become a GitHub PR.
7 min read
User Testing Tool: How to Pick One (and When You Do Not Need One)
A user testing tool records a real person using your product. Two questions pick the right one: do you need a moderator on the call, and do you need a recruited panel? Compare UserTesting, Maze, Lookback, Useberry, and Usero, with honest pricing and a when-to-skip-it.
8 min read
How to Import GitHub Issues Into a Feedback Tool (and Why)
GitHub issues pile up and never dedupe. Import them into a feedback tool that clusters by meaning across every source, counts what recurs, and can open a GitHub PR you review and merge. A practical guide.
7 min read
Build a feedback loop your team actually uses
Usero collects, clusters, and turns user feedback into shipped fixes.
Get started free