OBS Recording Formats: MKV, Hybrid MP4, and Remux Checks

Start with the file you need, not a universal format rule

This guide is scoped to OBS 33.0.0, listed on the official download page as released on October 23, checked October 28, 2026. Record your installed version, operating system, video editor and required source tracks. Then check Settings → Output → Recording Format in your own build; a saved profile's setting cannot be inferred from this version scope.

A container is the file's packaging; the codecs describe the encoded picture and sound inside it. An MP4 filename does not tell you that it contains H.264 and AAC. Write down both the selected container and codecs before choosing a handoff.

The official guides disagree about defaults. The Audio/Video Formats Guide calls MKV the default, yet on that same page labels Hybrid MP4/MOV as operating-system defaults. The older Standard Recording Output guide recommends MKV. For the dated default change, use the 32.0 release notes: hybrids became defaults for new profiles. None of that establishes the setting of your existing profile.

The useful decision is whether your recording can survive the kind of interruption the format is designed for and whether your destination accepts the actual streams. No container protects against every storage failure or replaces a second copy.

MKV, regular MP4, and the hybrid alternatives

OBS describes MKV as resilient when recording is interrupted and broadly capable of storing its supported encoder outputs. Its practical tradeoff is the destination: some editing workflows need a different container. If your editor already imports the complete MKV correctly, an extra remux is not automatically necessary. OBS's Formats Guide describes broader editing-software support for its hybrid options than for MKV; treat that as a documented starting point, then check your editor with a short recording.

Traditional MP4/MOV needs finalisation. OBS warns that an interrupted file may not be recoverable. Do not treat regular MP4 as equivalent to the fragmented or hybrid options simply because they share an extension.

Hybrid MP4/MOV writes fragments during recording and, after a normal stop, adds the indexing that lets compatible software treat the result like a regular file. An unfinished hybrid file can retain readable fragments, but that is not a guarantee of complete media, metadata or recovery from a damaged drive.

The hybrid options also have different documented codec support. Check OBS's current format table for your chosen video and audio codecs, then verify that combination in your destination. This page does not turn a container's ability to store a stream into a claim that every editor can decode it.

Remux an existing MKV to MP4 in OBS

For a stopped recording, OBS's Standard Recording Output guide documents File → Remux Recordings: choose the recording with the file-picker button, run Remux, and wait for the completion prompt. Confirm those controls in your own build; we did not exercise the OBS 33 interface. Retain the source and note the input and output paths so you inspect the new copy.

OBS's remux implementation at the 33.0.0 version tag copies the encoded media packets into the output container rather than decoding and encoding them again. We inspected that source, not a running recording. This supports the no-new-encoding-pass distinction; it does not mean the output file is byte-identical or that every stream will work in every destination. FFmpeg's streamcopy documentation explains the general operation and why a destination container can still reject a source.

If the remux fails, creates an unexpected output, or still will not import, preserve both files and read the actual error. Check the source codecs and the editor's current supported formats before trying a different container or a separately planned transcode. Renaming .mkv to .mp4 does not perform a remux.

• Before: record the source filename, its location, approximate duration and required audio tracks.
• During: use File → Remux Recordings and give the output a distinguishable path; do not overwrite your only source.
• After: a completion prompt is the start of verification, not proof that your editor exposes every track.

Automatic remux saves a step, not the acceptance check

OBS's recording guide documents an Automatically remux to mp4 option in Advanced settings that runs after recording stops. Confirm the available setting in your installed version and profile. A hybrid recording's normal finalisation and this separate automatic-remux workflow should not be treated as the same operation.

If you use automatic remux, identify which file is the capture original and which is the handoff. Budget storage for both and make the editor check part of the session routine. Do not automatically delete the original simply because an MP4 appeared.

For a repeat series, validate one representative short recording before trusting the same settings with an interview or tutorial. Repeat that check after changing an encoder, audio format, OBS version, operating system or editor.

A missing voice may be a track-selection problem

OBS's multiple-track guide notes that standard players play one audio track at a time. Hearing only one source in a player does not by itself prove that the others were lost. The editor may also expose a different subset of the streams than the player.

Inspect the expected audio tracks in the source and in the remuxed handoff. Then import the handoff into the intended editor and audition each required track. If a source was never recorded, changing the container cannot reconstruct it; if the file has the track but the editor cannot use it, investigate that editor's import/codec behaviour.

Remuxing does not combine tracks into a mixed programme. Design the mix and isolated-track assignment before recording; our separate OBS audio-tracks guide covers that routing job. Here the question is whether the file-to-editor handoff preserved what was actually captured.

The recording-to-edit acceptance worksheet

Use a disposable short test before the real session and complete the same checks on the finished handoff. These are editorial acceptance criteria to run yourself, not test results from StudioSignalLab.

Write one row per check with five fields: source filename, handoff filename, expected result, observation and pass/hold. A vague note such as ‘video works’ cannot tell the next editor which recording was checked.

• Identity — identify the exact source and output paths, OBS version, selected container and codecs. Hold if you cannot distinguish the original from the handoff.
• Duration and seeking — compare the reported duration, seek near the beginning, middle and end, and confirm the final intended passage exists. Investigate unexplained shortening or an unreadable ending.
• Required tracks — list the programme mix and each isolated source you intended to capture. Audition them individually in the editor. Hold if an essential voice or channel is missing or silent.
• Picture and sound — inspect a representative moving section, speech and quiet passage. Hold on unexpected artifacts, wrong colour interpretation or decoding errors; a new extension is not a diagnosis.
• Sync — check a visible/sounding reference near the start and end. If you observe drift, document it before editing; repeated remuxes are not a promised timing fix.
• Reopen and retain — close and reopen the editing project, verify the intended media resolves, then retain a separate copy of the original under your backup plan. Passing this worksheet is not permission to erase the only capture.

Choose the next action from the failed check

If the source is complete and the only obstacle is its container, remux and repeat the acceptance check. If the destination cannot decode the streams, investigate supported codecs and whether a new encoded working copy is necessary. If required media is absent from the source, return to the capture plan or a separately retained recording.

Do not test recovery by cutting power or forcing a crash during valuable work. This article does not provide forensic recovery instructions, a measured crash-survival result, or a universal editor compatibility list. Its recommendation is narrower: make the format decision early and approve the actual handoff before it becomes the only file left.

Once the complete recording imports correctly, a slow timeline is a separate problem. A proxy workflow can make editing more manageable, but it is not a substitute for retaining a complete, verified master.