Posthog Session: Replay Portable [verified]

Mutations, clicks, keypresses, mouse activity. Console Logs & Network Requests.

This portability relies on (record and replay the web), an open-source framework utilized by PostHog to collect JSON "snapshot data". Instead of capturing traditional, heavy video files like MP4s, the SDK records DOM changes, mouse tracking, console logs, and network metadata. posthog session replay portable

: Users can preserve specific recordings by selecting Export to JSON . This creates a portable data file that can be stored in external repositories or uploaded back into PostHog later, ensuring that critical bug reproductions are not lost when standard retention periods expire. Mutations, clicks, keypresses, mouse activity

When you watch a replay, the frontend player first queries ClickHouse to get the list of recordings. When you click play, the API retrieves the compressed snapshot data from the blob store, which the browser's JavaScript engine decompresses and plays back [12†L23-L25]. Instead of capturing traditional, heavy video files like

This proxy intercepts the incoming /e/ (events) and /s/ (session recording) endpoints from posthog-js .

Your user behavioral data shouldn't be an island. With portable data, session replays can be fed into your own data lakehouse alongside your transactional databases, CRM entries, and support tickets. PostHog's CDP (Customer Data Platform) facilitates this through batch exports that support scheduled, compressed exports in JSON, CSV, or Parquet formats to destinations like Snowflake, BigQuery, or Amazon S3 [17†L9-L17]. This allows you to combine replay metadata with long-term business KPIs in your BI tool of choice.