START HERE
For a practical starting point, choose MKV and remux when your editor needs MP4, or use a supported Hybrid MP4/MOV workflow after testing an import. Traditional MP4 is different from Hybrid MP4. Preserve the original and verify video, sound, and separate tracks before deleting anything.
Separate the container from the codec
MKV, MP4, and MOV are containers. The video inside might use H.264, HEVC, AV1, or another codec, and the audio has its own format. An editor recognizing an MP4 file does not prove it can decode everything inside it. Check an actual short import using the settings you plan to keep.
The OBS format reference lists supported combinations. Avoid treating any one codec as the universal best choice: compatibility with the editor, destination, and hardware matters as well as file size. This guide addresses local recording; a streaming service may have different accepted codecs.
Choose the recovery and editing tradeoff
| Container | Useful starting point | Check before relying on it |
|---|---|---|
| MKV | A resilient recording master with broad codec support. | Your editor may require remuxing or transcoding. |
| Hybrid MP4 / Hybrid MOV | Recoverable fragmented writing with conventional-file compatibility after normal finalization. | OBS version, supported codecs, and the actual editor import. |
| Traditional MP4 / MOV | Compatible finalized files where that exact workflow is required. | An interrupted recording may be unusable because finalization did not finish. |
Hybrid MP4 arrived in OBS 30.2; Hybrid MOV arrived in 32.0. Their codec support differs: for example, the official Hybrid format guide lists ProRes for Hybrid MOV and AV1 for Hybrid MP4. Check the current table rather than renaming an extension.
Resilience is not a backup. A full or failed disk, incomplete copy, or damaged storage can still lose data. Keep important originals on reliable storage with enough free capacity for the recording and any additional remuxed copy.
Record a small file before a long session
- In Settings > Output, select the intended recording path, format, encoder, and audio tracks. Record the settings you changed.
- Capture a short sample with moving video, normal speech, a louder phrase, and a clear clap or other visible audio event.
- Stop normally and wait for the file to finish writing. Open it in the player and editing software you actually use.
- Scrub near the beginning and end, inspect audio/video alignment, and check every intended audio track. Repeat using your normal stream-and-record setup if that is the real workload.
A file that opens is only the first checkpoint. Confirm the editor exposes the tracks you need, that color and motion look sensible, and that export produces a usable result. A two-minute test is cheaper than discovering an incompatible recording format after a long event.
Remux a compatible recording and retain the original
OBS provides File > Remux Recordings. Select the source recording, review the destination, and run the operation. The recording-output guide also documents automatic remuxing after recording stops.
Remuxing repackages encoded streams; it is not the same as rendering them through a different codec. It can solve a container-acceptance problem, but it cannot make an unsupported video or audio codec universally playable. If the editor still rejects the result, identify which codec or track causes the problem and choose a supported conversion workflow.
Keep both files until the remuxed copy has passed playback and editor checks. Do not rename the original extension to “convert” it. When storage is tight, move a verified backup first rather than deleting the only source file to make room for an unverified export.
Investigate missing sound or an interrupted recording
If the file plays video but seems silent, check the player's selected audio track. A multitrack file can contain an intentionally empty or isolated first track while another track has sound. Inspect it in the editor before concluding that remuxing removed audio. Then verify the source-to-track assignments for the next recording. If you export a WAV audio clip to check levels or clipping before editing, the local WAV file inspector verifies channel peaks on your device.
If OBS or the machine crashed, first copy the interrupted file and work on the copy. Record the chosen container and codec and whether the recording ever stopped normally. Do not promise a universal recovery command: the next step depends on what was actually written and which format was used.
After resolving an import or recovery problem, run the small end-to-end test again. Preserve a working settings note and sample file so future OBS, driver, or editor updates can be checked against a known baseline.
To estimate GB/hour disk space before a long capture, use the OBS bitrate & recording size calculator; to verify every track assignment in your MKV or Hybrid MP4 recording, map them in the OBS multitrack audio planner.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.