If OBS cannot open a video file, start by checking its Media Source settings and the exact local file path. Then inspect the media inside the file; a familiar filename extension does not by itself prove that OBS can decode it.
This is a local playback problem in your OBS scene. A YouTube stream key, ingest setting or network connection will not make a file that fails in OBS start playing, so resolve the source first and test the scene before going live.
Confirm the problem is local file playback
Look at where the failure occurs. If the video is meant to appear in an OBS scene and the Media Source preview is blank, shows an error, or plays audio without its picture, the first task is to diagnose that source on the computer running OBS. If the file will not play in another local player either, that is useful evidence about the file, but it still does not establish exactly what is wrong with it.
Separate the source test from the broadcast test. Open the scene in OBS and check whether the video appears and plays there. You do not need to start a YouTube broadcast just to establish whether OBS can read a local file. Conversely, if the local preview works but viewers cannot see the programme after you go live, that is a different stage of the workflow and deserves separate diagnosis.
This distinction matters when you are preparing a continuous devotional programme, a study loop or a local news sequence. A scene may contain several sources, and the missing picture may be a hidden source, an incorrect scene, or a file that was moved—not necessarily a YouTube problem. Confirm that the scene you are testing is the one that contains the video, then isolate its file source before changing unrelated streaming settings.
For a channel built from recorded material, the broader workflow is covered in whether you can stream pre-recorded videos on YouTube Live. Keep that question separate from whether a particular file opens in OBS: one concerns the format of the broadcast, while the other concerns local playback.
Choose Media Source for a local file
For one local video or audio file, add an OBS Media Source to the scene. OBS describes Media Sources as the source type for adding audio and video files, and its Sources Guide explains how sources are added to a scene. A Media Source configured with a local file is the direct route to test before looking at alternatives.
Open the source properties and check that the local-file option is selected. Browse to the intended file rather than assuming that the path saved in an old scene still points to the right place. If you are creating a fresh test, add a new Media Source and select the file through the file browser. Give the source a recognisable name, such as “intro video test”, so it is clear which item you are checking in the Sources list.
A source can exist in a scene without being visible or active in the way you expect. Check its visibility, position in the source stack and any other scene items that could cover it. These checks do not change the file itself, but they help distinguish “OBS did not open this file” from “OBS opened it, but the scene is not showing it”. If the source properties identify a file and the preview remains empty, continue with the path and media details.
The Media Source properties also include playback behaviour, such as whether to loop or restart when the source becomes active. Those choices affect what happens after playback starts; they are not substitutes for selecting a readable file. First establish that the source can show the video, then set the behaviour needed for your programme.
Verify the selected path and file
A surprisingly common explanation is that the source points somewhere other than the file you intended. The file might have been renamed, moved from Downloads to another folder, copied to removable storage that is no longer connected, or replaced by a second version with a similar name. Read the path shown in the Media Source properties and compare it with the file you meant to use.
Use the file browser to select the current copy directly. Avoid relying on a shortcut or a remembered location when you can verify the actual file. If your media lives on a removable drive, confirm that the drive is mounted and available under the same path. If the file is in a cloud-synchronised folder, check that its contents are downloaded locally rather than represented only by an online placeholder.
Check the file name and size in the operating system as well. A name that ends in .mp4 could still refer to the wrong version, an incomplete download or a tiny placeholder. Compare it with the copy you expect to use. If you have another known-good copy, test that copy separately instead of overwriting the original while diagnosing.
When you relink a file in an existing scene, verify that the source properties retain the intended path after you close and reopen them. The aim is not to infer a codec issue from a missing path: first establish that OBS can reach the exact file. Keep an untouched copy of the original while testing, especially if the video is the only copy of a finished programme.
For a prepared continuous stream, a stable, clearly named local copy is easier to revisit than a file buried among temporary downloads. The practical target is simple: the source should point to the file you can open and identify, in a location that remains available when you run OBS.
Check the extension and inspect the media
Once the path is correct, look at the extension. OBS’s Media Sources documentation lists video extensions including .mp4, .ts, .mov, .flv, .mkv, .avi, .gif and .webm, and audio extensions including .mp3, .aac, .ogg and .wav. See the OBS Media Sources reference for the list. These extensions are a useful first check, not a guarantee that every file bearing one will play.
A media file has a container and one or more encoded streams inside it. The extension usually gives a clue about the container; it does not reveal the actual video and audio codecs with certainty. Two files ending in .mp4, for instance, can contain different encodings. If the extension appears supported but OBS still does not play the file, inspect its media information with a media-inspection tool or a player that reports stream details. Record the container and the video and audio codecs rather than guessing from the suffix.
Compare those details with the OBS Audio/Video Formats Guide. Its compatibility table documents combinations of containers and codecs supported by OBS. Treat the table as a guide to combinations, not a guarantee for every file, operating system or decoder setup; inspection is what lets you ask a specific question about this file rather than a general one about .mp4 or .mkv.
If the inspected combination is not listed, or the file behaves differently in another player, you have evidence to investigate compatibility or file integrity. If the combination is listed, that is not proof the file is healthy; it may still be incomplete or damaged. Preserve the original and, if possible, compare a known-good file encoded the same way. Avoid changing the filename suffix as a supposed fix. Renaming .mov to .mp4, for example, does not re-encode the media inside it.
Do not pick a codec or conversion setting before you know what the file contains and what OBS can accept. The right decision follows from the inspection: use the native source if it works; try an alternate playback route where appropriate; or make a converted copy in a documented supported combination if evidence points to a compatibility problem. For a conversion workflow that keeps the output aligned with your OBS project, see how to transcode videos to the same resolution and frame rate for OBS. That is a separate choice from simply changing an extension.
Test a supported file in OBS
A small controlled test can show whether the issue is specific to one file. Add a short video you already know plays in OBS as a separate Media Source, leaving your original source intact. If the test plays but the problem file does not, the evidence points towards the original file, its path or its media combination—not towards every Media Source in the scene.
If neither the known-good file nor the original plays, return to the source configuration. Confirm you are testing the intended scene, that the source is visible, and that each source points to the correct local file. You can also create a clean scene with only the test Media Source. This removes other scene items from the diagnosis without making changes to your live scene.
Change one thing at a time and note what happened. For example, record that the known-good file played in a clean scene, while the original did not play after its path was reselected. That is more useful than changing the extension, installing extra software and altering scene settings all at once, because you will know which test changed the result.
When a file does play in OBS, test the actual scene arrangement you intend to use. Check the picture, audio, looping or restart behaviour, and the transition into and out of the scene. A file opening in a simple test scene is a good checkpoint, not a reason to assume the full programme is ready. If you are building a loop of several pieces, test each file and the sequence rather than extrapolating from one successful sample.
The distinction between source playback and broadcast checks remains useful later. Once the local scene behaves as intended, move on to whatever checks apply to your YouTube broadcast. If the problem is instead a platform status message, the separate YouTube Stream Health Check troubleshooting guide addresses that situation; it is not a remedy for a file that fails in the OBS preview.
Consider VLC Video when playlist support is needed
OBS also offers a VLC Video source, which uses VLC libraries for extended media support. It is worth considering when you need playlist-style playback or when the native Media Source route is not suitable for a particular file. OBS documents that VLC must be installed for this source type, and that 64-bit OBS requires 64-bit VLC. Check the current OBS Media Sources documentation before setting it up.
This is an alternate playback route, not a promise that VLC will play every file. It adds a dependency: VLC has to be installed with the matching architecture, and your scene must use the VLC Video source rather than the ordinary Media Source. For a single file that already works natively, there is little reason to add that extra step. For an ordered set of clips where playlist behaviour is needed, it may fit the task better.
Test the VLC route with the same file and note whether the outcome changes. If it plays there, you have learned that this alternate source can handle the file in your setup; you have not established that every source or every machine will behave identically. If it does not play, retain your file inspection notes and continue from the actual codec/container details rather than cycling through random extensions.
For playlist use, check the order, transitions and repeat behaviour before relying on it for an unattended programme. A playlist can help organise several local items, but it cannot correct a missing file or make a damaged file complete. The right source depends on the job: a single stable file is straightforward in Media Source; a playlist requirement can justify testing VLC Video.
Record details before further diagnosis
Before making more changes, write down what you have established. Include the OBS version and operating system, the source type, the path or a safe description of where the file sits, the exact extension, the reported container and codecs, and what happened in a clean test scene. Note whether another local player can play it, but do not treat that alone as proof of OBS compatibility.
Keep the error text exact if OBS displays one. “Blank preview” and “file could not be opened” are different observations. Also note whether audio is present without video, whether playback begins and then stops, and whether the failure happens only after restarting OBS. These details narrow the next step without pretending that a symptom identifies a single cause.
If you decide conversion is warranted after inspection, retain the original and test a new output file. Choose a combination shown as supported in the OBS format guide, and verify the converted file in OBS before replacing anything in your scene. A conversion can alter quality, file size or processing time, so avoid doing it just because a filename looks unfamiliar. If you are not sure what the inspection report means, share the actual details with a knowledgeable technician or ask in an appropriate support forum rather than guessing.
For an always-on channel, a recurring local playback failure also raises an operational question: who or what can restore the programme if the computer is unavailable? StreamNeo can remove the need to keep your own computer running for a file-based YouTube broadcast, but it does not diagnose or repair a source file that OBS cannot open. Resolve the media issue first, and only then decide how you want to run the channel.
When the local file and scene are behaving as intended, consider the operating arrangement separately from the file diagnosis.
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
Why does OBS not open my MP4 file?
The .mp4 extension identifies a container, not necessarily the video and audio codecs inside it. Check the Media Source path first, then inspect the actual container and codecs and compare them with OBS’s compatibility guide. The file could also be incomplete or damaged, so do not assume that every MP4 has the same cause.
Will renaming the file extension make it work?
No. Changing the filename suffix does not convert the media inside the file. Inspect its format first; if conversion is necessary, create a new copy in a supported combination rather than disguising the original with a different extension.
Should I use VLC Video instead of Media Source?
Use Media Source as the direct test for an individual local file. Consider VLC Video when its extended media support or playlist handling is relevant, and remember that OBS documents VLC as a prerequisite with matching 64-bit architecture for 64-bit OBS. Neither source is guaranteed to play every file.
If it plays locally in OBS, is the YouTube stream problem solved?
It confirms that the tested OBS scene can play that file locally; it does not test the complete broadcast or establish that viewers will receive it. Check the full scene, then diagnose any separate YouTube broadcast issue on its own evidence.