You do not necessarily need to convert a MOV file before using it in OBS. OBS lists MOV as a supported Media Source format, but playlists use the VLC Video source, so test your clips in the source you intend to run before changing them.
If a clip fails or behaves inconsistently in that configuration, a sensible compatibility-focused target is MP4 with H.264 video and AAC audio. Use stream copy when the existing streams already fit the target; transcode only when they do not.
Do MOV files need conversion for OBS?
The file extension tells you the container, not the codecs inside. Two files ending in .mov can contain different video and audio formats, and that difference matters more than the filename when you test playback. Converting every MOV by default can waste time and introduce another lossy encode without solving a problem.
OBS documents MOV among the video types supported by Media Source. Its VLC Video source is the option that supports a playlist, and requires VLC to be installed. These are distinct source types, so success in one does not establish that a file will work in the other. Check the OBS Media Sources guide for the documented source behaviour and VLC requirement.
Start by adding a representative clip to the exact source you plan to use. If you need a single file, try Media Source; if you need a rotating playlist, test VLC Video. Confirm picture, audio, looping, and the transition between clips before deciding that the file needs conversion. This test-first approach is especially useful for a long-running channel: a clip that previews correctly once may still expose a problem when the playlist loops overnight.
If the workflow also involves choosing a playback method for an extended broadcast, compare the trade-offs in our guide to running a 24/7 stream from prerecorded videos. The choice of streaming arrangement is separate from MOV conversion, but testing your media within the intended arrangement avoids solving the wrong problem.
Check MOV support in Media Source
To check the simpler case, create a Media Source in OBS and select a MOV clip. Confirm that the video appears, that its audio is audible where expected, and that restarting or looping the source does not change the result. If it works for your use, there may be no reason to convert it.
A successful Media Source test is useful but limited: it does not prove the VLC playlist will behave the same way. Playback depends on the codecs in the file as well as the playback path and the software versions on the machine. OBS's audio and video formats guide documents format and codec combinations, including H.264 video and AAC audio in MP4 and MOV. It does not promise that every codec inside every MOV will play reliably in every playlist configuration.
For a one-off local clip, a direct Media Source may be enough. For a collection, test several representative files, especially any produced by different cameras or editing applications. Include the clip with the most unusual frame size, frame rate, audio arrangement, or codec if you know which one that is. A successful test of one ordinary clip cannot stand in for a playlist containing several different kinds of file.
Set up a playlist with VLC Video
Add a VLC Video source in OBS and use its playlist controls to add the files. OBS documents playlist looping and shuffle options; looping is enabled by default and shuffle is disabled by default. Choose deliberately: a devotional sequence may need a fixed order, while a station that should vary its ambience may prefer shuffle. The VLC Video source also has controls for audio tracks, subtitles, and behaviour when the source becomes visible.
VLC must be installed for the VLC Video source to be available. OBS specifies that 64-bit OBS requires 64-bit VLC. Check the matching requirement on the computer where the channel will actually run; installing VLC on a different editing machine does not help the broadcast machine. See the OBS Media Sources documentation for the source setup and its playlist controls.
Test the playlist as a playlist, not only as a set of files opened one at a time. Let it advance from one clip to the next, then let it loop back to the start. Listen for missing audio, abrupt silence, or a track that differs from the one you expected. If the file has multiple audio tracks or subtitles, set the intended track and verify that selection; an encode that silently discards a needed track is not a compatibility fix.
If you are troubleshooting stutter rather than a file that will not open, separate those questions. Caching settings and the way a desktop application reads media can affect playback, so our article on media-file caching and stuttering may help with that specific symptom. It is not a reason to convert a file that already plays correctly in OBS.
When stream copy is suitable
Stream copy changes the container or selected streams without decoding and encoding the media again. In FFmpeg, -c copy requests this no-re-encode path. It avoids the quality loss and processing time associated with another lossy encode, but it does not make an incompatible codec compatible: the chosen output container and the playback environment still need to support the copied streams.
First inspect the file's streams. Note the video codec, dimensions, frame rate, audio codec, and whether it has additional audio tracks or subtitles that matter to you. Then decide whether you need to preserve all tracks or only the first video and first audio. FFmpeg's documentation explains stream selection and stream copy; explicit mapping is helpful when automatic selection could choose the wrong track.
For a file whose video and audio streams are suitable for MP4 and the intended OBS/VLC path, a simple example is:
ffmpeg -i input.mov -map 0:v:0 -map 0:a:0? -c copy output.mp4
Here, the command selects the first video stream and the first audio stream if one exists, then copies them. The ? makes the audio mapping optional, so a silent clip does not fail solely because it has no audio stream. This command does not re-encode the video or audio. If the MOV's streams do not fit MP4 or your target playback path, a new filename will not fix that; use a transcode instead.
Stream copy is a useful first attempt when you want an MP4 container and the codecs are already appropriate. It is also a way to avoid degrading material that already plays well. Do not use it merely because it is faster: if the test shows a codec or playback issue, copying preserves that issue. A related decision path for a different source format appears in our guide to converting WebM files for OBS playlists.
Convert to H.264 and AAC if needed
When testing points to a compatibility problem, MP4 with H.264 video and AAC audio is a reasonable general-purpose target. OBS lists those combinations in its format guide. They are a practical starting point, not a guarantee for every machine or source file. For an H.264 video stream and optional AAC audio, an FFmpeg example is:
ffmpeg -i input.mov -map 0:v:0 -map 0:a:0? -c:v libx264 -preset medium -crf 20 -c:a aac -b:a 192k output.mp4
This selects the first video stream and, if present, the first audio stream. It encodes video with libx264 and audio with AAC. The output options need to appear before the output filename. The example gives you concrete starting values to test; crf 20, preset medium, and 192k audio are not universal best settings, nor values OBS certifies for every MOV. Consult FFmpeg's libx264 encoder options and adjust based on a short sample and the result you need.
CRF controls the quality/file-size trade-off for the libx264 encode: a lower value generally aims for higher image quality and a larger file, while a higher value generally makes a smaller file at lower quality. Compare a short representative section on the actual output display, including any fine detail that matters, such as text in a news loop or a deity's facial details in a devotional video. Do not choose a CRF only by looking at the file size.
The preset is a speed-versus-compression-efficiency control. A faster preset can complete sooner but may make a larger file for a comparable quality target; a slower preset may use more processing time. The best choice depends on how long you can wait for conversion and whether storage matters. FFmpeg documents the preset and CRF controls, but your own short test is the useful check for a particular source.
Keep the source resolution and frame rate unless you have a defined reason to change them, such as a playback constraint or an intentional common format for the playlist. Resizing or changing frame rate is not automatically a compatibility improvement and can alter the image or motion. If you have multiple audio tracks or subtitles that matter, revise the -map options rather than relying on this example, which deliberately selects only the first video and optional first audio stream.
Test playback in the target configuration
After copying or transcoding, reopen the output in the same OBS source and on the same machine that will run the channel. A file playing in a desktop player is not enough to establish that the VLC Video playlist will handle it correctly. Check the start, the end, and the transition to another clip; then verify the loop or shuffle setting you intend to use.
Use a short test playlist with both converted and unconverted examples if you are deciding whether conversion helps. Keep notes on which file, source type, and settings you tested. If the original MOV works in VLC Video, leave it alone rather than producing a converted copy just to standardise extensions. If only one clip fails, convert that clip first instead of reprocessing the entire collection.
Check audio separately. Confirm that the clip's intended audio track is selected and that the level remains suitable when the next item begins. For a silent visual loop, verify that the absence of audio is intentional rather than a failed track mapping. If captions or subtitles are part of the broadcast, confirm their behaviour in the source and output; the sample transcode above does not preserve every possible stream automatically.
For a channel that runs continuously, make the test long enough to include the points most likely to expose a setup issue: playlist advancement, looping, and any variation between clips. This is not a promise that a test rules out every future fault. It is a practical way to avoid spending hours encoding material when the source already works, and to identify a specific failure before preparing the full collection. If the larger question is how to keep an always-on broadcast operating, our guide to hosting an always-on YouTube stream from India covers a different part of that decision.
If your problem is leaving a local computer running to keep a file on air, StreamNeo removes that particular task: you upload the video once, provide your YouTube stream key, and the broadcast can continue with your computer switched off. It is YouTube-only, so first confirm that a file and channel are ready for the workflow you intend to use.
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 convert every MOV to MP4 for OBS?
No. OBS lists MOV as a supported Media Source type, and a MOV may already play in the source you need. Test it in the actual source first; conversion is for a demonstrated compatibility or workflow need, not a requirement based on the extension alone.
Does OBS play MOV files in a VLC playlist?
A MOV extension alone cannot answer that because the file's codecs and the playback setup matter. VLC Video is OBS's playlist source and requires VLC to be installed, with 64-bit VLC for 64-bit OBS; test the specific file in that playlist before relying on it.
Can I use -c copy instead of re-encoding?
Yes, when the existing streams are suitable for the output container and the playback environment. Stream copy avoids another encode, but it does not change the codec, so transcode to H.264 and AAC if testing shows that the copied file still does not work as needed.
What are the best FFmpeg settings for an OBS playlist?
There is no single best setting for every MOV. If conversion is needed, MP4 with H.264 video and AAC audio is a sensible compatibility-focused target; preserve resolution and frame rate by default, then adjust CRF or preset only after testing a representative clip.