OBS is the application sending your video to YouTube, but your computer’s operating system controls whether the machine sleeps. To prevent a 24/7 stream from stopping, change the relevant power settings on Windows, macOS or Linux, then test the same power source and display state you will use during the real broadcast.
A dark screen does not necessarily mean the computer has slept. The display can turn off while OBS continues running, whereas system sleep can pause the application and interrupt the broadcast. Start with the operating system’s power controls rather than looking for an OBS switch that the reviewed OBS documentation does not document.
Understand what controls sleep
OBS handles scenes, sources, encoding and the connection to YouTube. Its official overview explains the main streaming and recording controls, while its launch parameters include options such as starting a stream automatically. Those are useful for automation, but they are not the same as a system sleep policy.
The distinction matters because a 24/7 channel can fail even when OBS itself is configured correctly. If Windows decides that the computer should sleep after an idle period, the operating system may suspend OBS along with other applications. Changing an OBS source, playlist or bitrate will not normally change that operating-system decision.
There is also a difference between three states that are often treated as one:
| State | What happens | Effect on an OBS stream |
|---|---|---|
| Display off | The monitor or laptop screen turns off | OBS may continue streaming normally |
| Computer awake with display off | The system remains active but uses less display power | Usually suitable for an unattended stream, subject to testing |
| System sleep or hibernation | The operating system reduces or stops active processing | The stream may pause, disconnect or stop |
For a long broadcast, your aim is usually to let the display turn off while stopping the computer from entering sleep. Keeping the screen lit all night is not the same as keeping OBS alive, and it can use more energy than necessary.
Do not assume that any application request will cover every installation. The documented material reviewed for this article does not establish that every OBS version, operating-system release or configuration always prevents the host computer from sleeping. Treat the power policy as something you must set and verify.
This is separate from the content itself. If you are running a playlist, you may also need to check that videos progress as intended. The guidance in how to add multiple videos to an OBS 24/7 stream playlist addresses the playback side, while this article concentrates on the computer staying awake.
Change the Windows 11 sleep timeouts
On Windows 11, open Settings, then go to System → Power & battery → Screen, sleep, & hibernate timeouts. This is the control surface for the idle periods that govern the screen and the computer’s sleep behaviour.
You will normally see separate choices for when the device is plugged in and when it is running on battery. Expand the relevant controls and inspect both sets rather than changing only the first option you notice. A laptop that starts the stream while connected to its charger can still switch to a battery policy if the charger is loose, disconnected or no longer recognised.
For a machine dedicated to a continuous stream, set the sleep timeout for the plugged-in condition so that the computer does not enter sleep during the intended broadcast. You can set the screen timeout separately, allowing the display to turn off while the computer remains awake. The exact choices shown can vary with the Windows release, device type and policy applied by an organisation.
If Windows shows a separate hibernate timeout, inspect that as well. Hibernation is not simply a darker screen. It saves the system state and stops normal activity, so it can interrupt an unattended broadcast just as sleep can. The setting names and available choices may differ between devices.
After changing the values, close Settings and check them again. This simple confirmation can catch a change made under the battery heading when the stream will actually run under the plugged-in heading. It also gives you a known starting point before a test.
Microsoft’s Windows 11 power settings guidance is the best place to check the current labels and behaviour, because Windows updates and device policies can change what appears on screen. If a setting is missing or unavailable, the computer manufacturer or an administrator may be applying a power policy.
Do not use a permanently awake display as your first solution. It can hide the real issue, make the room brighter, and use more energy without proving that OBS would have stopped when the screen was off. Test the screen timeout and system sleep timeout independently where possible.
Choose plugged-in or battery behaviour
A 24/7 stream should normally be tested and operated with the computer connected to reliable mains power. Battery operation introduces another failure path: the battery can discharge, Windows can use a different sleep policy, or the computer can reduce performance to extend battery life.
Plug the charger directly into the computer and confirm that Windows reports the device as charging or connected to power. Do not treat the presence of a cable as proof that the machine is drawing power. A loose connection, overloaded adapter or faulty socket can leave a laptop running on battery without making the change obvious from across the room.
Then review the two Windows policy groups:
- On battery power: decide what should happen if the charger is removed. For an unattended stream, a short battery sleep timeout can stop the broadcast quickly, but leaving a laptop awake until its battery is empty is not a dependable fallback.
- When plugged in: set the sleep behaviour intended for the stream. This is the policy that should apply during normal operation, provided the charger remains connected.
You can usually allow the screen to turn off on either power source while keeping the computer awake for longer. That distinction is useful when you are monitoring a stream remotely and do not need the local display illuminated.
For a desktop computer, the battery heading may not be relevant, but still inspect the available settings. Desktop systems can have separate options for display timeout, sleep, hibernation and power-button behaviour. A physical power button or a mains interruption can stop the stream even when the idle timeout is correct.
If the stream is important, consider the whole power chain rather than only the Windows menu. The computer, charger, wall socket and network equipment all need to remain powered. This does not mean buying a particular accessory. It means identifying which single interruption would stop the broadcast and testing that arrangement before relying on it.
A laptop lid is another practical detail. Closing the lid can trigger a separate action, such as sleep, even if the normal idle timeout is configured correctly. Check the current lid behaviour in Windows before placing the computer in a closed position. If the computer must run with the lid shut, test that exact arrangement rather than assuming the open-lid test applies.
Understand application sleep requests
Modern operating systems can receive requests from applications that indicate ongoing work needs the computer to remain awake. Microsoft documents these as system-required requests that the power manager can consider when deciding whether to enter automatic sleep. That explains why some applications appear to keep a machine awake without a visible change to the normal timeout.
This mechanism should not be confused with a documented OBS setting. The reviewed OBS documentation covers streaming, recording and launch behaviour, but it does not document an OBS control labelled as a keep-awake or prevent-sleep switch. Nor does the Microsoft material establish that every OBS version creates an accepted sleep request in every configuration.
The practical consequence is straightforward: do not build a 24/7 plan around an assumption that OBS will always keep the computer awake. Set the operating system’s sleep policy explicitly, then test whether the actual OBS setup remains active after the idle period that previously caused trouble.
Application requests can also be conditional. An application may request continued activity only while a particular operation is running, while the operating system may reject or modify requests according to policy, power state or other conditions. A stream that is connected at one moment is not evidence that the same request will cover every later reconnect or playback state.
If the system reports that an application is preventing sleep, treat that as useful diagnostic information rather than a permanent guarantee. You still need to check the settings for plugged-in and battery use, confirm that the machine does not hibernate, and test after restarting OBS or Windows.
This is one reason a dedicated computer can become difficult to maintain. You may start with a stable scene collection, then discover that a Windows update, changed power plan or accidental charger removal alters the conditions. Record the settings that work, including whether the screen was off and whether the laptop lid was open, so you can restore them after maintenance.
Check other power settings
Sleep timeouts are the main setting, but they are not the only cause of an interrupted unattended stream. Check whether the computer has separate controls for hibernation, lid closing, power-button actions and screen timeout. The names may differ by Windows version or device manufacturer.
Review Windows Update and restart behaviour as part of your operating routine. A restart can stop OBS even when the power settings are correct. You should not disable important security updates casually, but you should know whether the computer is allowed to restart at night and choose a maintenance window that does not overlap your broadcast.
Also check whether the computer is managed by an employer, school or shared workspace. An administrator may enforce sleep or restart policies that you cannot change from the normal Settings page. If an option is greyed out or returns to its old value, ask the administrator or consult the device manufacturer’s documentation instead of repeatedly changing it.
Power-saving software supplied by a laptop manufacturer can add another layer. It may reduce performance, alter charging behaviour or change the active Windows power mode. For an unattended test, note the active mode and avoid changing several unrelated settings at once. Otherwise, you will not know which change affected the result.
Network behaviour deserves a separate check. Keeping the computer awake does not repair a Wi-Fi dropout, router restart or unstable upload connection. A successful power test should therefore be followed by a short observation of the YouTube live control room and the OBS status indicators.
The same principle applies to content. A stream can remain technically live while showing a frozen frame, an empty scene or a video that has ended. If your channel uses lectures, prayers, music or ambient loops, review the content workflow as well as the power workflow. For example, how to prevent a lecture playlist stream from repeating the same video deals with a playback problem that sleep settings cannot solve.
macOS and Linux need different checks
On macOS, Apple documents the option “Prevent automatic sleeping on power adapter when the display is off.” The menu location can vary between macOS releases, so open the current battery or energy settings on the Mac and look for that power-adapter behaviour. Use it while the computer is connected to power, then confirm that the display can turn off without putting the Mac to sleep.
Apple cautions that delaying or preventing sleep can increase power use. That is another reason to separate the screen setting from the computer sleep setting. If the Mac is in a warm or poorly ventilated space, observe it during the test rather than leaving it unattended immediately.
Apple’s current Mac sleep settings documentation should take priority over older instructions that mention a different System Preferences or System Settings layout. Do not copy a command from an unrelated macOS version unless you understand what it changes and have checked Apple’s current guidance.
Linux does not have one universal click-by-click route for this task. Power controls differ between distributions and desktop environments, and a command that is suitable for one setup may not apply to another. Identify the distribution and desktop environment first, then use the relevant official documentation.
If you are unsure which Linux setting controls idle sleep, ask for help with those two details included. “Linux” alone is not enough information to prescribe a reliable command. A wrong change can affect more than OBS, including display locking, suspend behaviour and power consumption.
Test the computer while streaming
OBS recommends testing your settings before a real stream. Make the test resemble the intended broadcast: use the same computer, charger, network connection, OBS profile, display timeout, lid position and content source. A test made while you are moving the mouse every few minutes does not test what happens when the machine is genuinely idle.
Start OBS and send the stream to YouTube using the normal workflow. Confirm that the preview and live status are behaving as expected, then let the display turn off if that is part of your plan. Do not use the keyboard or mouse during the idle period. Watch from another device if possible, because checking the local screen can keep the computer active.
The test should extend beyond the idle period that previously caused the interruption. If the stream used to stop after the screen timeout, wait through that timeout and the next expected sleep point. This is not a claim that a short test proves 24/7 reliability. It only checks whether the known failure condition still occurs under the chosen settings.
After the test, check both sides of the connection. In OBS, look for a continuing stream state and any reconnect messages. In YouTube Studio, confirm that the broadcast remains live and that the picture and audio continue. A computer can stay awake while the upload fails, so do not use power behaviour as a substitute for checking the stream itself.
Repeat the test after a restart if the machine will be restarted before the real broadcast. This catches settings that were not saved, applications that do not launch as expected, and scenes or sources that behave differently after a fresh start. OBS’s quick-start guidance is useful for checking the basic stream path before you add unattended operation.
Keep a short record of the result. Write down the operating system, power source, sleep timeout, screen timeout, lid position and whether the test was viewed from another device. If the stream later stops overnight, you will have a reproducible baseline rather than a collection of guesses.
OBS also notes that meeting compatible system requirements does not guarantee successful streaming or recording. Power settings are one part of reliability. Encoding load, upload stability, source playback and YouTube’s live connection all need their own checks.
Decide whether the computer should run unattended
Running OBS locally gives you direct control over scenes, sources and live changes, but it leaves the computer responsible for the entire broadcast. You need to maintain its power settings, keep the operating system available, and recover from a restart, charger problem or local connection failure.
That may be the right arrangement for a channel that needs frequent live editing. It can also suit a test channel where someone is already present. The trade-off is that the stream depends on a specific physical machine remaining configured and powered correctly.
If your content is already prepared as a video and you only need it to run continuously on YouTube, a cloud-based workflow can remove the need to leave your personal computer switched on. StreamNeo is designed for this particular hand-off: upload the file once, add the YouTube stream key, and let the broadcast run without keeping your own computer awake.
That does not remove the need to check the video, stream key, channel settings and YouTube status. It simply moves the sleep-related problem away from the computer you would otherwise leave running overnight. If you are comparing approaches, the guide to running a 24/7 music stream without OBS explains the wider trade-off between local OBS operation and a workflow that does not depend on an open desktop session.
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 have a setting that prevents the computer from sleeping?
The reviewed OBS documentation does not document an OBS-level keep-awake switch. OBS controls the stream, while Windows, macOS or Linux controls system sleep. Set the operating system policy explicitly and test the actual configuration.
Can I turn the screen off without stopping OBS?
Usually, the screen timeout and system sleep timeout are separate controls. You can configure the display to turn off while leaving the computer awake, but confirm this with an idle test because device policies and other settings can change the result.
Should I run a 24/7 OBS stream on battery power?
Use reliable mains power for a continuous stream where possible. Battery operation can introduce a different sleep policy, reduced runtime and a risk of the charger being disconnected. If you must test battery operation, test that condition separately rather than assuming the plugged-in settings apply.
How long should I test before starting the real stream?
Test beyond the idle period that previously caused the interruption, using the intended power source, display state, lid position and content. That can reveal a sleep problem, but no short test proves uninterrupted 24/7 reliability, so also monitor YouTube and OBS for connection or playback issues.