Clairvio vs. Hotjar: Which Session Replay Tool Is Right for Your Team?

Hotjar is probably the most recognised name in session recording for smaller SaaS products. If you've looked at session replay tools at all, you've encountered it. Clairvio is a newer, narrower tool built around a fundamentally different model — and a fundamentally different use case.

This comparison is honest about both. The tools overlap in that they both record browser sessions. Beyond that, they're solving different problems for different people — and conflating them leads to choosing the wrong tool for your actual workflow.

The Core Difference: Who You're Recording For

Hotjar is a UX research and feedback platform. Session recording is one feature inside a broader product that includes heatmaps, clickmaps, scroll maps, form analytics, and user surveys. Its primary audience is product managers, UX designers, and marketers trying to understand how visitors interact with pages in aggregate — where they click, how far they scroll, where they drop off in forms. The core question Hotjar answers is: what do users do on my site?

Clairvio is an on-demand diagnostic tool. There are no heatmaps, no surveys, no form analytics. Its primary audience is support and engineering teams trying to reproduce and diagnose specific customer-reported bugs. A customer reports a problem, your team sends them a magic link, they activate it with one click, and you get a full technical replay of exactly what happened — DOM mutations, console output, network requests, JavaScript errors and stack traces. The core question Clairvio answers is: what went wrong for this specific user?

These are different questions asked by different people at different points in the product lifecycle. Hotjar is a proactive research tool. Clairvio is a reactive debugging tool. The right choice depends almost entirely on which of those descriptions matches your team's actual workflow.

Feature Comparison

What Hotjar Captures vs. What Clairvio Captures

Both tools record browser sessions, but the depth of what they capture is categorically different — and that difference matters enormously if you're trying to debug a technical problem.

Hotjar's session recording captures mouse movements, clicks, and scrolls. You can watch a video of what a user did on the page. For UX research — understanding whether users see a CTA, how far they scroll before leaving, where they hesitate — this is exactly what you need. But Hotjar does not capture console output, network requests, or JavaScript errors. If a user encounters a silent failure (a 401 from your API, an unhandled promise rejection, a race condition in your state management), Hotjar's replay will show you the user clicking and waiting, and then leaving. It won't show you why.

Clairvio captures the full technical state of the session. Alongside the DOM replay, you get the console log timeline (including console.error, console.warn, and uncaught exceptions), the full network request log with status codes, response times, and payloads, and JavaScript errors with stack traces. This is the difference between watching someone struggle and actually understanding what the application was doing when they did.

The trade-off is deliberate. Hotjar captures everything shallowly, across every session. Clairvio captures one session deeply, on demand. Neither approach is better in the abstract — they serve different workflows.

Performance and Privacy Impact

Hotjar's tracking script is typically 50–100 kB and loads on every page for every user. Because it's recording continuously — building heatmap data, capturing session videos, running survey triggers — it maintains active connections throughout the session. Hotjar has put effort into async loading and deferral, but it is a real third-party script with real overhead, and it appears in Lighthouse third-party audits.

Clairvio's loader is under 1 kB and is completely inert until a magic link is activated. For the overwhelming majority of your users — everyone who isn't in an active support session — there is zero capture overhead, zero additional network traffic, and no impact on your Core Web Vitals or Lighthouse scores. The capture library is only loaded when the session begins.

Privacy is the other dimension worth addressing directly. Hotjar's always-on model has faced regulatory scrutiny in Europe — several EU data protection authorities have raised concerns about Hotjar's data transfers under GDPR, and Hotjar has had to invest significantly in consent mode, user suppression, and data residency features in response. This is the structural consequence of recording every session by default: you're processing behavioural data from every visitor, most of whom will never interact with your team.

Clairvio's per-session consent is simpler by design. When a user clicks a magic link, they are explicitly opting into having their session captured and shared with your support team. There is no passive collection, no cookie requirement for recording, and no need to suppress users who haven't consented. For a deeper treatment of this, see our guide to privacy-first session recording.

Pricing

