A YouTube live stream can loop a pre-recorded video without stopping when the file ends. In OBS Studio, add the file as a Media Source, enable Loop, keep that source visible in the scene being streamed, and test the end-to-start change before you go live.
Looping only addresses the point at which playback finishes. It does not by itself fix a hidden source, a file that fails to render, a lost connection, an incorrect stream key, or a blank output that appears only on the public watch page.
Why a looping source can still go blank
A local video normally has a clear end. If the source reaches that point and no repeat instruction is enabled, OBS may stop showing the media or display whatever behaviour its source properties specify. A live encoder can continue sending a scene while the scene itself contains no visible video, so YouTube may receive a valid broadcast with a blank picture.
OBS separates several settings that are easy to confuse. Loop tells a Media Source to play the file again after playback completes. Restart playback when source becomes active controls what happens when the source becomes visible or active again. The second setting does not replace Loop.
There are also several places where a blank frame can be introduced:
- The selected file may be the wrong file, damaged, or unsupported by the computer's media playback path.
- The source may be hidden in the scene, underneath another full-screen source, or outside the canvas after a transform change.
- The file may have completed with Show nothing when playback ends enabled.
- OBS may show the video correctly while the connection to YouTube has failed or is sending a different scene.
- YouTube may receive the stream while a viewer's watch page or device is having a separate playback problem.
That is why the first useful question is not simply whether the stream is black. Ask where the blank picture first appears: in the OBS preview, in YouTube Live Control Room, or only for viewers.
For a wider explanation of file preparation, see this guide to the best video format for 24/7 live streaming. The important point here is to separate playback completion from the rest of the delivery chain.
Loop one file with OBS Media Source
For one local video, OBS Media Source is the simplest documented setup. It keeps the file as one source in one scene, which makes the end-to-start transition easier to observe and troubleshoot.
- Open OBS Studio and create a scene for the broadcast. Give it a clear name such as
Main loop. - In the Sources panel, choose Add, then select Media Source.
- Create a new source and give it a descriptive name, such as
Main video. - In the source properties, select the local video file.
- Turn on Loop.
- Decide whether Restart playback when source becomes active suits the scene. It can be useful if you want the file to begin at the start whenever you return to this source, but it is not the setting that repeats the file.
- Check the other playback options, including the behaviour when playback ends, and avoid relying on an end-of-file setting as a substitute for Loop.
- Select OK, then confirm that the source is visible in the scene.
Fit the source to the canvas if necessary. In OBS, you can use the source's transform controls to fit it to the scene rather than assuming that the file's dimensions match your canvas. Watch the preview after adding it. You should see moving video and, where intended, hear the source audio through OBS's audio mixer.
Do not test only the first few seconds. A source can look correct when it starts and still disappear when it reaches the end. Let it play through one complete cycle before using it for a long broadcast. If the file is several hours long, use a short test copy made from the same export settings, or allow enough time for the real transition to occur.
A single file also has a practical limitation: its content repeats in the same order every time. That is suitable for a devotional visual, a shop information loop, a study background, or an ambience video. If you need several files in sequence, use the playlist method below instead of adding many unrelated sources and hoping their visibility states remain consistent.
Loop a playlist with VLC Video
OBS also provides a VLC Video source for playing a playlist. This is a separate source type from Media Source and requires VLC to be installed on the computer. It is useful when the channel needs several files in a defined sequence.
Add a VLC Video source from the Sources panel, then add the files or playlist entries you want it to play. In its properties, enable Loop Playlist. Review the order of the items and use the available playlist controls for the behaviour you want, such as shuffle where appropriate.
The choice between the two source types is straightforward:
| Choice | Fits when | Main trade-off |
|---|---|---|
| Media Source with one file | You want the simplest local-file loop | It repeats one file, so the content order does not change |
| VLC Video with a playlist | You want several files in sequence | VLC must be installed, and the playlist needs its own testing |
| Software encoder on a computer | You need OBS scenes and source controls | The computer must remain on and the upload connection must remain usable |
| Hardware encoder | You already use dedicated production equipment | It is a separate hardware path and is not required for this basic setup |
For a single file, Media Source gives you fewer moving parts. For a playlist, VLC Video avoids building a scene with a separate source for every clip. Either way, the source must remain visible in the scene that OBS is sending to YouTube.
A playlist can also introduce transitions that do not exist in a single file. One item may have different dimensions, a different frame rate, no audio, or a brief pause before the next item. Test the change between each type of content, not just the return from the final item to the first.
If your aim is a multi-video channel rather than one repeating file, the guide on how to stream a playlist of videos on YouTube Live covers the broader planning questions. The immediate black-screen check remains the same: watch the actual source through a complete changeover.
Keep the source visible in the live scene
A correctly configured loop can still produce a blank stream if the source is not part of the scene being sent. In OBS, a scene may contain several sources, and the eye icon or source order determines what is visible. A source underneath an opaque image or browser layer will not appear in the output even if its media is playing.
Select the scene you intend to broadcast and check the program preview. Confirm that the looped source is visible, fitted to the canvas, and not covered by another source. If you use a logo, lower-third, clock, or background, add those deliberately and check that they do not cover the video area.
Scene switching creates another common failure. You may test the loop in Main loop, then switch to Starting soon, Chat, or another scene before starting the stream. If that scene does not contain the video, YouTube will receive the new scene rather than the one you tested.
For a basic channel, one scene with one full-screen Media Source is easier to verify than a complex collection of scenes. You can add overlays later. First establish that the video remains visible through its entire cycle, then add one visual element at a time and check the preview again.
Keep the OBS audio mixer open as well. A picture that continues while the audio meter is silent may be a source-audio issue rather than a black-screen issue. Conversely, an audio meter moving beside a hidden video source does not mean viewers can see the intended picture.
Connect OBS and check YouTube's preview
Once the local playback is working, connect OBS to the YouTube broadcast. In YouTube Studio, open Live Control Room and create or select the encoder stream. YouTube's encoder setup guide explains where to find the server URL and stream key.
In OBS, open the streaming settings and enter the current YouTube server details and stream key. Treat the stream key like a password. If you create a new stream or YouTube provides a different key, confirm that OBS is using the key for the stream you are actually viewing in Live Control Room.
YouTube recommends RTMPS for encrypted ingestion. Match the encoder quality settings to the upload connection you have available, then use YouTube's encoder settings guidance when choosing a practical configuration. A more demanding output does not fix a looping problem and can make connection problems harder to diagnose.
Start streaming from OBS, but do not assume that the public page is ready immediately. Wait for the YouTube preview in Live Control Room. Look for movement, confirm that the picture is the intended scene, and check that the audio behaves as expected. If the preview is blank, stop and diagnose that stage before making the broadcast public.
YouTube's live-stream guidance recommends checking stream health, monitoring audio and video, and testing access on the watch page and a mobile device. Its live-stream tips are useful here because they treat the broadcast as a chain rather than only an OBS setting.
When you finish, stop sending content from the encoder and end the live event where YouTube requires it. YouTube says streams under 12 hours are automatically archived, while its DVR guidance says rewind may be limited or unavailable for streams longer than 12 hours. Do not treat a very long loop as having the same archive and rewind behaviour as a shorter stream.
Test the end-to-start transition
The most important test is the moment the file reaches its end. Start with the source visible in OBS and note the final scene. Keep watching through the transition until the first frames of the next cycle appear.
Look for four things:
- The picture remains visible or returns promptly when playback restarts.
- OBS still shows the source in the same scene rather than switching to an empty scene.
- The audio does not remain silent after the video restarts, if the file is meant to contain audio.
- YouTube's preview shows the same transition rather than a blank output that exists only in OBS or only on the watch page.
A brief change in picture at a file boundary is not automatically evidence of a network failure. The file may simply be handing playback back to its beginning. What matters is whether the source resumes as expected and whether the same output reaches YouTube.
For a playlist, repeat the test at the end of the final item and at least one change between ordinary items. A playlist can loop correctly while one individual file displays incorrectly. Check each item if the channel depends on reliable playback overnight.
Write down what you observe and where. For example: OBS blank at file end, OBS moving, YouTube preview blank, or YouTube preview moving, viewer watch page blank. This short note prevents you from changing the media source when the actual problem is the stream connection.
Do the test before scheduling a long broadcast. The point is not to claim that every computer and every file will render every transition without a black frame. The point is to expose the behaviour of your actual file, source, scene, encoder, and YouTube stream before viewers depend on it.
Troubleshoot remaining blank output
If the file is blank in OBS preview, start locally. Check that the selected file is the intended one and that it opens normally outside OBS. Confirm the source eye icon is enabled, the source is inside the canvas, and no opaque source is covering it. Check the playback position and confirm that the file has not already completed.
Then return to the source properties. Make sure Loop is enabled. If Show nothing when playback ends is enabled, OBS may hide the source after completion; that property does not create a loop. Restart playback when source becomes active also does not create a loop. These settings describe different events.
If OBS preview shows moving video but YouTube preview is blank, inspect the connection stage. Confirm that OBS is streaming to the selected YouTube event, that the server URL and stream key are current, and that OBS reports an active connection. Check YouTube stream health rather than changing the local file first.
YouTube's encoder help notes that a third-party encoder start error may require copying the current stream key into the encoder again. Its live-stream troubleshooting page is the appropriate place to check current messages and platform-specific steps.
If YouTube's preview works but viewers report a blank picture, inspect the public watch page yourself and check it from a mobile device. Confirm that the correct event and scene are being used. Monitor the live output and ask whether the issue affects all viewers or only one playback device or connection.
If the picture is visible but keeps stopping or degrading, look at stream health and the upload connection. Test with a less demanding encoder setting if the available connection cannot sustain the chosen output. This is a delivery problem, not something that enabling Loop can solve.
If the source works at the beginning but fails at a particular file boundary, inspect that file or playlist item separately. Try a short copy made from the same source material, check whether it contains the intended audio and video, and compare its behaviour in OBS. Do not assume that a blank transition is caused by YouTube when the same file also fails locally.
For recurring overnight problems, keep a simple record of the scene, file, time, OBS status, YouTube preview, and public watch page. That gives you a way to distinguish a repeatable media-source fault from an intermittent connection or viewer-device problem. The YouTube stream health troubleshooting guide is relevant when the local preview is stable but the delivered stream is not.
Choose the operating method that fits the channel
OBS is a good fit when you need local control of scenes, playlists, overlays, and audio. The trade-off is that the computer must stay on, OBS must remain open, and the upload connection must continue working. A power interruption, operating-system update, sleep setting, or local network change can affect the broadcast even when the media loop itself is correct.
A dedicated hardware encoder can suit an existing production setup, especially when several sources or physical inputs are involved. It is not necessary for a single local video loop, and it adds another device and configuration path to maintain.
A cloud-based workflow changes where the long-running job is handled. With StreamNeo, you upload the video once, add the YouTube stream key, and the broadcast continues without leaving your own computer running; monitoring and automatic restart address the specific burden of watching a local computer overnight. It remains important to test the source and YouTube preview, and it is intended for YouTube rather than other destinations.
The right choice depends on what you need to control. If you are still proving that one file loops correctly, begin with the simplest local setup. If the channel needs to run while nobody is available to restart a computer, compare the operating responsibilities rather than looking only at the playback setting.
A short pre-broadcast checklist
Before starting a long loop, confirm the following:
- The intended file is selected in Media Source, or the intended files are in the VLC playlist.
- Loop is enabled for a single Media Source, or Loop Playlist is enabled for VLC Video.
- The source is visible in the scene that will be sent to YouTube.
- The source fits the canvas and is not covered by another layer.
- OBS preview shows both the intended picture and intended audio.
- You have watched an end-to-start transition locally.
- The current YouTube server URL and stream key are in OBS.
- YouTube Live Control Room shows motion in its preview.
- Stream health is acceptable for the chosen encoder settings.
- The public watch page and, where practical, a mobile device show the expected output.
- You know how to stop the encoder and end the event when the broadcast is finished.
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 OBS Loop prevent every black screen?
No. Loop repeats a file after playback completes, but it does not repair a hidden source, a media-rendering failure, a lost upload connection, an incorrect stream key, or a YouTube playback problem. Check where the blank output first appears.
Should I use Media Source or VLC Video?
Use Media Source when you want one local file to repeat. Use VLC Video when you need a playlist, provided VLC is installed and you enable Loop Playlist. Test each file boundary in the playlist before relying on it for a long broadcast.
Why is OBS showing video but YouTube is showing black?
The problem is likely after local playback, so check the selected YouTube event, stream URL, stream key, encoder connection, and stream health. Start with YouTube's preview and current troubleshooting guidance before changing the media file.
Do I need to leave my computer on for an OBS loop?
Yes, an OBS workflow on your computer depends on the computer, OBS, and its upload connection remaining available. If you need the channel to continue without keeping that computer running, consider an operating method designed to run the broadcast away from your desk and test it before going live.