Microsoft Clarity Is Free — Here's What That Buys You in Session Replay

Microsoft Clarity gives you session replay, heatmaps, and frustration signals for free, with no session caps that matter for most sites. That’s not a trial or a loss leader with a paywall behind it — as of mid-2026 it’s simply free, and for what it does, it’s good. The catch is what it does: Clarity’s session replay is built for understanding user behavior, not for debugging your application, and the gap between those two jobs is wider than the feature lists suggest.

I recommend Clarity regularly. I also keep something else installed next to it. Here’s the reasoning on both halves.

What Clarity does well

The recordings are easy to skim, the heatmaps are legitimately useful for layout decisions, and the frustration detection — rage clicks, dead clicks, excessive scrolling — surfaces sessions worth watching without anyone filing a ticket. For a marketing site or an early-stage product where the questions are “where do people get confused?” and “does anyone scroll past the fold?”, it answers them at a price of zero.

Setup is a snippet. There’s a decent Google Analytics integration. The privacy controls mask text by default, which is a safer default than some paid tools ship with.

If that’s your whole problem, stop reading and go install it.

Where an engineer hits the wall

The wall shows up the first time you try to use a Clarity recording to fix a bug rather than observe behavior.

No console output. The user clicked the button, nothing happened, and you’re watching it happen in the replay — but the JavaScript error that explains it lives in a console Clarity doesn’t record. You can see the symptom on a loop. The cause isn’t in the recording.

No network visibility. Was the API call slow? Did it return a 500? Did it fire at all? A behavior-focused tool doesn’t capture requests, so the most common class of production bug — the backend said no and the frontend didn’t handle it — is invisible.

No error correlation. There’s no way to start from “show me every session where this exception fired” because exceptions aren’t part of the data model. You browse sessions the way Clarity organizes them: by page, by frustration signal, by segment. That’s the right organization for UX research and the wrong one for triage.

Sampling and retention are outside your control. Clarity makes its own decisions about what to keep and for how long. For watching aggregate behavior, fine. For “a customer reported this specific thing on Tuesday,” you need the specific session from Tuesday, and you need to find it by who the user was — which is exactly the lookup a replay link in the bug ticket depends on.

None of these are flaws, exactly. Clarity was built by an analytics team for analytics questions. Expecting it to debug is like complaining that your dashcam doesn’t show the engine temperature.

The two-tool setup that actually works

The pattern I’ve settled on for small SaaS teams: Clarity for the marketing site and top-of-funnel pages, where the questions are behavioral and the traffic is high. A developer-focused replay tool on the app itself — behind the login — where sessions are fewer, users are identified, and every recording might need to answer “what exactly broke?”

Developer-side tools capture the console, the network requests with status codes, and the errors, all pinned to the same timeline as the DOM recording. That’s the difference in one sentence: Clarity shows you what the user did; a debugging replay shows you what the app did back. LogReplay is one option in that category (it’s ours — evaluate accordingly, and there are others); the free tier covers a small app’s session volume, which keeps the two-tool setup at a total cost of zero until you grow.

The one thing I’d caution against is running two recorders on the same pages. Each one hooks DOM mutation observation, and while a single well-behaved recorder is cheap, stacking them on a mutation-heavy app is how you end up investigating your own instrumentation. Split by property, not by page.

The honest summary

Clarity’s free session replay is the best zero-dollar UX research tool available right now, and Microsoft shows no sign of changing that. Use it for the questions it was built for. Just don’t let “we already have session replay” end the conversation when your team is debugging production — the recordings look similar, but the data underneath is a different product.