---
id: 3f8a2c1d-7e4b-4d9f-a6b3-2c5e8f1d4a7b
blueprint: session-replay
title: "Session Replay Viewer"
this_article_will_help_you:
  - "Resize panels in the expanded replay viewer to suit your workflow"
  - "Inspect network requests during a session replay with the DevTools Network tab"
landing: false
exclude_from_sitemap: false
updated_at: 1777248000
---

The Session Replay viewer lets you watch replays with full context alongside an event timeline and developer tools. Product managers and analysts use it to understand user behavior and identify UX friction, while developers use it to correlate user actions with network activity and console errors during debugging.

## Resizable panels

The expanded viewer opens when you select the expand icon on any replay. It contains three panels you can resize to fit your workflow:

- The video player
- The events timeline
- The side panel

To resize a panel, drag the divider between any two panels. The panels adjust to the position you set.

Amplitude saves your panel sizes to your browser's local storage. The next time you open the viewer, the panels reopen at the widths you set. To return panels to their default sizes, select **Reset panel sizes** in the toolbar.

## DevTools Network tab

The *DevTools* section of the Session Replay viewer includes a **Network** tab. The Network tab displays network requests captured during the replay, giving you visibility into what the user's browser requested and how those requests resolved.

Each network request entry shows:

- URL
- HTTP method
- Status code
- Response time

Select a row to open a detail panel with four tabs:

- **Headers**: Shows the request URL, HTTP method, status code, and any captured request and response headers.
- **Payload**: Shows the captured request body. This tab appears only when you configure a `requestBody` capture rule in your SDK settings.
- **Response**: Shows the captured response body. This tab appears only when you configure a `responseBody` capture rule in your SDK settings.
- **Timing**: Shows when the request started relative to the replay and how long it took, with a waterfall visualization.

To capture request and response bodies, configure `requestBody` and `responseBody` capture rules in your `networkTracking` SDK configuration. For setup instructions, go to [Track network requests](/docs/sdks/analytics/browser/browser-sdk-2#track-network-requests).

Use the Network tab to correlate user actions with API calls or identify failed requests that contributed to a broken experience. For example, if a user encountered an error during checkout, you can check the Network tab to see whether a payment API call returned a non-200 status code at that moment in the replay.

### Network tab and the Console tab

The **Network** tab works alongside the **Console** tab, which shows JavaScript console logs captured during the replay. Together, these tabs give you a complete picture of client-side behavior during a replay.

To capture console logs, go to [Session Replay settings](/docs/session-replay/session-replay-settings) and enable console tracking.