> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/reports-and-debugging/recordings.md).

# Recordings

Every run is recorded end to end — a full-motion replay of UI actions, transitions and responses, downloadable per test attempt.

|                   |                                                                           |
| ----------------- | ------------------------------------------------------------------------- |
| **Platforms**     | Android · iOS                                                             |
| **Recorded**      | Every run, automatically. Nothing to enable                               |
| **Download from** | The **Actions** section of a test attempt                                 |
| **Also there**    | Screenshots and execution logs                                            |
| **Watch out**     | Secure screens render black in the recording. The OS blocks capture there |

## Prerequisites

* A completed run, local or cloud
* The specific test attempt you want artifacts for — each attempt has its own set

## Download the artifacts

1. Open the run.
2. Open the test attempt.
3. Open the **Actions** section.
4. Download the recording, the screenshots or the execution logs.
5. Confirm the downloaded file opens. Report links are signed and time-limited; the downloaded file is not.

| Artifact           | Contents                                                       |
| ------------------ | -------------------------------------------------------------- |
| **Recording**      | The full run, replayable frame by frame                        |
| **Screenshots**    | The before and after images for every step                     |
| **Execution logs** | Timestamped, step by step, with what Drizz decided at each one |

Each test attempt has its own set. A test that ran three times in a plan has three recordings.

## What a recording shows that a screenshot cannot

<table data-search="false"><thead><tr><th>Case</th><th>Detail</th></tr></thead><tbody><tr><td><strong>Transient UI</strong></td><td>A toast, error banner or loader that appeared and went between screenshots</td></tr><tr><td><strong>Animation and timing</strong></td><td>A screen still settling when the step ran</td></tr><tr><td><strong>Unexpected navigation</strong></td><td>A tap that opened something and closed it again</td></tr><tr><td><strong>Failures that don't reproduce locally</strong></td><td>Diagnose from the recording rather than rebuilding the scenario</td></tr><tr><td><strong>Shared evidence</strong></td><td>QA, engineering and product review the same footage</td></tr><tr><td><strong>Audit trail</strong></td><td>A verifiable artifact of exactly what ran</td></tr><tr><td><strong>Secure screens</strong></td><td>Rendered black. The OS blocks capture there</td></tr></tbody></table>

{% hint style="success" %}
Read the report first, recording second. The before-screenshot of the first failing step resolves most failures on its own — see [When a step fails](/reports-and-debugging/when-a-step-fails.md).
{% endhint %}

## Retention

Report links are **signed and time-limited**, and so is access to the artifacts behind them. A recording that is evidence for a bug report or a release decision has to be downloaded and attached as a file.

## Common mistakes

| What you do                                          | What happens                                                       |
| ---------------------------------------------------- | ------------------------------------------------------------------ |
| Link a recording in a ticket instead of attaching it | The link expires and the ticket loses its evidence                 |
| Open the recording before reading the report         | You watch four minutes of video to find what one screenshot showed |
| Report a black section as a broken recording         | Secure screens block capture. Nothing was recorded to lose         |
| Download from the plan rather than the attempt       | Artifacts are per test attempt. A re-run has its own set           |

## Next

* [Reading a report](/reports-and-debugging/reading-a-report.md)
* [When a step fails](/reports-and-debugging/when-a-step-fails.md)
* [Troubleshooting](/reports-and-debugging/troubleshooting.md)

***

*Last updated: 6 August 2026*