from posthog import Posthog import json
You can export individual recordings to a JSON file via the "more options" menu in the recording viewer. These files contain the serialized DOM snapshots (using rrweb ) and can be re-imported into PostHog for playback later.
The Guide to PostHog Session Replay Portable: Self-Hosting and Offline Capture posthog session replay portable
Because this entire pipeline runs on your infrastructure, the recording data is inherently portable and under your control. Benefits of Using Portable Session Replay Description Sensitive user data (PII) stays within your VPC. Data Retention You decide how long to keep recordings, not a SaaS plan. Disconnected Environments Operates on internal networks without internet access. Custom Auditing Store recordings alongside internal log systems. How to Set Up Portable (Self-Hosted) Replay
Understanding how data flows through PostHog will help you grasp the full extent of your portability options. from posthog import Posthog import json You can
Open source (and self-hosted) session replay tools - PostHog
1. The Localized Docker Compose Deployment (True Offline Self-Hosting) To watch the sessions
Using the PostHog API , you can automatically attach session replay links to support tickets in platforms like Intercom, Zendesk, or Crisp. This makes the "user experience" portable, bringing the context directly to your support engineers. 3. Self-Hosting for Total Data Sovereignty
Enter . This approach leverages PostHog’s powerful open-source capabilities to create a flexible, self-contained, or highly adaptable session recording pipeline.
GDPR Article 17 ("Right to Erasure") requires you to delete user data upon request.
To watch the sessions, you import these JSON files into a custom local HTML page running rrweb-player , or build an ingestion script that uploads them to a central PostHog instance later using the PostHog Capture API. Step-by-Step: Setting Up a Portable Local Ingestion Buffer
