# Record to file
Capture live video feeds **directly to disk** using either **H.264 (macOS/Windows)**, **HEVC (macOS/Windows)** or **ProRes (macOS)** codecs. The intuitive interface supports **manual recording** or **trigger-based options**, including keyboard shortcuts or **Stream Deck integration**.
> Use case: Archiving signal for live productions or recording unexpected color issues.
For each input source you can configure video file recording separately — codec, resolution, and custom filename template.
From **1.11.45+**, these recording settings are remembered for each input source and no longer reset after restarting OmniScope or reconnecting the source.
Configure video file capture for each input separately.
If recording fails to start (e.g. due to a missing codec, full disk, or an inaccessible folder), OmniScope now displays a clear error dialog describing the cause. Check the message and verify the recording folder path and available disk space.
You can quickly toggle the recording in the Input Strip context menu or from keyboard shortcut / Stream Deck action:
Context menu allows for a quick capture toggle
When recording is active, a red dot appears in the input strip:
## Recording Folder
{% hint style="warning" %}
**BETA** — This feature is available in beta releases (1.11.x). Install the beta version from the downloads page to access it.
{% endhint %}
By default, recorded clips are saved alongside snapshots in the active snapshot folder. You can set a dedicated recording folder in **Input Settings > Codec & output**:
* **Browse folder…** — select a custom directory for all recorded clips
* **Use snapshot folder** — reset to saving clips next to snapshots (default)
The recording folder applies to all input slots. If the selected folder doesn't exist, it is created automatically when recording starts. (1.11.34+)
## Multi-Slot Recording
{% hint style="warning" %}
**BETA** — This feature is available in beta releases (1.11.x). Install the beta version from the downloads page to access it.
{% endhint %}
You can record from multiple input slots simultaneously. Each slot produces its own clip file with a `_s{slot}` suffix to distinguish them:
| Input | Example filename |
| ------ | ---------------------------------- |
| Slot 0 | `capture_2026-03-15_143022_s0.mp4` |
| Slot 1 | `capture_2026-03-15_143022_s1.mp4` |
| Slot 2 | `capture_2026-03-15_143022_s2.mp4` |
Start and stop recording independently for each slot using the context menu, keyboard shortcuts, or Stream Deck actions. (1.11.34+)
## Filename Template
Customise the clip filename pattern using tokens. The same tokens available for [snapshot filename templates](/nobe-omniscope/features/snapshots.md#filename-templates) can be used, with the most common being:
| Token | Description | Example |
| -------------- | ---------------- | ------------- |
| `%DATE%` | Current date | `2026-03-15` |
| `%TIME%` | Current time | `143022` |
| `%INPUT_SLOT%` | Input slot index | `0`, `1`, `2` |
The default template is `capture_%DATE%_%TIME%_s%INPUT_SLOT%`, producing files like `capture_2026-03-15_143022_s0.mp4`.
Your chosen filename template is also persisted per input source. (1.11.45+)
## Codecs
| Codec | Platform | Notes |
| ------------- | -------------- | ---------------------------------- |
| H.264 | macOS, Windows | Default, widely compatible |
| HEVC | macOS, Windows | Better compression at same quality |
| ProRes 422 | macOS only | High quality, larger files |
| ProRes 422 LT | macOS only | Lighter variant of ProRes 422 |
## Resolution
Recordings can be captured at **1280×720** or **1920×1080**. The source signal is scaled to the selected resolution during recording.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.timeinpixels.com/nobe-omniscope/live-pack-add-on/record-to-file.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.