If OBS shows a black screen, first check whether you added the video file as a source or are trying to capture a separate player window. Media Source and VLC Video play a file inside OBS; Window Capture captures another application, and the right diagnosis depends on which workflow you intended.
There is no single setting that explains every black preview. The operating system, OBS version, file codec, source type and graphics hardware all matter, so work through basic checks and change one thing at a time rather than assuming the file is broken.
Identify how the video should enter OBS
Ask yourself: do you want OBS to play a video file in the scene, or do you want OBS to show a separate application that is playing it? For the first goal, add the file using Media Source or, when playlist support or an alternate decoding path is useful, VLC Video. For the second, use a capture source appropriate to the application and platform.
The distinction matters because a player window can fail to appear in a capture source even while the file plays normally in that player. That does not establish that the media itself is faulty. Conversely, adding a file as a Media Source does not capture the controls or interface of an external player.
The OBS Project describes Media Source as a way to add media files to a scene and VLC Video as a separate source that uses VLC libraries. An OBS forum discussion about a black VLC window illustrates why source selection matters: the exchange concerns capturing a VLC window, not a universal fix for a black Media Source. Treat it as a workflow example, not as a diagnosis for your setup.
Before changing anything, note the exact source name in the Sources panel and whether you added a local file, a playlist, or a player window. If you are building a continuous programme, it can also help to distinguish playback from scene organisation; for example, a scheduled playlist of OBS scenes is a separate layer from decoding the video currently in a scene.
Use Media Source for a local file
If your aim is simply to show an encoded local video, start with Media Source. Add it to the intended scene, select the file, then confirm that the source is visible and positioned where you expect. The OBS Project’s Media Sources documentation explains the source and its properties.
OBS lists extensions including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM for Media Source. An extension tells you the container or file type, not every detail of the encoded video and audio inside it. Two files with the same extension can use different codecs or profiles, and the extension list is not a complete compatibility table. If the basic checks fail, gather codec details instead of treating the suffix as proof that playback must work.
A source can also be present but not visible in the scene output. Check that its eye icon is enabled, that it is in the active scene, and that another source is not covering it. Select the source and look for its outline in the preview. These are straightforward scene checks, not evidence that any one of them caused the black image.
If the file has audio but no picture, note that difference. Audio-only output narrows what you should report, but it does not identify the cause by itself. If neither picture nor sound appears, record that too. Avoid replacing the file or installing a codec pack before you know what OBS is actually trying to play.
For a long-running channel, a local OBS workflow also means the computer and scene remain part of the operating setup. A checklist for preparing videos on a spare PC covers adjacent preparation decisions, but it does not replace checking the source and codec when a particular file renders black.
Use VLC Video when playlist support is needed
VLC Video is a distinct OBS source, not another name for Media Source. It relies on VLC libraries and can be useful when you need its playlist features or want to compare playback through a different source path. The OBS documentation notes that VLC must be installed for the VLC Video source to appear; 64-bit OBS requires a 64-bit VLC installation.
If you need VLC Video, install VLC from its official source and check that its architecture matches OBS. Then add VLC Video, choose the same file, and test it in the same scene. If the source is not available in OBS, check whether VLC is installed and whether you have matching 32-bit or 64-bit applications before looking for a deeper playback fault.
A file that displays through VLC Video but not Media Source has given you useful comparative evidence: the two source paths behave differently with this file on this setup. It does not, on its own, tell you the precise codec issue or prove that VLC Video is a permanent solution. Likewise, a black result in both sources does not prove corruption; you still need details about the file and software versions.
Use the same file and comparable scene conditions for the test. Avoid changing the file, source type, hardware-decoding option and graphics settings all at once. If several things change together, you will not know which observation is useful. The OBS media source guide is the best reference for the documented source choices; check it again if your OBS interface differs from instructions written for another version.
Confirm the selected file and source settings
Open the source properties and verify that the intended file path is selected. It is easy to test an older export or a similarly named file by mistake, especially when a folder contains several versions. If the file has been moved since the source was configured, browse to the current local copy and apply the change. Confirm that the file can also be opened in a normal standalone player, but treat that only as a comparison: success in another player does not establish how OBS will decode it.
Check the source’s visibility and scene placement again after selecting the file. A black preview can result from looking at a different scene, leaving a source hidden, or placing it behind another item; these checks do not establish any of those as the cause in your case. If the source is visible and the correct file is selected, keep those facts in your notes and move on to a controlled decoding test.
Media Source includes an optional setting called “Use hardware decoding when available”. It asks OBS to use the GPU for decoding when a suitable hardware decoder is available for the media. The OBS documentation gives the setting a default of Off. If you enabled it and the image is black, turn it off, apply the change and test again. If it was already off, do not assume that turning it on is the answer; suitability depends on the file and the available decoder.
This is a reversible test, not a universal remedy. A historical OBS issue concerning a WebM Media Source described a black screen with hardware decoding enabled on macOS 13 and OBS 28.1.2. That report supports checking the option in a comparable scenario, but it is specific to that older platform and version and should not be generalised to current systems.
Check the VLC dependency for VLC Video
When you compare with VLC Video, confirm that VLC is installed and that its architecture matches OBS. The source may not appear until VLC is installed, and an architecture mismatch can prevent the expected integration. Use the official VLC download or documentation to identify the appropriate installer for your system rather than downloading an unknown codec package.
If the source appears, select the same local file that you tested with Media Source. Keep a brief record of the outcome: image and sound, sound only, or neither. If playback differs between the two sources, report that comparison alongside the file details. It narrows the investigation to differences in how the sources handle playback; it does not establish exactly which codec, profile or setting is responsible.
VLC Video is not a promise that every file will work. If it also shows black, that is a reason to gather evidence, not to buy new graphics hardware or install a collection of codecs without a specific diagnosis. Before trying any change to VLC or OBS, preserve the original file and note the current source settings so you can return to the previous state.
Gather details before guessing
When the basic checks do not resolve the issue, collect enough information for someone else to reproduce it. Record the operating system and version, OBS version, VLC version if used, source type, file extension, and the actual video codec and profile if you can identify them. Include the graphics card and driver version, and whether hardware decoding was enabled for the test.
Also say whether the file plays in a standalone player, whether OBS receives audio, which scene and source you tested, and what changed between attempts. An OBS log from a session that reproduces the problem can be useful when asking for help; follow the OBS Project’s current guidance for collecting and sharing logs. Do not publish a stream key or other account credentials with a log or screenshot.
These details prevent a common dead end: receiving advice for a different source type or platform. A Windows Window Capture problem, for instance, is not automatically the same as a macOS Media Source decoding problem. If you ask in a support forum, state what you meant OBS to do, then list the exact steps and results rather than saying only “video is black”.
Keep the scope of the report precise. If the video is a local file played through Media Source, say so; if it is a captured application window, name the capture source. Include the filename’s extension but do not rely on that alone to identify its encoding. If you do not know the codec, say that it is unknown rather than guessing.
Test one change at a time
Use a small test sequence and write down each result. First confirm the source workflow, scene visibility and selected file. Then, if hardware decoding is enabled for Media Source, disable it and retest. After that, compare the same file using VLC Video if you need its playlist support or an alternate source path. Apply one change, observe the result, and restore it if the test does not help.
| Test | What to do | What the result can tell you |
|---|---|---|
| Source choice | Use Media Source for file playback; use capture only for a separate player window | Whether the original setup matched the intended workflow |
| Scene and file | Confirm the active scene, visibility and selected local path | Whether OBS is displaying the expected source and file |
| Hardware decoding | If enabled for Media Source, turn it off and retest | Whether this optional decoding path changes the result on this setup |
| VLC comparison | Test the same file in VLC Video with matching VLC architecture | Whether the two OBS source paths behave differently |
| Performance symptoms | Follow performance guidance only if output stutters or overload is reported | Whether a separate resource-load issue needs attention |
Do not turn a black still image into a performance diagnosis without symptoms that support it. OBS’s encoding performance guide addresses issues such as laggy output and overload, which are different from a static black file preview. If you also see stutter, skipped frames or overload warnings, follow that guidance as a separate branch; it may involve GPU load, scene complexity or output settings, but those are not proven fixes for a black file.
If the issue remains, take the collected facts to the OBS support channels or compare them with the current official documentation for your version. For a continuous YouTube channel, the playback computer is one possible source of overnight interruption; moving the file-based broadcast away from a computer that must stay on removes that particular operating burden. StreamNeo turns an uploaded video into a YouTube live stream, so you do not need to keep your own computer running for that broadcast.
If you are preparing a channel around recorded lessons, a guide to streaming recorded NIOS classes may help with the broader workflow. It is separate from diagnosing an OBS preview, and you should still verify that any file you plan to use plays as intended before building a schedule around it.
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 use Window Capture to play a video file in OBS?
No, not if your goal is simply to play the file in an OBS scene. Add the local file with Media Source, or use VLC Video when you need its playlist support or want to compare a second source path. Window Capture is for showing a separate application window.
Does a supported file extension guarantee that Media Source will play the file?
No. OBS lists file extensions for Media Source, but an extension does not tell you every codec or profile inside a file. If playback is still black, identify the actual codec and include it with your OBS and operating system details when asking for help.
Should I enable hardware decoding to fix a black screen?
Do not assume that enabling it will fix the problem. If it is already enabled, try turning it off and retesting as a reversible diagnostic; if it is off, keep it off for the initial comparison. The right result depends on the file and the decoding hardware available to your system.
What should I share if the black screen continues?
Share your operating system and version, OBS version, source type, file extension and codec if known, GPU and driver, VLC version if relevant, and whether audio plays. Include the steps you took and an OBS log from a session that reproduces the issue, following the current OBS guidance for logs. Do not include a stream key or other credentials.