Hotjar structures pricing around daily session limits on its Observe product. The free Observe Basic plan caps at 35 sessions per day. The Plus plan ($32/month) allows 100 sessions/day. Business ($171/month) allows 500 sessions/day with additional filtering and segmentation. Scale and Enterprise pricing requires a sales conversation. If you're on a high-traffic site and want to capture a meaningful percentage of sessions, the daily caps become the binding constraint quickly — and Hotjar's session count scales directly with your traffic, not your support volume.

Clairvio offers a free tier (25 sessions/month) and paid plans from $9/month (Starter) to $99/month (Scale, 5,000 sessions/month). Because recording is on-demand, your session consumption is tied to how many support cases you open, not how many users visit your site. A high-traffic product with a small support team pays very little; the cost scales with the workflow you're actually using.

Where Hotjar Is Genuinely Stronger

Hotjar has real strengths that Clairvio doesn't replicate and isn't trying to.

Heatmaps, clickmaps, and scroll maps. These are Hotjar's flagship features and they're genuinely good. If you want to understand where users click on a page in aggregate, how far they scroll before leaving, or which elements draw visual attention — Hotjar is purpose-built for this. Clairvio captures nothing in aggregate.

User feedback and surveys. Hotjar's feedback widgets and survey tools let you collect qualitative feedback from users while they're in the moment. This is valuable for UX research and product discovery. Clairvio has no equivalent.

Form analytics. Hotjar tracks field-level drop-off in forms — which fields cause hesitation, where users abandon. For conversion rate optimisation, this is a meaningful capability.

Broad UX research ecosystem. If your team is doing structured UX research — running tests, gathering feedback, optimising conversion funnels — Hotjar's integrated platform is a natural fit. Clairvio is not a UX research tool.

The free tier for UX research. 35 sessions/day on the free plan is enough for many small product teams to get meaningful heatmap and scroll data without spending anything.

Where Clairvio Is Genuinely Stronger

For support and debugging workflows specifically, the on-demand model has advantages Hotjar's architecture can't match.

Technical depth. Console logs, network requests, JavaScript errors, and stack traces alongside the DOM replay — this is what engineering teams need to actually diagnose a bug. Hotjar's session recordings are useful for UX but insufficient for debugging. Watching a replay of a user clicking into a broken state without seeing the 500 error from your API or the uncaught exception in the console doesn't tell you what to fix.

The magic link workflow. Hotjar has no equivalent to Clairvio's magic link model. With Hotjar, you can only review sessions that were already passively recorded — within your daily session limit. With Clairvio, the recording is triggered in response to the specific support case, so you're guaranteed to capture the exact reproduction attempt. If a user reports a bug and Hotjar had hit its session cap, or the session wasn't sampled, it's gone. With Clairvio, you send a link and capture it deliberately. We cover this workflow in detail in our guide to debugging without screen sharing.

Zero performance overhead for normal users. A dormant loader under 1 kB is categorically different from a 50–100 kB always-on capture script in terms of its effect on page performance. For teams with Lighthouse budgets or Core Web Vitals targets, this matters.

Predictable pricing at support scale. Session consumption tied to support volume — not site traffic — makes costs predictable and proportionate to the workflow you're actually using.

Which Teams Should Choose Each

The Honest Summary

Hotjar is a UX research platform. Session recording is one feature inside a product designed to help product, UX, and marketing teams understand how users interact with their site in aggregate. If that's what you need, Hotjar is a mature, capable tool with a generous free tier and a proven track record.

Clairvio is a debugging tool. It is built for the specific moment when a customer reports a bug and your team needs to see exactly what happened in their browser — including the technical signals that Hotjar doesn't capture. The on-demand recording model means zero overhead for normal users, a simpler privacy posture, and pricing that scales with your support workflow rather than your traffic.

If you're a support engineer or engineering team evaluating tools for debugging and customer escalations, Hotjar isn't the right comparison point — it was built for a different job. If you're a product or UX team that wants heatmaps and aggregate session data, Clairvio isn't the right tool either. The overlap is real but narrow; the use cases are genuinely distinct.