# Run recordings and sharing them

Watch what the browser actually did, and hand somebody a link to it without giving them an account.

> **Plan:** available on the Basic plan and above.

Screenshots tell you what the page looked like at each step. A recording tells you what happened between them. When a failure is caused by an animation, a toast that appeared and vanished, or a race between two requests, the recording is usually the only artifact that shows it.

![A run detail page, from which a recording is watched and a share link is generated.](https://testsnag.com/images/docs/running-tests/reading-run-results-1-passed-run.r2.jpg)

Marked on the screenshot:
- Open the run whose recording you want.
- Watch recording lives in the three-dot menu, alongside Share recording.
- Run details, including the session the recording belongs to.
- Line the recording up against the step you are investigating.

## Watching one

Open a run, then choose Watch recording from the three-dot menu next to Rerun. It plays inline on the [run detail page](https://testsnag.com/docs/running-tests/reading-run-results.md), beside the steps, so you can line up what you are watching with the step that failed.

## Web and mobile record differently

A web run streams its recording from the browser session, so it is available as soon as the run finishes and plays like a live stream. A mobile run records the device screen to a video file instead, which is stored with the run and played back from there. You watch both the same way, and the difference only shows up in how quickly a very long run becomes available.

> **Note:** A mobile recording starts before the app does, so its first few seconds are the device booting and the app launching. Playback skips that automatically and opens on the first frame of your app, which is why the timeline does not begin at zero.

## Sharing a link

Generate a share link for a recording and anyone with the URL can watch it without signing in. That is the point: it lets you send a failure to a developer, a designer, or a customer-facing colleague who has no Testsnag account, without describing the bug in prose.

> **Warning:** A share link is public to anyone holding it, and a recording shows whatever was on screen, including anything typed into a form. Revoke the link when you are done, and never share a recording of a run that used real customer data.

## Revoking

Revoking invalidates the URL immediately. Generating a new one issues a fresh link, so an accidentally forwarded link is easy to kill.