Skip to Content

      Portable !link! - Posthog Session Replay

      start(userId?: string): void if (this.isRecording) return;

      If your application is portable (like a laptop out in the field) but eventually reconnects to the internet, you can use an edge proxy to cache recordings locally.

      What are you planning to run this portable setup in (e.g., Docker, an offline desktop app, a local server)?

      At its heart, portable session replay is about agency. It rests on three key principles, each of which PostHog addresses head-on. posthog session replay portable

      Run PostHog on your own servers or VPC, meaning your data never leaves your infrastructure.

      private handlePromiseError = (event: PromiseRejectionEvent): void => this.addEvent('promise_error', reason: String(event.reason), stack: event.reason?.stack, ); ;

      If your needs outgrow PostHog in the future, you don't have to start from zero. Because you have the raw JSON exports in your own S3 bucket, you can write a custom importer for your new analytics tool. Your historical session data remains an asset, not a hostage. start(userId

      In the era of privacy-first analytics and strict data sovereignty, relying on third-party SaaS tools to store sensitive user session recordings is becoming a liability. Enter the concept of —a paradigm shift where session replay data isn’t just accessible, but truly owned, transferable, and portable by the user.

      By making your session replay data portable, you're not just archiving; you're enabling richer, more contextual analysis. PostHog's design encourages this by weaving its products together. You can jump from a insight directly into a playlist of session replays for the users who dropped off. Or, you can filter recordings based on which feature flag variant a user was exposed to, providing direct video evidence of an experiment's impact.

      While PostHog's portability is powerful, it's important to acknowledge its current limitations. The most significant is the lack of a built-in mechanism for . While manual and API-driven methods exist, the platform does not offer a one-click solution for archiving all your recordings. Additionally, you cannot directly export a session recording as a standard MP4 video file; the data is stored as JSON and must be played back within PostHog or a compatible player. It rests on three key principles, each of

      If you embed replays into a CRM or support tool, ensure only authorized personnel have access to those pages.

      There are two main ways to achieve portability:

      Disclaimer: Feature availability and pricing for competitors are accurate as of the publication date. Always verify current vendor terms regarding data export.