Session Replay
Contents
Session replay records what real users do in your product and plays it back like a DVR, with a synced DevTools panel showing console logs, network requests, and errors at the exact moment they happened. Because PostHog already captures your events, every replay is enriched with the person, their properties, and the feature flags they had, so you can jump from a funnel drop-off or an exception straight to the session behind it.
You can watch replays yourself, ask PostHog AI to find and summarize them, or pull them into your editor over MCP.
Where you can use it
You watch, filter, and share replays in the PostHog web app. The other surfaces let you investigate sessions and act on them without leaving your existing tools.
PostHog Web
Watch recordings with synced DevTools, build collections, and share them with your team.
Watch replays →Where its data comes from
Session replay runs on recordings captured by your PostHog SDKs. What ends up in a replay depends on how you configure capture: which sessions you record, what the browser panels collect, and what you mask before it ever leaves the device.
Recording rules
Sample, gate by URL or feature flag, and record only the sessions worth keeping.
Set recording rules →Console and network
Capture console logs and the network waterfall so the DevTools panel has something to show.
Capture performance data →Privacy and retention
Mask text, inputs, and whole elements before capture, and control how long replays are kept.
Configure privacy →