Quick answer
PostHog documents monthly recordings as 5,000 recordings per month. Replay is metered separately from product analytics events.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| monthly recordingsReplay is metered separately from product analytics events. | 5,000 recordings per month | Cloud free tier | PostHogAug 22, 2026 |
Why does this limit matter?
Recording every low-value session can exhaust replay capacity independently of analytics events.
This value is scoped to Cloud free tier; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Review replay sampling, retention needs, and monthly recordings by environment.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Sampling and privacy configuration should be designed before cost optimization.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related