# Record your Flow

Maestro allows you to generate high-quality screen recordings of your tests without needing third-party software. The `record` command programmatically stitches the app screen and Flow output into a professional MP4, making it easy to debug failures or showcase features.

<figure><img src="https://639424640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmS3lsb9jRwfRHqddeRXG%2Fuploads%2FbahM8E7MQyhbg9xSQ2PU%2Fimage.png?alt=media&#x26;token=768c6cde-1f4a-420d-98a2-c9d5e69bb7ef" alt=""><figcaption></figcaption></figure>

### Why record your Flows?

* **Debugging**: Visually identify race conditions or rendering issues by seeing exactly where a test fails.
* **Collaboration**: Share a clear video of a bug or user journey with developers and stakeholders.
* **Documentation**: Maintain a visual record of your application's critical paths for compliance or training.

### How to record&#x20;

To ensure the best performance and privacy, it is recommended to use Local Rendering. This processes the video directly on your machine.

```bash
maestro record --local YourFlow.yaml
```

After rendering, the video will be available in the same directory as the [reports and artifacts](https://docs.maestro.dev/maestro-flows/workspace-management/test-reports-and-artifacts):&#x20;

* **macOS and Linux**: `~/.maestro/tests`
* **Windows**: `%userprofile%\.maestro\tests`

{% embed url="<https://vimeo.com/775621555/736930f7f9?fe=cm&fl=pl&turnstile=0.v5Dvsunbspg6mWzDMUSHFs0dMs0yAkm68v2PnKbKZbbCDrOqeOLFVw7a0MDCeXvmnW8VegEoLLgaCXp384i5Zsdw_-C9fdftxSav1doTnmY7rd7yUrocp8Nt5uXZnhtq2HrH4XYHOs41wjwywt-DI8xquooSNTamIjkZ3Bhvizb-F5riR4BsvLxhJGgdDIdAu4QlcFA95sQwEExtLRvrPFMeMzUBsoeGBecion0aVfg_3XmCmkm3fypkyOVMJElpjXb_8tK7WxWXQKmqDFOKf4Gm-Aowm12ohdCbZsc6LFN0XrwaPg4zZv8eYuqcrekH0PfcVcPnVM4uSYXy3Rpo_J1dDMTQyxadLRBX_rc8olaBC-MyI4hBvyDWbfm1N6VapDlTh0p5ahB5P_MGNoNdDyvckhJn5o_1C3TvzatOpRosZEav3RI5CN0CdvxoUm5Q4ci46wrkaO-3mDeef2Mu8uqwBzhyXIg_1n_WyPKRd56jO0FW_B9P8kwo4rdEVEBrivbqzEa46ypxiZwps3oVgkgSUDB6T1QlgL9evbNWo40QW26ut8vSseur3VBCMPC9ZjqwXGC5PevVGYZvfoZuirg-m3yDLBK1Rc74Z4RQJMIreAhF6G5xRJFtW56ntaD-PLcP-pxoy_aESMTDiolfcYD9CNy4LG5BRXSGPhSx7vlsWkNwbmz_pgfm40WSEAm900ypHSL5N4lXlJubejTV_yyEk5GpItHBvXAU9D3ZncstuVj8jsV8pMzYONiMbMHwCJ9lnES1yeql2Rp1Tf02l9owTIFPZ1UdgQ2AnH-XAjZy_vi0oT8gyKZ53oeLqRoQNqkSORIBZouPt2N5bnZ0oWW_AwEkU021KAvKFWdBKjDWduhrdwfwqAzwvl54i0hBTtUPRQaNXZkyi3_DBV6afpvz1d_3-19Gqp22NHlPH_voGzCgr2NDjibcwbRBWds6.2fM6XVw1thFNfTonAE7BUg.f69c9372bcce305de3604bbfb8f35e381ea503296a0c3decd7c88e7db84e967b>" %}

It's important to notice that recordings are limited to a maximum of two minutes. If your Flow runs longer, the recording will stop automatically.

{% hint style="info" %}

#### Deprecation notice

The standard `maestro record` (remote) command is being deprecated. In future releases, local rendering will become the default behavior. We recommend switching to the `--local` flag now to prepare for this change.
{% endhint %}

#### Legacy (Remote rendering)

If you run `maestro record` without the `--local` flag, Maestro currently sends the raw screen capture and Flow output to mobile.dev servers to be processed.

{% hint style="info" %}

#### Privacy and security&#x20;

* **Signed URLs**: Remote recordings generate a [signed URL](https://cloud.google.com/storage/docs/access-control/signed-urls) valid for 60 minutes.
* **Auto-Deletion**: All videos sent to our servers are automatically deleted after 24 hours.
  {% endhint %}

### Related content

You can also record your tests using [startRecording](https://app.gitbook.com/s/HqSeOOzxPCLfnK9YzOkb/commands-available/startrecording "mention") or take screenshots for specific steps using [takeScreenshot](https://app.gitbook.com/s/HqSeOOzxPCLfnK9YzOkb/commands-available/takescreenshot "mention").
