First identify where the failure happens: in a playlist of files played locally by OBS, during a YouTube upload, or in a YouTube video shown through an OBS browser source. Those workflows do not share one codec fix, and the error alone may not identify the cause.
For local playlists, check the OBS source type and each file's actual streams. For an upload, compare the file with YouTube's recommended encoding settings. Keep browser-source playback problems separate unless you have evidence that the local media file itself is unsupported.
Identify which workflow is failing
A phrase such as “unsupported video codec” can describe different stages of a workflow. Start with what you were doing when the message appeared, rather than changing a codec immediately.
If you added files stored on your computer to an OBS scene and expected them to play one after another, you are troubleshooting local playlist playback. OBS has a built-in Media Source and a separate VLC Video source. They are not interchangeable for playlist behaviour: OBS describes VLC Video as playlist-capable, whereas Media Source is intended for an individual media file. This is the first distinction to check if the source itself will not load or does not behave as a playlist.
If you selected a file on YouTube and YouTube rejected it, failed to process it, or produced an upload error, the issue is in YouTube's upload and processing workflow. That is where YouTube's encoding recommendations apply. They do not, by themselves, establish which formats will play as a local OBS source.
If you added a Browser source in OBS and opened a YouTube watch page, the browser is displaying a web page. A playback message there is not proof that OBS cannot decode the video file: you may not be playing a local file at all. Treat page loading, sign-in, playback availability and local media decoding as separate questions.
This distinction matters for an always-on channel. A file that will not play in an OBS playlist needs investigation before it becomes part of the rotation; an upload that YouTube has not processed needs a different check. If you are comparing a conventional OBS workflow with an always-on service, how Muvi Live and OBS differ for an always-on YouTube channel may help clarify which part of the workflow you are choosing. It does not replace diagnosing the actual error.
Record the exact error and file details
Before changing settings, make a short record of the failure. Copy the complete message exactly as shown, including any file name, code or surrounding detail. “Unsupported video codec” is not enough to identify the failing layer, and the supplied title alone does not tell us which error you saw.
For a local file, note its name and extension, the video codec, the audio codec, the OBS version and your operating system. Record the source type in OBS too: Media Source, VLC Video or Browser. If the message appears only after a particular item in a playlist, note which item and whether the earlier files played normally. For a YouTube upload, note what stage failed: selecting the file, uploading, processing or playback after processing.
The extension is useful but does not reveal everything inside a file. An .mp4 suffix identifies a container, not necessarily the exact video and audio streams it contains. Two files ending in .mp4 may use different codecs, profiles or other stream properties, and may not behave alike in the same player. Inspect the file's stream information rather than treating its name as a complete diagnosis.
Also note whether the same file plays in another player. This is a comparison, not a guarantee that OBS will play it: applications can use different media libraries and support different combinations of formats. Keep the original file unchanged while testing, and write down one change at a time so you can tell which result followed from which action.
Check whether the file plays in another player
Open the same local file in a known media player and see whether video and audio both play from beginning to end. If it fails there as well, the file may be incomplete, damaged or encoded in a way that the player does not support. That does not yet say which of those explanations is correct, but it makes an OBS-only source setting less likely to be the first thing to change.
If it plays in another player, compare that result with the OBS test. Check whether the issue affects every file or only one, whether the sound plays without the picture, and whether playback stops at a particular point. A single troublesome item in a playlist points you towards inspecting that file; a source that cannot open any items may warrant checking the source type, installed dependencies and OBS configuration first.
A media inspection tool can report the actual video and audio codec names and other stream details. Use those details to compare files that behave differently. A container conversion by itself may not help if the unsupported part is the codec inside it. Conversely, re-encoding every file before you know which one fails adds work and can reduce quality without addressing a source-selection or playlist problem.
For channels built around a rotating set of prerecorded tracks, the playlist mechanism matters as well as the media format. The guide to making a 24/7 Punjabi bhangra stream from an M3U playlist discusses the playlist side of that kind of channel. Here, keep the test narrower: establish that each local file plays and that OBS is using a source that supports the behaviour you expect.
For local playlists, try OBS VLC Video
When you want OBS to play a playlist of local media files, add a VLC Video source rather than assuming that Media Source will provide playlist controls. OBS's documentation says VLC Video uses VLC libraries for extended media support over the built-in Media Source, and identifies it as the playlist-capable source. This makes it a sensible next test for a local playlist; it does not promise that every file or codec will work.
VLC Video depends on VLC being installed. OBS also notes that if you are using 64-bit OBS, you must install 64-bit VLC. If the source type is missing from the add-source menu, check the VLC installation and match its architecture to OBS before investigating the media files further. Restart OBS after installing a missing dependency, then check whether VLC Video is available.
In the source properties, add a small test playlist containing the file that failed, or one known-good file and the failing file. Confirm the playlist behaviour you need and observe which item stops. Avoid changing a whole production scene at once. If the test works, add the remaining items in manageable batches and watch for a specific file that causes the failure. If the same file still fails, record that result and inspect its streams individually.
The OBS documentation's extended-media-support description is not a universal compatibility guarantee. VLC Video may solve the playlist-source mismatch while still failing on a particular file. If you have a devotional video that plays in a desktop player but not in the VLC Video source, for example, the next step is to compare the actual streams and OBS/VLC setup, not to assume that installing VLC fixes every unsupported-file case.
For more on the difference between playlist and long-running channel decisions, see how a prerecorded-audio YouTube radio channel can use a static image. Keep the scope in mind: an audio-and-image workflow is not the same as troubleshooting a video file, but the local playlist and continuous-broadcast choices can affect how you organise source material.
For uploads, verify the actual codec and container
If the failure happens while uploading to YouTube, inspect the file and compare it with YouTube's own recommended upload encoding settings. YouTube recommends an MP4 container with H.264 video, progressive scan and a frame rate matching the recording. Its guidance lists AAC-LC, Opus or Eclipsa Audio for audio and a 48 kHz audio sample rate. Check the current official page for the full recommendations before preparing a new export.
Those recommendations concern upload encoding. They are not a direct fix for an OBS source that cannot open a local playlist item. Likewise, YouTube's published upload recommendations do not establish that a file with a different format is automatically the reason a particular upload failed. Use the exact YouTube error and the file's stream information together before deciding whether to export again.
A container and a codec answer different questions. The container packages streams and related data in a file; codecs describe how audio or video is encoded. Changing a file's extension does not convert its streams. A container remux may help with a container compatibility issue, but it will not turn an unsupported video codec into H.264. Re-encoding does that, and it can take time and change image or sound quality, so keep the original and choose settings for the intended upload.
OBS's audio and video formats guide describes container trade-offs in the context of recording. It calls MKV flexible and resilient for recording, while MP4 and MOV offer broad compatibility with downstream editing and upload workflows; regular MP4 and MOV need finalisation. This is useful background when you are choosing a recording format, but an OBS recording-container recommendation is not the same thing as YouTube's upload-encoding recommendation.
| What you are checking | What to inspect | What the result helps you decide |
|---|---|---|
| Local playlist in OBS | Source type, file-specific video and audio streams, and whether VLC Video is available | Whether you have a playlist-source issue, a dependency issue or a particular file to investigate |
| YouTube upload | YouTube's full error and the actual container, video codec, audio codec and export settings | Whether a new export aligned with the current upload recommendations is worth testing |
| OBS recording for later use | Recording container and where you will edit or upload the file | Whether recording resilience or downstream compatibility is the more relevant priority |
| YouTube shown in a Browser source | Page behaviour and the exact browser/playback message | Whether the issue belongs to web playback rather than a local codec diagnosis |
Avoid copying bitrate figures or other export settings from a general guide without considering the source resolution, frame rate and intended output. YouTube labels its figures as recommendations, not guarantees. For a specific upload, start from the official page and preserve an original master so you can try a different export without losing the source.
Test one file and review the result
After the initial diagnosis, make a controlled test. For a local playlist, start with one file that failed and, if useful, one that played. Use the intended playlist-capable source, then play each item long enough to see whether video and audio begin and remain in sync. Record the outcome and any new error wording. If the test isolates one file, inspect or convert that file rather than changing every item in the rotation.
For an upload, make a new export only after you have checked the actual streams and the relevant YouTube recommendation. Upload that test file and note whether the original stage of failure changes. A file that completes upload but is still processing presents a different observation from one that YouTube rejects immediately. Do not treat an upload finishing as proof that every playback or quality issue is resolved.
If re-encoding is warranted, use an established conversion workflow that lets you select the output container and codecs explicitly. Match the output to the destination and source; do not apply an arbitrary command, bitrate or codec setting to every file. Keep a copy of the original and test the converted file before replacing the playlist copy. If the picture works but audio does not, inspect the audio stream rather than repeatedly changing the video codec.
Once the test behaves as expected, expand it gradually. Add the other playlist files, check the OBS scene after a restart, and observe a full transition from one item to the next. A file that works by itself may still expose a playlist-order or transition issue. For an always-on channel, this small check is more useful than assuming a setup is sound because a single clip played once.
If you are planning a channel that will run when your own computer is switched off, StreamNeo removes the specific need to keep a local OBS playlist running on that computer by turning an uploaded video into a YouTube live stream. That is a different operating approach, not a way to repair a file whose codec or upload compatibility still needs checking.
Keep browser-source playback errors separate
A Browser source displays web content inside OBS; it is not the same as loading a local video file through Media Source or VLC Video. If an embedded YouTube video shows an error, do not infer that its codec is unsupported by OBS. The supplied evidence for this article does not establish that a browser-source playback message is a codec error, and neither VLC Video nor conversion can be promised as a fix for it.
First confirm what the Browser source is meant to show and capture the full message. Check whether the same page plays in a normal browser, whether it asks for an account or interaction, and whether the issue is limited to that page. A page or playback problem that also occurs outside OBS points away from local file decoding. A page that works elsewhere but not in the OBS browser still needs browser-specific diagnosis; do not treat a local file conversion as the default response.
If the actual source is a local file, test that file directly in a media player and through the relevant OBS media source. If the actual source is a web page, keep the browser page and local-media tests separate. This simple split prevents a YouTube playback or page error from sending you into unnecessary conversion work.
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 an MP4 extension mean the file uses a supported codec?
No. MP4 is a container, and the video and audio streams inside it have their own codecs. Check the stream details rather than relying on the extension alone.
Why is VLC Video missing from OBS?
VLC Video depends on VLC being installed, so check that installation first. OBS's documentation also says 64-bit OBS requires 64-bit VLC; after installing the matching version, restart OBS and check the source menu again.
Should I convert every playlist file to H.264?
Not without identifying which workflow and file are failing. H.264 is part of YouTube's recommended upload profile, but that does not make it an automatic fix for local OBS playback or a browser-source error. Test the failing file and choose a conversion only when its actual streams and destination call for it.
Is a YouTube error inside an OBS Browser source a codec error?
Not necessarily. A Browser source is showing a web page, and its playback message does not prove that a local file codec is unsupported. Check the page behaviour separately from local media playback.