Skip to content
DocsGitHub

replay

Search and inspect Session Replays

List recent Session Replays

Arguments:

Argument Description
[<org/project>] <org>/ (all projects), <org>/<project>, or <project> (search)

Options:

Option Description
-n, --limit <limit> Number of replays (1-1000) (default: "25")
-q, --query <query> Search query (Sentry replay search syntax)
-e, --environment <environment>... Filter by environment (repeatable, comma-separated)
-s, --sort <sort> Sort by: date, oldest, duration, errors, activity, or a raw replay sort field (default: "date")
-t, --period <period> Time range: "7d", "2024-01-01..2024-02-01", ">=2024-01-01" (default: "7d")
-f, --fresh Bypass cache, re-detect projects, and fetch fresh data
-c, --cursor <cursor> Navigate pages: "next", "prev", "first" (or raw cursor string)

Examples:

Terminal window
# List recent replays (project auto-detected)
sentry replay list
# List recent replays for a project
sentry replay list my-org/frontend
# Search across all projects in an organization
sentry replay list my-org/ --query "environment:production"
# Change the time window and sort
sentry replay list my-org/frontend --period 24h --sort errors
# Find replays for a user
sentry replay list my-org/frontend -q "user.email:foo@example.com"
# Filter by environments
sentry replay list my-org/frontend -e production -e canary
# Show more results
sentry replay list my-org/frontend --limit 50
# Fetch the next page
sentry replay list my-org/frontend -c next
# Fetch the previous page
sentry replay list my-org/frontend -c prev
# Output as JSON
sentry replay list my-org/frontend --json
# Find a project across organizations
sentry replay list frontend

View a Session Replay

Arguments:

Argument Description
<replay-id-or-url...> [<org>/<project>] <replay-id or trace-id> or <replay-url>

Options:

Option Description
-w, --web Open in browser
-f, --fresh Bypass cache, re-detect projects, and fetch fresh data

Examples:

Terminal window
# View a replay by ID (organization and project auto-detected)
sentry replay view 346789a703f6454384f1de473b8b9fcc
# View a replay in an explicit organization
sentry replay view my-org/346789a703f6454384f1de473b8b9fcc
# View a replay with explicit org/project context
sentry replay view my-org/frontend/346789a703f6454384f1de473b8b9fcc
# View a replay from its URL
sentry replay view https://sentry.io/organizations/my-org/explore/replays/346789a703f6454384f1de473b8b9fcc/
# View the replay linked to a trace
sentry replay view my-org/frontend/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
# Open a replay in the browser
sentry replay view my-org/346789a703f6454384f1de473b8b9fcc --web

sentry replay download <replay-id-or-url...>

Section titled “sentry replay download <replay-id-or-url...>”

Download a Session Replay as rrweb JSON

Arguments:

Argument Description
<replay-id-or-url...> [<org>/<project>] <replay-id or trace-id> or <replay-url>

Options:

Option Description
-o, --output <output> Output path (default: .rrweb.json in the current directory)
-f, --fresh Bypass cache, re-detect projects, and fetch fresh data

Examples:

Terminal window
# Download a replay as rrweb JSON to ./<replay-id>.rrweb.json
sentry replay download my-org/346789a703f6454384f1de473b8b9fcc
# Choose where the file goes
sentry replay download my-org/346789a703f6454384f1de473b8b9fcc --output ./replay.json
# Download from a replay URL
sentry replay download https://sentry.io/organizations/my-org/explore/replays/346789a703f6454384f1de473b8b9fcc/

All commands support --json for machine-readable output and --fields to select specific JSON fields.

sentry replay download writes a flat, time-ordered array of rrweb events, ready for rrweb-player or rrvideo. Sentry's custom events (breadcrumbs, performance spans) are kept.