If you have a finished OBS recording in MKV and need an MP4 copy, start with OBS’s built-in File > Remux Recordings workflow. Remuxing copies the encoded streams into a different container; it does not re-encode them, so it avoids another lossy encoding pass.
That does not make an unsupported video or audio codec compatible with MP4, your editor, or a playback device. Keep the original recording until you have checked the resulting file in the application you plan to use.
When remuxing is the right fix
Remuxing is useful when your recording’s encoded video and audio are suitable for the destination, but the file container is not. For example, an editor or workflow may accept MP4 more readily than the MKV file produced by OBS. A remux can provide an MP4 container while retaining the existing video and audio streams.
The distinction matters because a file has both a container and encoded streams. The container organises the streams and carries information about them; the codecs describe how the audio and video themselves are encoded. Changing the container leaves those encodings in place. If a target application cannot decode the video codec inside your MP4, remuxing will not change that codec.
Use remuxing when you want a container change and your intended playback or editing software supports the streams being copied. It can also be useful when you want to put a completed recording into a format required by a downstream workflow without making a new generation of compressed video. It is not a general-purpose repair or conversion step.
If the file plays correctly in OBS but fails in another application, first identify what that application accepts. Check the video codec, audio codec, and any extra audio tracks in the source file. If the issue is a codec mismatch, you may need a different container that supports the existing streams, or a separate transcoding workflow that decodes and re-encodes them. Those are different choices with different compatibility and quality trade-offs.
For a recurring channel, treat the recording file and the stream source as related but separate jobs. A remuxed recording is not itself a live broadcast; it is a file you can use in an editing, publishing, or playback workflow. If you are building a channel around a repeating video source, the OBS media source and VLC playlist comparison covers a different decision: how OBS plays content during a live session.
Remux a recording in OBS
For a one-off file, OBS’s own remux tool is the simplest route. Stop the recording first so OBS has finished writing the source file. If you are recording live material, make sure you have the complete take you intend to use; the remux process works on a recording file, not on a recording that is still being written.
In OBS, choose File > Remux Recordings. Use the file picker to select one or more recordings, then click Remux. Wait for OBS to show its completion prompt. The output MP4 is the new file to inspect; retain the original MKV until you know the MP4 works where you need it.
Open the result in the intended editor or player. Check that the picture and sound are present, the duration looks right, and any tracks you expect are available. If your workflow needs separate microphone and desktop audio, for example, confirm that the output and the target software present those tracks as expected. This check is practical verification, not a guarantee that every editor handles the same streams in the same way.
OBS documents this workflow in its Standard Recording Output Guide. The menu wording and placement can change between versions, so if you do not see the option, check your installed OBS version and its current guide rather than assuming the file is unsuitable.
Do not overwrite the only copy of the source. If the remux fails, or the resulting file does not behave as expected, the original gives you a clean point from which to examine stream compatibility or try a different workflow. If you are setting up OBS for an always-on channel rather than preparing a finished recording, see this guide to using a cloud-hosted OBS session; its purpose is operating a live session, not changing a file container.
Enable automatic remuxing for future recordings
If you routinely need MP4 copies, OBS can remux automatically after you stop recording. In OBS, open Settings > Advanced and enable Automatically remux to mp4. The OBS guide describes the remux as starting as soon as recording stops. The original recording settings still decide what streams are recorded; the automatic option does not change codecs or recording format choices.
This setting is convenient when you want an MP4 output after each recording without remembering a separate manual step. It is also easy to misunderstand: it does not mean OBS records directly to MP4 throughout the session, nor does it make the recording process immune to interruption. It runs after stopping the recording, when OBS can process the completed file.
OBS recommends MKV for ordinary recording because an interrupted recording is less likely to lose the entire file. Traditional MP4 and MOV recording generally need finalisation, and an interruption before finalisation can leave the file unusable. A practical pattern is therefore to record to MKV, stop recording cleanly, and have OBS create the MP4 copy afterwards. Keep the MKV until you have verified the MP4.
The trade-off is an additional output file and a small extra step in your storage routine: you need to know which file is the original and which is the remuxed copy. Use clear filenames or a folder convention if you make many recordings. For instance, keep the OBS recording in one folder and place the checked MP4 copy in the folder used by your editor or upload workflow. Do not delete the source simply because an MP4 appeared.
OBS’s recording guide describes the automatic setting and the recommended recording pattern. Menu labels can vary by version, so confirm the setting in your installed version. If your OBS version offers a different recording format intended to combine recovery resilience with MP4 compatibility, read its format guidance and test it with your specific software before changing a routine that already works.
What remuxing changes—and what it does not
A remux changes the container around selected streams. In a stream-copy operation, software reads the existing encoded streams and writes them into the destination container without decoding the video and audio and encoding them again. That is why remuxing can avoid quality loss caused by an additional lossy encoding pass. It does not improve the picture, reduce the file size by re-compressing it, or change resolution.
The phrase “without re-encoding” is useful, but it describes a specific operation, not an outcome guarantee. The output still contains the same encoded streams that were in the source, subject to what the tool can carry into the destination container. If a particular stream cannot be represented in the target container, the operation may fail or require you to change which streams are selected. If the destination application cannot decode a retained codec, it can still reject the output.
Keep three questions separate:
| Question | What remuxing can do | What you should check |
|---|---|---|
| Is the container acceptable? | Write copied streams into another container when supported | Whether the editor, player, or upload workflow accepts the output container |
| Are the streams compatible? | Retain selected encoded streams without re-encoding | Whether the target supports each video and audio codec and track |
| Is the recording intact? | Create another file from the source | Whether the source itself is complete and the output plays through as expected |
If your reason for seeking an MP4 is simply that an application asks for MP4, try the OBS remux workflow and test the output. If your reason is that the application rejects a codec, a container change alone is not the answer. Find out which streams it accepts, then decide whether to use a suitable container or re-encode into supported formats. Re-encoding may take more work and can alter quality; it is not what OBS’s remux button does.
This is also why a remuxed MP4 should not be treated as a compatibility certificate for every platform. MP4 can contain different types of encoded audio and video, and software support varies. The OBS Audio/Video Formats Guide lists formats OBS works with, but a third-party editor’s supported formats are a separate question. Check that application’s own documentation as well.
Use FFmpeg for batches or stream selection
FFmpeg is an alternative when you need a repeatable command, want to process files in a batch, or need explicit control over which streams are copied. It is less convenient than the OBS dialog for a single recording because you must inspect the input and choose a mapping deliberately. The command-line approach is useful only if you are comfortable confirming paths and reading the output messages.
A basic stream-copy example with an explicit map is:
ffmpeg -i INPUT.mkv -map 0:1 -c copy OUTPUT.mp4
Here, -c copy tells FFmpeg to copy rather than decode and encode the selected stream. -map 0:1 selects the second stream from the first input; it does not mean “keep all video and audio”. The stream’s type depends on the actual input file, so inspect the stream listing before relying on a numeric index. This example can be useful when you intentionally want one stream, but it is not a universal command for a complete recording.
If you want FFmpeg to attempt to map all streams, a common form is:
ffmpeg -i input.mkv -map 0 -c copy output.mp4
That asks FFmpeg to copy all input streams. It does not mean every stream type can be written to MP4, or that the output application can use them. Read the stream information and any warnings or errors. If the source has multiple audio tracks, subtitles, or other data, decide whether each belongs in the output and whether MP4 and your destination software support it.
FFmpeg’s documentation explains stream mapping and stream copy. Its documented example with -map 0:1 makes stream selection explicit. Mapping is particularly useful when the source includes tracks you do not need, but it is also a way to accidentally omit the video or the audio you expected if you choose the wrong stream number. If you do not know what the stream indices represent, inspect them before running a batch over valuable originals.
For batch use, test the command on one copy first. Confirm the output filename, check that the command exits without an error, and play the result in the target application. Only then adapt it to a folder of files. Keep the source files until the batch outputs have been checked, and avoid commands that overwrite source material. If FFmpeg reports a codec or container limitation, do not try random mapping changes until you know which stream is causing it.
The choice between OBS and FFmpeg is mostly about workflow control, not quality. OBS’s manual remux is straightforward for a few completed recordings; its automatic setting removes the reminder step for future recordings; FFmpeg gives command-line users finer mapping and scripting control. None changes the compatibility rule: stream copy preserves the encoded streams selected, so a codec the destination cannot handle remains a codec it cannot handle. For a separate streaming workflow built around a playlist, the FFmpeg playlist rotation troubleshooting guide addresses playback order rather than remuxing files.
Check compatibility before streaming or editing
Before you plan to use an MP4 as a source, check the actual codecs and tracks, not just the .mp4 extension. The OBS format guide distinguishes containers and supported audio/video formats. The editor or player you intend to use may support a narrower set, and an application’s own documentation is the right reference for that application. If the file must go to a YouTube workflow, check current YouTube guidance rather than assuming that any MP4 is accepted or suitable.
A practical check has two parts. First, inspect the source’s stream list and note the video codec, audio codec, number of audio tracks, and any additional streams you rely on. Second, open the remuxed file in the destination software and test the parts that matter to your use: picture, sound, track selection, and duration. A brief test at the start is not enough if you rely on a long file; seek to another point as well and ensure playback remains normal.
If the remux operation fails, the output is missing a track, or your editor refuses the result, return to the source and identify the mismatch. Possible next steps are to select only streams needed and supported by the target, to choose a different container that carries the existing streams, or to transcode into formats the target accepts. Transcoding is a distinct step that decodes and re-encodes; choose it only when stream copying into a suitable container cannot meet the requirement.
For YouTube uploads and live workflows, consult the current YouTube Help guidance on supported file formats and the relevant live-stream setup guidance before making assumptions about compatibility. Requirements and documentation can change. A file that opens in your local editor is not, by that fact alone, confirmation that every upload, playback, or live-stream workflow will accept it.
For someone preparing a recorded loop, the file check is only one part of operating a channel: you also need a reliable way to deliver the video when your own machine is off. StreamNeo removes the specific burden of keeping your computer running to repeat an uploaded file as a YouTube live stream; it does not change the file’s codecs or make a mismatched recording compatible, so check the source before choosing the broadcast workflow.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does remuxing an MKV recording to MP4 reduce quality?
A stream-copy remux does not decode and re-encode the selected video and audio streams, so it avoids another lossy encoding pass. It does not improve the original quality either. The output retains the encoded streams that were copied.
Will every MKV recording remux successfully to MP4?
No. Success depends on the streams in the recording and whether they can be carried in MP4. Even if the remux completes, the software you use may not support one of the retained codecs or tracks.
Should I record directly to MP4 in OBS?
OBS recommends MKV for ordinary recording because an interruption is less likely to make the whole recording unusable. You can remux a completed recording to MP4 after stopping. Check OBS’s current recording-format guidance if you are considering another format, including any alternative offered by your installed version.
When should I use FFmpeg instead of OBS?
Use OBS’s remux dialog for a straightforward one-off or its automatic setting for future recordings. FFmpeg is useful when you need a script or explicit stream selection, but inspect the source streams and mapping carefully. Neither method makes unsupported codecs compatible.