Sharing or embedding replays

Last updated:

|Edit this page

Replays are typically viewed in Session Replay part of PostHog. However, you may want to share specific recordings with people outside of your PostHog organization. You can share them directly using a URL, or embed them in a webpage using an iframe:

Above is an embedded recording of… on – very meta.

How to share session replays

Method one: Sharing via the PostHog app

When viewing any recording, press Share. You can then configure the recording for external sharing. There are also configuration options for the iframe, as well as the ability to specify whether it should start at a particular timestamp.

Method two: Sharing via the PostHog API

Using the PostHog API, you can automate the sharing of replays. For example, a common use case is to include a session replay in a support ticket whenever a user reports a bug.

Here is how to use the API to share replays:

  1. In your frontend, retrieve the session_id of the replay you want to share. Then, upload that session_id to your backend
// Frontend - where the recording is taking place
const sessionID = posthog.get_session_id()
// Upload this sessionID to your backend
  1. Once you have the session_id in your backend, you can enable sharing for that recording using the API to create an access token.
// Node.JS backend example
const projectID = 123 // Found in [Project Settings](
const sessionID = '{FROM_STEP_1}'
const url = `${projectID}/session_recordings/${sessionID}/sharing?personal_api_key=${POSTHOG_PERSONAL_API_KEY}`
const response = await fetch(url, {
method: 'PATCH',
body: JSON.stringify({
enabled: true,
headers: {
'Content-type': 'application/json;',
}).then((res) => res.json())
// You can also retrieve the access token again by calling the same endpoint
// const response = await fetch(url).then((res) => res.json())
const accessToken = response.accessToken
  1. You can now share the replaying using the access token and an iframe:


  1. We make no guarantees about sensitive information contained in the recording. We recommend you only sharing recordings that you are certain contain no sensitive information or embed them only where authorized users can see them.
  2. Events will not be shown in the shared iframe, as they are loaded from a separate endpoint that is not accessible from the embedded iframe.
  3. If your replays look incorrect or buggy, be sure to read our troubleshooting docs on how to debug this.


Was this page useful?

Next article

Replay data retention

Depending on how your app or website is built, recordings can take a lot of disk space. To manage this, we have the following retention policy options in place. PostHog Cloud Recordings are automatically deleted after 1 month ( 3 months for paid customers). The deletion is not immediate meaning that recordings may still appear for a short time in the UI after the retention period expires or when manually deleted via the UI. Preserving recordings Pinned or Shared recordings are kept for as…

Read next article