If you are making a long recording in OBS, record to MKV when you want a better chance of keeping a usable file after an unexpected stop, then remux it to MP4 if your next tool needs MP4. If you already have an MP4 and want it to play in an OBS scene, add it as a Media Source; remuxing is a separate task and is not a general repair step.
That distinction matters because “prepare an MP4” can mean either creating a recording in a recoverable way or setting up an existing file for playback. The right choice depends on the job, the codecs inside the file, and the software that needs to open it.
Decide whether you are creating or playing an MP4
Start by asking what you need at the end. If you are about to record a long session, your first decision is the recording format. If the video already exists, your first decision is how to load and test it in the scene. These routes overlap only when you need to convert a recording into a file another application can use.
A container such as MP4 or MKV holds the video and audio streams. The codecs describe how those streams are encoded. Changing a container is not the same as changing codecs: a file can be an MP4 and still contain a codec that a particular player or editor cannot handle. Likewise, a file can have compatible streams but be unusable because it is damaged or incomplete.
For a new long recording, think about what happens if OBS or the computer stops before you press Stop. Standard MP4 needs finalisation, so an interrupted write may leave a recording that cannot be used. OBS recommends MKV for most recording situations because an unfinished MKV can remain playable and recoverable. That is a reason to choose it, not a promise that every failure leaves every file intact. The OBS Audio/Video Formats Guide explains the trade-offs between containers.
For playback, do not convert a file just because it is long. First add it as a Media Source and see whether OBS can read it and whether it behaves as needed in your scene. You can then investigate symptoms such as a missing image, stutter, or audio trouble without assuming that the container is the cause. A guide to using an external SSD as a video library may help if the practical issue is where to keep large source files, but extra storage does not repair a file or make an unsupported codec compatible.
Record to MKV when recoverability matters
If the recording itself is valuable and runs for a long time, choose MKV as the conservative starting point. In OBS, open Settings → Output and check the recording path as well as the recording format. The path determines where the file will be written, so make sure the selected drive has room for the session and is available for its duration. OBS’s Standard Recording Output Guide covers these controls and recommends MKV where a recording may not stop gracefully.
MKV is useful here because the unfinished file does not depend on the same finalisation step as ordinary MP4. OBS describes an unfinished MKV recording as playable and recoverable. “Recoverable” should be read in that context: it improves the odds of retaining usable media after an interruption, but it does not guarantee recovery after every kind of failure. A damaged drive, a serious write error, or other media problems can still affect the result.
There is a compatibility trade-off. OBS supports a broad range of audio and video encoder combinations in MKV, but some editing applications have weaker MKV support than MP4 support. If your editor, delivery workflow, or receiving party specifically needs MP4, capture in MKV first and convert the container afterwards using OBS remuxing. This keeps the recording decision focused on the risk of interruption, then handles compatibility as a separate step.
Before a session, confirm the output path rather than assuming it is the folder you used last time. If that drive is nearly full, choose a location with enough capacity. An external SSD can be useful as a capacity choice when your internal drive is limited, but it is not a fix for finalisation, codec support, or file damage. If the recording will also become part of a continuous channel’s library, keep the working copy and the intended playback copy distinct until you have checked the latter. For a wider view of output settings and YouTube workflows, see the YouTube live streaming setup guide.
Remux with OBS when MP4 is needed
Remuxing is OBS’s built-in way to put a recording’s existing audio and video streams into another container. After an MKV recording has finished, open File → Remux Recordings, choose the recording, and run Remux. Check where the MP4 output is saved, and confirm that it exists before moving or deleting the MKV source.
You can also have OBS remux recordings to MP4 when they stop: in Advanced output settings, enable Automatically remux to mp4. This can remove a manual step from a regular workflow, but it does not make the initial recording an ordinary MP4 write. The recording is captured in the selected format and remuxed after it ends. If you prefer to verify each result before proceeding, leave the conversion as a deliberate manual step.
A sensible routine is to finish the recording, wait for OBS to complete its work, then check the resulting file in the application that will use it. Keep the MKV until the MP4 has passed that check. This is a practical safeguard against deleting your source before you know the output is suitable; it is not a claim that remuxing can restore a source that was already damaged.
The destination application matters. MP4 is widely supported, but compatibility depends on the streams as well as the container. If an editor refuses the remuxed file, note the exact error and check its supported codecs and audio formats rather than repeating the same remux. OBS documents the workflow in its recording output guide. For a continuous YouTube stream built from prerecorded material, the distinction between preparing a local file and sending it to a live broadcast is important; this guide to streaming prerecorded video from a cloud server covers that different job.
What remuxing changes—and does not change
Remuxing changes the container around the encoded streams. It is not the same as rendering or transcoding, which would decode and encode audio or video again. Because remuxing does not re-encode the streams, it is generally the appropriate choice when you need a different container without changing the encoded picture and sound.
That also defines its limits. A remux does not make a codec supported by a player that cannot read it. It does not improve a low-resolution image, change the frame rate, correct an audio mix, or reliably fix a damaged or incomplete recording. If the original file has missing data or playback faults, changing its container does not establish that the underlying media is healthy.
When a remuxed MP4 still fails, separate the questions. Does the file open in another player? Does the target software support the video and audio codecs? Is the source file itself complete? Does playback fail at the same point each time, or only in one scene or setup? Those checks help you narrow down the issue without treating remux as a universal recovery tool. If your concern is actually a YouTube output setting rather than a local file, the distinction is covered in why OBS may show 4K while YouTube Live shows 1080p.
Some editors accept MKV but need an MP4 delivery copy; others have their own import requirements. Keep the original recording until the actual target workflow has been tested. If you need to change codecs because the receiving application does not support them, that is a separate transcoding decision. Transcoding can take time and can affect quality depending on its settings, so do not choose it merely because a file is large or because its name ends in MKV.
Consider Hybrid MP4 and codec support
OBS also offers Hybrid MP4 for people who need MP4 output directly but want resilience against an interrupted recording. OBS documents Hybrid MP4 as introduced in OBS 30.2. It writes fragmented data and performs a “soft-remux” when recording finishes normally. This is different from ordinary MP4’s dependence on finalisation, but it is not an unconditional guarantee against loss.
The key condition is codec support. Hybrid MP4 works only with supported audio and video codec combinations; do not assume that every encoder available in OBS can be used with it. Check the current codec matrix in the OBS Hybrid MP4 and Hybrid MOV guide and confirm that your chosen output settings match. The guide also notes that Hybrid MOV was introduced in OBS 32.0, so version-specific details should be checked against the OBS version you are actually running.
| Format | Interruption and compatibility trade-off | Practical use |
|---|---|---|
| MKV | OBS describes unfinished recordings as playable and recoverable; some editors have weaker MKV support. | A cautious default for long recordings, followed by remux if MP4 is needed. |
| Ordinary MP4 | Needs finalisation and may be unusable if writing is interrupted; widely supported by editing tools. | Suitable when a completed MP4 is the priority and interruption risk is not the deciding concern. |
| Hybrid MP4 | Uses fragmented writing and a soft-remux on normal completion; codec combinations are limited. | Consider when direct MP4 output matters and your selected codecs are supported. |
| Fragmented MP4/MOV | Fragmented files do not rely on the same finalisation step; workflow support varies. | A possible alternative if the editor or player you need accepts it. |
Hybrid MP4 can simplify a workflow if its codec limits suit your recording settings. MKV followed by remux remains straightforward when you want to record first and create MP4 afterwards. Do not choose between them by name alone: check the encoder settings, the required destination format, and what you need to retain after a forced stop.
Add a prepared MP4 as an OBS Media Source
To play an existing file in an OBS scene, add a Media Source and select the local MP4. OBS lists MP4 among the supported video types for that source. A source can be configured in the scene like other OBS elements; make sure the selected file path remains valid if you move the file or the project to another computer. The OBS Media Sources guide describes the source and its available options.
For a long file, do not judge it only by whether the first frame appears. Let it play through a representative stretch, including any sections where the image or sound changes. If it is intended to loop, test the transition back to the beginning. A file that starts correctly may still have a later fault, and a scene that works once may be affected by how its source is configured. Treat this as a practical check, not a guarantee that every future run will behave identically.
The Media Source settings include Use hardware decoding when available. It is an option to test when the file type and GPU support it, not a universal stutter fix. If the source does not play, first check that the file path is correct and that the file opens in another player. Then check the file’s codec and OBS’s supported formats. Avoid changing several settings at once; otherwise you may not know which change altered the result.
OBS also has a VLC Video source for extended format support, but it requires VLC to be installed. OBS notes that 64-bit OBS requires 64-bit VLC. Use it only where the built-in Media Source is not suitable and the required software is installed. It is a separate source choice, not a reason to install extra tools before you have established what the problem is.
If your scene contains multiple sources, test the file in the scene where it will actually run, with the other intended elements enabled. That can expose a configuration issue that a quick test in an empty scene would miss. For looping prerecorded footage, check how the source behaves at the end rather than assuming the next scene or file will take over automatically; a black-screen troubleshooting guide for a finished video discusses an adjacent end-of-video problem.
Test the file and playback setup
A useful test separates the file from the playback setup. First, confirm the output file exists at the expected path and can be opened outside OBS. Then add it as a Media Source and play it in the intended scene. If one check fails and the other passes, you have a narrower starting point for diagnosis than “the MP4 is unreliable”.
For a recording workflow, make a short trial using the same format, encoder, audio tracks, and destination drive planned for the real session. Stop OBS normally, let any automatic remux finish, and open the output in the application that needs it. A short test cannot reproduce every risk of an overnight recording, but it can reveal a wrong folder, an unsupported codec choice, or an output that your editor does not accept before you invest a long session in it.
For playback, test the whole file where practical, especially if it will loop or remain in a live scene for a long time. Listen as well as watch. Check the point where it repeats, if looping is part of the use, and verify that the source remains visible after scene changes if your layout uses them. This is more useful than assuming that a larger file needs conversion or that a hardware decoding switch must solve every symptom.
If stuttering or sync drift appears, record what you observe: whether it happens in another player, whether it starts at the same point, whether audio continues, and whether the OBS preview and output both show it. The available OBS format and Media Source guidance does not give one universal fix for every such symptom, so avoid applying speculative remedies as if they were guaranteed. Check the current documentation and the exact codec and source behaviour before deciding whether to remux, transcode, or replace the file.
If you are preparing a local file for a continuous YouTube channel, keep the file-preparation decision separate from the decision about how the channel stays live. StreamNeo is relevant when the specific burden is keeping a prepared video broadcasting after your own computer is switched off; it does not change the codec or repair the MP4.
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
Should I record in MKV or MP4 in OBS?
Choose MKV when protecting a long recording from an unexpected stop matters, then remux it to MP4 afterwards if the next application needs MP4. Ordinary MP4 is widely compatible but relies on finalisation, so an interrupted recording may not be usable.
How do I convert MKV to MP4 in OBS without losing the recording?
Use File → Remux Recordings, select the MKV, and run the remux. Keep the MKV until you have checked that the MP4 opens in the application you need; remuxing changes the container and does not promise to repair damaged media.
How do I play an MP4 as a Media Source in OBS?
Add a Media Source to the scene and select the local file. Test playback in the intended scene, and check the path and codec if it does not play; hardware decoding is optional and is not a guaranteed remedy.
Does remuxing make every MP4 compatible with OBS or an editor?
No. Remuxing does not re-encode the streams, so an unsupported audio or video codec remains unsupported. Check the target application’s format requirements, and distinguish codec incompatibility from a damaged or incomplete file.