On this page

Debug Statsig Session Replay

Use Statsig Session Replay to debug user-reported issues by replaying real sessions alongside console logs, network requests, and feature gate values.

Large session recording warning

In the Console, you may encounter the warning:

"This session recording is too large to load."

This occurs when a session exceeds 50 MB in size. Once Statsig records a session at this size, the console can't display it, and you can't fix it retroactively. If you consistently see this warning, here are a few steps you can take to reduce session sizes going forward:

  1. Disable Inline Stylesheets
    When initializing the SessionReplayClient, set inlineStylesheet to false. Statsig generally recommends keeping inlineStylesheet set to true, because it ensures recordings accurately reflect your original CSS even if you later update your styles. However, this setting often causes sessions to grow very large and is the most common source of bloat.
jsx
runStatsigSessionReplay(client, {
  inlineStylesheet: false,
});
  1. Exclude Large Static Elements
    If certain elements on your page are large but static (for example, background images or videos), you can exclude them from session capture by adding the rr-block class to their className. This prevents Statsig from recording those elements and can significantly reduce session size.

  2. Reach Out for Assistance
    If you continue to experience large sessions, contact the team in Slack Community. A Statsig team member can review your session and provide recommendations for your setup.

Was this helpful?