A black screen when playing 4K videos in OBS can come from the source path, local rendering, encoding, or the stream reaching YouTube. Start by checking where the video enters OBS and whether it is already black in the preview or a local recording; bitrate settings cannot fix a local playback problem.
There is no single fix that applies to every setup. The operating system, OBS version, file format, graphics hardware, and source type all matter, so work through small tests and note what changes before adjusting more settings.
Identify the OBS source type
First establish what OBS is displaying. If you added a video file directly, it should ordinarily be loaded as a Media Source or VLC Video Source. If you are showing a browser window, a desktop, or an application window, you are using a capture source instead; that requires a different diagnostic path, covered below.
In the scene, select the source and confirm that it is enabled and visible. Check its properties to make sure it points to the intended file or capture target. A source can be present in the scene but hidden behind another source, disabled with its eye icon, or outside the visible canvas. Check the source order as well: a full-screen colour, image, or browser layer above the video can make the video appear black even when it is playing underneath.
For a local file, confirm that the path still points to the file you mean to play. If you move a file after setting up the scene, a source may no longer find it. Open the file in a normal media player as a basic check that it exists and plays, but do not treat success there as proof that OBS can render it the same way. The player and OBS may use different playback components or graphics paths.
OBS documents Media Source and VLC Video Source as choices for local media. Their behaviour and available controls may differ, so avoid switching sources and changing several other settings at once. For a loop, also inspect the source's playback options and confirm that the file has not simply reached a blank point or ended. Compare a moment where you know the video should contain visible frames.
If the video comes from a playlist workflow rather than a single local source, distinguish the playlist tool from OBS itself. The guide to adding videos to a LiveReacting playlist describes a separate path for assembling a live playlist; it does not diagnose an OBS Media Source. Keeping that distinction clear helps you identify which application needs attention.
Test the local video in OBS
Before starting a YouTube broadcast, test the file locally in OBS. Open the scene and watch the preview while the file plays. Note whether the image is black immediately, appears only after playback starts, disappears after a time, or returns after a loop. Also note whether the audio plays. These observations narrow the possibilities, though audio without a picture does not by itself identify the cause.
Make a short local recording if practical, then review it in a media player. The comparison is useful because the OBS preview and the recording test related but distinct parts of the path. If both are black, concentrate first on the file, source, scene, and local rendering. If the preview looks right but the recording is black, investigate the recording or output configuration before changing YouTube settings. If both look right but the YouTube player is black, the outgoing stream or ingest path becomes more relevant.
Use a small, ordinary test file as a comparison rather than repeatedly altering the original. If that file displays, try a lower-resolution copy of the 4K material. OBS notes that displaying a 4K source may be unnecessary when the actual stream output is lower resolution or the source is being scaled down; a smaller file can reduce workload. If the smaller file works, that is evidence that the workload or media path differs, not proof that resolution alone caused the black screen.
Keep the comparisons controlled. Change one variable, test again, and write down the result. For example, record the source type, file, scene, whether audio plays, and whether the preview and recording show an image. A note such as “small test file works in a clean scene; original 4K file is black” is more useful than a list of settings changed together.
A prerecorded loop also depends on how the media is assembled and repeated. If the issue is actually a playlist repeating or advancing unexpectedly, that is different from a black source. The XSplit playlist troubleshooting guide concerns XSplit rather than OBS, but illustrates why the playback application and the symptom should be identified separately.
Reduce the scene to a simple Media Source test
Create a temporary scene with only one Media Source and the test video. Remove or hide animated overlays, browser elements, extra capture sources, filters, transitions, and other demanding elements for the test. Do not delete your working scene; duplicate it or make a separate test scene so that you can restore the original layout.
This is not just a tidy-up. Sources, filters, and scene complexity can consume resources, and OBS recommends limiting expensive sources when performance is a problem. A minimal scene answers a practical question: can OBS show this file when fewer other things are happening? If it can, add the removed elements back one at a time. The element whose return coincides with the black screen or instability is a useful lead, though you may still need to inspect its settings or resource use.
Check that the Media Source is visible, selected for the correct file, and positioned within the canvas. Temporarily use a straightforward transform rather than a complex crop or filter chain. If you use a colour correction, mask, scaling filter, or other effect, remove it for the test and reintroduce it later. A black result in a complicated scene does not tell you which layer or effect is responsible.
Use the small-file comparison here too. Test a known-working lower-resolution file in the minimal scene, then the intended 4K file under the same conditions. Keep the output settings unchanged during this local test. If only the 4K file fails, record its container and codec details if you know them; do not assume that the extension alone tells the whole story. If neither file works, return to source visibility, file selection, and the local OBS setup rather than tuning stream bitrate.
For channels that rely on long unattended loops, keep a simple diagnostic scene and a known-good test clip available. That gives you a comparison when the full show fails overnight, without dismantling a production scene while the channel is live. A stable local test is also useful before you schedule a playlist rotation or add complex overlays.
Separate local rendering from stream encoding
Keep playback and encoding as separate questions. OBS has to render the source into a scene, then encode the outgoing programme for YouTube. A black image already visible in the OBS preview is a local source or rendering symptom until evidence points elsewhere. Changing the stream encoder may affect how OBS encodes output, but it does not universally repair a black Media Source.
Use the preview, local recording, and YouTube player as checkpoints. If the preview and recording both show the picture but the YouTube stream does not, check that the correct OBS output is being sent and inspect YouTube's stream-health information. If the preview is correct and the recording is not, compare recording and streaming output configuration. If the preview is black too, start locally and avoid treating upload bitrate as the likely first fix.
Hardware encoding can move some encoding work from the CPU to a specialised component of the GPU. OBS discusses supported hardware encoding options in its hardware encoding guidance. That can be relevant when encoding performance is poor, but a change of encoder is not a general diagnosis for source playback. Change it only as a controlled test, and note the original setting so you can reverse the change.
YouTube's live encoder settings guidance is for the outgoing broadcast, not for decoding a file in the OBS preview. As listed in YouTube Help in September 2026, its H.264 recommendations for 4K/2160p are 42 Mbps at 30 fps and 50 Mbps at 60 fps. Match the recommendation to the actual output frame rate and encoder, and check whether your upload connection can sustain the chosen setting with headroom. These figures are ingest recommendations, not a requirement for local playback and not a remedy for a black preview.
If your stream output is below 4K while the local source is 4K, consider testing a lower-resolution copy. Scaling a large source down still asks the system to handle that source, whereas a smaller file may reduce work. Whether it helps depends on the setup, so compare the preview and performance rather than assuming the resolution mismatch is the cause.
Check OBS performance and stream health
When OBS reports rendering or encoding lag, or the picture stutters as well as going black, look at system workload before making a large batch of changes. Close applications that are using substantial graphics resources and simplify the scene. On Windows, OBS's encoding performance troubleshooting guide includes reopening OBS with “Run as administrator” as a quick step to try. This is Windows-specific guidance, not a universal instruction for other operating systems.
If symptoms continue, test a lower output resolution or frame rate, disable costly filters, and reduce scene complexity one change at a time. Note whether the preview becomes visible, whether rendering or encoding warnings change, and whether the local recording improves. Reverting a change that makes no difference keeps the diagnosis understandable.
For a live test, use YouTube's stream-health indicators alongside OBS statistics. YouTube recommends testing in advance with representative audio and motion and monitoring stream health during the event. A local preview that is good while the stream-health panel reports trouble suggests attention should shift to the outgoing path; it does not mean that a specific bitrate or encoder setting must be the cause. For more context on the network side, see the 4K live streaming internet requirements guide.
Do not confuse dropped frames, encoding lag, and a black local source. They describe different observations. Compare what is actually black and where: OBS preview, local recording, YouTube player, or more than one of them. If motion freezes but a frame remains visible, that differs from a fully black picture. Likewise, audio continuing while video is black is worth recording as evidence, not a diagnosis in itself.
A 24/7 channel also has operational risks beyond the video file. If a local OBS machine is responsible for the broadcast, a power interruption or computer sleep can stop the stream even after the media problem is solved. The power-cut planning guide for an ambience stream in India covers continuity planning separately from OBS rendering.
Diagnose browser or desktop capture separately
If the source is a browser, desktop, or application capture rather than a local video file, do not apply Media Source fixes as though the file were the source. Confirm that the intended window or display is selected, that the source is visible, and that another window or layer is not covering it. Check the source properties and capture method available in your version of OBS; the labels and behaviour can vary by operating system and version.
For a browser source, first test a simple page with visible content and no unnecessary animation. For a display or window capture, check whether the capture target changes when the application is minimised, moved to another display, or switched to full-screen. These are diagnostic comparisons, not guarantees: capture behaviour depends on the operating system, graphics setup, and OBS version. Avoid assuming that a black capture has the same cause as a black local media file.
If the browser or desktop is black in the OBS preview and in the recording, focus on the capture source and its target before adjusting stream bitrate. If the preview is visible but the YouTube player is not, return to the encoding and ingest branch. A useful record should say precisely which capture source you used and what was visible on the computer outside OBS.
For a long-running prerecorded channel, repeatedly troubleshooting a home computer can itself be the operational burden. StreamNeo removes the need to leave that computer running for a file-based YouTube loop: you upload the video, provide your YouTube stream key, and the broadcast can continue with your computer off, with monitoring and automatic restarts if it drops. It is YouTube-only, so it is not a solution for a desktop capture, browser interaction, or a diagnosis of why a particular file renders black in OBS.
Gather evidence before escalating
If the simple scene and controlled comparisons do not isolate the issue, stop changing settings at random. Record the operating system and version, OBS version, graphics hardware and driver if known, source type, file container and codec if known, and whether audio plays. Note exactly whether the preview, local recording, and YouTube player are black, and whether a smaller test file changes the result.
Save an OBS log from the session that reproduces the problem. Include what you changed immediately before the test and any performance warnings OBS showed. This gives support volunteers or your technical colleague a traceable starting point. OBS provides a help portal with support material and links to community help; describe the evidence rather than asserting a cause you have not established.
For a YouTube-side issue, also note the stream-health status and the output resolution, frame rate, encoder, and bitrate. Keep these separate from local playback observations. If the local preview and recording are healthy, those outgoing details matter; if they are black too, the local file and scene remain the stronger place to investigate first.
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 is my OBS Media Source black but the audio still plays?
Audio and video can fail at different points, so sound continuing does not identify one cause. Check that the source is visible and points to the intended file, then test the file in a one-source scene and compare a small known-working clip. Note whether the preview and local recording are both black before changing encoder or bitrate settings.
Can changing bitrate fix a black screen in the OBS preview?
Usually, bitrate is relevant to the outgoing stream rather than local source playback. If the OBS preview itself is black, first check the source type, file path, scene visibility, and local rendering. Use YouTube's bitrate recommendations only when configuring the stream output, matched to its actual resolution and frame rate.
Should I convert the 4K video to a smaller file?
A smaller-resolution copy is a useful comparison when the stream output is lower resolution or the source is scaled down. If it works while the 4K file does not, that narrows the investigation but does not prove resolution alone is responsible. Preserve the original and change one test condition at a time.
What should I send when asking for OBS support?
Include your operating system and OBS version, source type, file details if known, graphics hardware and driver if known, and an OBS log from a session that reproduces the issue. State whether audio plays and whether the preview, recording, and YouTube player are black. That evidence is more useful than a list of fixes tried without recording their effects.