“I was watching session recordings for our sign-up page and realized a lot of people were trying to click something that wasn’t actually a button. We wouldn’t have noticed that needed fixing without PostHog’s session recordings.”
Instant realtime GraphQL APIs
Anubhuti MishraUI/UX Designer, Hasura
Play back sessions to diagnose UI issues, improve support and get inspired.
Understand why and how users get stuck
Debug faster, or build context on user stories. Nothing beats watching people use your product for real.
Quickly filter for important moments
Filter recordings for users who completed a specific event, or zoom in on errors, rageclicks and more.
Block sensitive data, even from PostHog
Avoid recording private data simply by adding a CSS class to elements and fields you don't want to capture.
How do PostHog Session Recordings compare?
Swipe right to compare.
Hotjar | Logrocket | Matomo | PostHog | |
Platform | ||||
Free plan | ||||
Open source | ||||
Cloud hosting | ||||
Product analytics | ||||
Session Recording | ||||
Single-page app support | ||||
Mobile app recordings | ||||
Identity detection | ||||
Target recordings by URL | ||||
Target by sample size | ||||
Filter recordings by user or event | ||||
Rage-click detection | ||||
Privacy masking for sensitive content | ||||
Export recordings | ||||
Retention policy for recordings | 1 year | 1 month | 24 months | PostHog Cloud: 3 weeks Self-hosted: No limit |
Session recording documentation
- Using Session Recording
- Ignoring sensitive elements
- Recording configurations
- Console logs recording (beta)
- Further controls
- Recordings data retention
- PostHog Cloud & Clickhouse Self-hosted
- Legacy Postgres Self-hosted
- Preserving recordings
- Troubleshooting
- My browser freezes / crashes when recordings are enabled
- Recordings are not being captured
- Permitted domain setting
- posthog-js configurations
- Content security policy
- Ad/tracking blockers
- Website is not recording properly
- Update posthog-js
- Report your specific issue