OBS can repeat a video or playlist, but that setting does not control when Windows sleeps. To keep a local OBS stream running, configure the media source to loop and set Windows not to sleep automatically during the broadcast; do not manually sleep or hibernate the computer while OBS is outputting.
These are separate jobs: OBS handles what plays, while the operating system handles the computer’s power state. Set up and test both before leaving a stream unattended.
Playback looping and computer sleep are different settings
A looping source tells OBS what to do when it reaches the end of a file or playlist. It does not mean the computer will remain awake. If Windows sleeps, OBS cannot continue sending a live encoder output as though the machine were still running normally. Streaming through sleep is not a supported workaround.
For one video, OBS’s Media Source has a Loop option. For a sequence of files, the VLC Video source can load a playlist and repeat it with Loop Playlist. The operating system’s power settings are separate from either source: automatic sleep, lid behaviour, and power-button behaviour are controlled in Windows.
That distinction helps narrow down the symptom. If the picture goes black while the computer and OBS remain active, check the source, file and playlist settings. If the computer itself has gone to sleep, investigate Windows power behaviour first. If OBS is awake but the stream loses frames or disconnects, that is a connection or encoding problem rather than a loop setting. The dropped-frame troubleshooting guide covers that separate problem.
Loop a single video or an OBS VLC playlist
For a single local file, add a Media Source to the scene, select the video file and enable Loop in the source properties. The source should be visible in the scene that is actually being output. Start playback and watch through the end of the file once to confirm that it begins again as expected.
For several files in a fixed sequence, add VLC Video, create or load a playlist, and enable Loop Playlist. VLC’s shuffle control is separate; leave it off if the order matters. This is useful when, for example, a study channel needs to show recorded lessons in a planned sequence rather than repeat a single long recording. OBS documents both source types and their playback controls in its Media Sources guide.
VLC Video also has visibility behaviour that matters when a source is hidden or placed on another scene. Depending on the configured behaviour, playback may continue, pause or stop when the source is not visible. Check that setting if a playlist appears to restart unexpectedly after a scene change, or if audio continues while the expected video does not.
Choose the source according to the job, not just the word “playlist” in the title of a tutorial. Media Source is the simpler built-in choice for one file. VLC Video adds playlist order and shuffle controls but requires a separate VLC installation. For a channel with several recurring segments, make the sequence explicit and test it in OBS before connecting to YouTube.
Install a compatible VLC version for the source
The VLC Video source depends on VLC being installed on the computer running OBS. If it is missing, the source may not appear in OBS. OBS’s documentation specifies that 64-bit OBS requires 64-bit VLC, so match the VLC installation to the version of OBS rather than assuming that any installed VLC copy will be detected.
Install VLC from its official download page, then restart OBS and look for VLC Video among the available sources. If it still does not appear, check whether OBS and VLC have matching 64-bit architecture and confirm that VLC finished installing. Do not replace a working Media Source setup with VLC merely to follow a playlist tutorial; a single file does not need the VLC source.
Before a long broadcast, check that every playlist entry points to a file that is still available on the computer. A playlist that refers to a moved, renamed or disconnected file cannot play it. Keep the files in a stable folder and avoid reorganising them after building the playlist. If the computer has more than one scene, make sure the playlist source is present and visible in the scene sent to the stream.
Adjust Windows power and sleep settings
On Windows, open the current power and sleep controls and set automatic sleep to stay off for the expected stream period. The exact path and labels can vary by Windows version, so use the system’s current Settings controls rather than following an old screenshot word for word. For a broadcast that should run overnight, confirm the setting for both plugged-in use and, if relevant, battery use.
A laptop needs particular attention. Closing the lid may trigger sleep even if the display timeout is harmless. Check the lid action and the power-button action in the current power settings, and do not close the lid unless its configured behaviour is appropriate for continued operation. A long local broadcast should normally run with the computer connected to power; battery depletion can stop the stream even if automatic sleep is disabled.
Windows power settings prevent automatic sleep according to the configuration you choose. They do not make a stream immune to every interruption: an update, power loss, network failure, user action or application problem can still stop output. The practical point is to remove the avoidable timeout first, then test the rest of the setup under the conditions you intend to use.
Microsoft documents an application API that can request an awake state, but its reference explicitly says that the function cannot prevent the user from putting the computer to sleep. That API is not a substitute for changing Windows settings or leaving the machine alone during output. For the source statement and its limits, see Microsoft’s SetThreadExecutionState documentation.
Avoid sleep or hibernation while OBS is outputting
Do not choose Sleep or Hibernate from the Windows menu while a stream is active. Do not rely on a lid close or power-button press being harmless. Those actions are different from automatic sleep after an idle timeout, and an awake request cannot override a user deliberately putting the computer to sleep.
The OBS project has discussed sleep during active output as destructive and unsupported in an issue about replay-buffer behaviour. Treat that discussion as a caution, not as a universal explanation for every failure: the specific symptom and operating-system configuration still matter. The safe procedure is straightforward. Stop the stream and close OBS before deliberately sleeping or hibernating the computer; if output must continue, leave the computer awake.
A monitor turning off is not the same thing as the computer sleeping. You can usually let the display go dark while the computer remains awake, but check that the chosen display timeout is not paired with a sleep timeout that ends the session. If you use a laptop with an external display, test the actual lid and display arrangement rather than assuming that an external monitor prevents sleep.
If the reason for choosing OBS is that you already have a local computer and want direct control of scenes, overlays or live changes, this approach keeps those controls in your hands, with the corresponding responsibility to keep the computer and connection running. If instead your main requirement is to have a file broadcast without keeping your personal computer on, StreamNeo removes that particular host-computer chore by turning an uploaded video into a YouTube live stream; it is YouTube-only and does not replace OBS scene control.
Connect OBS to YouTube Live and check the encoder settings
Create or manage the broadcast in YouTube Studio’s Live Control Room. YouTube provides a stream server URL and a stream key for the encoder connection. Enter those details in OBS’s stream settings, and treat the stream key like a credential: do not publish it or include it in screenshots, and reset it in YouTube if it is exposed.
The YouTube stream’s privacy, title and other metadata are separate from OBS’s loop settings. YouTube also documents optional encoder controls for starting and stopping a broadcast. Decide whether you want to start output from OBS or use the available auto-start behaviour, and check the current settings in YouTube’s encoder setup guidance and Live Control Room help. The exact interface can change, so confirm the controls shown in your account before relying on them.
A stream can be configured correctly in OBS and still fail to appear as intended on YouTube if the wrong stream is selected or its key does not match. Before leaving a channel running, confirm the preview and live status in Studio, then verify that the correct video is reaching the intended broadcast. If you are preparing a channel around recorded material, the guide to a 24/7 Hindi study stream offers a related planning example.
Test playback, power behaviour and the stream separately
Test each layer independently, then let the complete setup run long enough to expose ordinary mistakes. First test the local source in OBS: confirm sound and picture, wait for the file to end, and check that it loops. For a playlist, observe at least one transition between entries and confirm the order and visibility behaviour.
Next test Windows power behaviour while OBS is active. Set the computer up as it will be used for the broadcast, including its power connection, display timeout and lid position. Confirm that the machine remains awake when the display goes dark, and make sure that an automatic sleep setting will not end the session. Do not use a manual sleep test while output is active; deliberately putting it to sleep is not a supported stream state.
Then check the YouTube side. Confirm that OBS is connected to the intended stream and that YouTube shows the expected picture and audio. Watch for dropped frames or disconnects in OBS. OBS notes that a network connection unable to sustain the configured bitrate can cause dropped frames; a high-complexity scene or encoding load is a separate possible strain. If needed, simplify the scene, avoid unnecessary sources and review the bitrate against the connection. The no-gap highlights workflow is relevant when continuity between files matters, while the Windows update interruption guide addresses another cause of unattended interruption.
Write down what a successful test looked like: which scene was live, which source looped, whether the files advanced in order, and what YouTube displayed. That gives you a baseline for troubleshooting. If the picture goes black later, check source visibility and file availability before changing the bitrate. If the machine slept, revisit power, lid and button settings. If OBS stayed awake but the connection failed, investigate network stability rather than the playlist.
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 keep my computer awake while it streams?
Do not assume that OBS alone keeps Windows awake. OBS can loop media, but Windows power settings govern automatic sleep, and an application awake request cannot stop you from manually putting the computer to sleep. Configure the host for the session and avoid manual sleep or hibernation during output.
How do I loop a playlist rather than one video?
Use the VLC Video source, load the files as a playlist and enable Loop Playlist. VLC must be installed, and OBS’s documentation says 64-bit OBS requires 64-bit VLC. Leave shuffle off if the files must play in a fixed order.
Why did my stream stop even though the video was set to loop?
Looping only controls what happens when playback reaches the end; it does not prevent Windows sleep or fix a dropped connection. Check whether the computer slept, whether the source remained visible and its files remained available, and whether OBS reported dropped frames or a disconnection.
Can I manually sleep the computer and let OBS carry on?
No. Streaming through sleep is not supported, and Microsoft’s documented awake-state API cannot prevent a user from putting the computer to sleep. Stop the broadcast before sleeping or hibernating, or leave the host awake while output is active.