A display turning off does not necessarily mean your computer has gone to sleep. To keep OBS streaming to YouTube, let the display turn off if you want, but make sure the computer itself stays awake for the length of the broadcast.
The important qualification is that an awake computer does not guarantee every OBS source will keep producing a picture when a monitor powers down. Set the power behaviour for your operating system, then test the exact source and monitor arrangement you plan to use before leaving a stream unattended.
Display timeout is not computer sleep
Your computer has separate behaviours for its display and its own sleep state. A display timeout switches off the screen after a period of inactivity; system sleep suspends much of the computer’s activity. OBS can only keep sending an encoded stream while the computer remains awake and its capture, audio, network and encoding paths continue to work.
That distinction is easy to miss because both events can follow a period without keyboard or mouse activity. If the computer sleeps, OBS may stop sending video to YouTube. If only the display turns off, OBS may continue running, but the result depends in part on what the scene captures. A display-capture source is not the same as a media file or camera source, and no single power setting proves that every source will behave as intended.
For Windows 11, Microsoft provides separate controls for when the screen turns off and when the device sleeps. On a Mac, Apple documents an option that prevents automatic sleep while connected to power with the display off. Those settings address the computer’s sleep behaviour; they are not universal capture-source fixes. See Microsoft’s Windows 11 power settings and Apple’s Mac sleep settings for the current labels and guidance.
Start by identifying what “stopping” means in your case. Is OBS no longer reporting an active stream, or is OBS still connected while the picture is black or frozen? Those are different symptoms. The first points towards sleep, connectivity or encoding; the second can point to the source or graphics path even if the computer is awake.
Set separate screen and sleep times in Windows 11
Open Settings > System > Power & battery > Screen, sleep, & hibernate timeouts. The exact wording may change in a future Windows update, so use Microsoft’s current support page if a label does not match. You should see separate controls for turning off the screen and putting the device to sleep.
Choose the screen-off interval you actually want. Then set Make my device sleep after to Never, or to a time later than your planned stream, particularly for the plugged in condition. If you stream on battery as well, check that condition separately: a setting for plugged-in use does not necessarily apply when the charger is removed. For an extended stream, leave the computer connected to power and verify that it remains connected.
“Never” is a deliberate trade-off rather than a requirement for every session. It avoids an automatic sleep timeout ending a long broadcast, but the computer stays awake until you put it to sleep or change the setting. If you choose a finite timeout instead, make it longer than the planned stream, allowing for setup time and any delay before you stop OBS. A short timeout that is safe for ordinary desk work may interrupt a broadcast that is still running.
After changing the controls, check them again while the computer is plugged in. Power modes, device policies and other settings can affect what is available. Do not assume that shutting the lid will behave like an ordinary screen timeout; lid-close behaviour depends on the device and its configuration. If the setup uses a laptop with its lid open and display off, test that particular arrangement rather than inferring how it will behave from the timeout setting.
This is the system-level fix for a Windows machine that is actually sleeping. If your computer stays awake but the stream image disappears when the display turns off, do not keep changing sleep timers at random. First establish whether OBS is still connected, then check whether the selected source can keep capturing in that state.
Keep a Mac awake with its display off
On a Mac laptop, open System Settings, go to Battery, and look under Options. Apple documents the setting “Prevent automatic sleeping on power adapter when the display is off.” Enable it when you want the Mac to remain awake with its display off while it is connected to power. On a desktop Mac, check the relevant Energy settings in System Settings; names and placement can differ by model and macOS version.
The phrase “on power adapter” matters. Apple’s documented option is specifically about preventing automatic sleep on power when the display is off. It is not a general promise that the Mac will remain awake in every power condition, nor does it control what a particular OBS source captures. If you unplug a laptop, change its power condition or use a different macOS version, verify the applicable settings rather than assuming they carry over.
For a long stream, keep the Mac on its power adapter and confirm the setting is enabled. Then test the screen turning off while OBS is broadcasting. A Mac can remain awake while the display is off, yet an external monitor powering down can still affect a display-capture source. Apple’s power option addresses automatic sleep; it does not certify that a captured image remains available.
If you are deciding between a media source and display capture for a recorded loop, the distinction can affect how much the stream depends on the visible desktop. The guide to streaming MP4 videos continuously from a VPS in India discusses a different way to run recorded content continuously. It is useful context when the goal is a video loop rather than a live desktop, but it does not replace testing your own OBS scene.
Weigh the Mac power trade-off
Apple warns that preventing sleep can increase power consumption. The setting is useful when the Mac must keep OBS and the broadcast running with the display off, but it means the computer is not entering its lower-power sleep state under that condition. For a laptop, plan on it being connected to power during the stream rather than relying on battery life.
The practical balance is straightforward: switch off the display if you do not need to see it, but allow the computer to stay awake only for as long as the stream needs. When the broadcast is finished, stop it properly and restore a sleep setting that suits ordinary use. If you use a temporary power profile or setting, write down the change so it is not accidentally left in place after the session.
A desktop’s energy use and a laptop’s battery draw are different concerns, but the principle is the same. The Apple warning does not quantify the increase for your particular Mac, so do not plan around an assumed amount. If power consumption is a concern, test the setup for a representative session and monitor the machine’s power behaviour. Avoid leaving a computer awake indefinitely simply because it once hosted a stream.
Check what your OBS source depends on
A scene can contain sources with very different dependencies. A Display Capture source records the desktop. Window Capture targets an application window. A Media Source plays a file, while a camera source uses the camera input. A screen going off is not proof that all of these will continue working, and a black or frozen picture does not by itself prove the computer slept.
If you use Display Capture on a Windows laptop, graphics selection can matter. OBS’s laptop troubleshooting guide explains dual-GPU behaviour and display-capture compatibility, including the documented newer method’s requirements. Treat that guidance as a capture-path troubleshooting step, not as a universal fix for display sleep. If OBS remains active but the captured desktop becomes black or frozen, check the source and graphics path separately from Windows power settings.
The guide to OBS scene collections for separate YouTube channels can help you keep different broadcast setups organised. For this issue, note the source type in the scene you intend to run and test that scene unchanged. Switching to a different source for a quick check can be informative, but it does not validate the source you will actually use overnight.
Also consider the monitor arrangement. A laptop’s built-in display, an external monitor and a dock can behave differently when one screen powers down or disconnects. There is no universal claim that an HDMI dummy plug is needed, or that it solves system sleep; the reviewed guidance does not establish that. Change one thing at a time and record what happens so you can distinguish a power-state issue from a capture or graphics issue.
Test the exact setup before leaving it unattended
Make a low-stakes test using an unlisted stream or another appropriate test arrangement. Use the same computer, power connection, OBS scene, source types and display arrangement planned for the real broadcast. Confirm the stream starts in OBS and check the YouTube Live Control Room preview or status. Then let the display turn off using the timeout you configured.
Once the display is off, check the broadcast from a second device. Confirm that the picture continues to change where it should and that audio remains present. A static scene may look unchanged even when it is healthy, so choose a visible motion or other known signal if your content permits it. Check OBS’s own stream status too; YouTube’s preview alone may not tell you whether OBS is still sending or whether the last received frame has simply stopped updating.
If the test fails, separate the diagnosis into stages:
- Did the computer stay awake? Check whether OBS remains responsive and whether the system resumed from sleep. Revisit the relevant sleep setting and power condition.
- Did OBS stay connected? If its stream status stopped, investigate sleep, network and encoder behaviour rather than assuming the display timeout caused it.
- Did the picture fail while OBS remained active? Inspect the source, display arrangement and, on a Windows laptop, the GPU assignment and OBS capture guidance.
- What does YouTube show? Check the Live Control Room state and preview to see whether it reports a live, reconnecting or ended broadcast.
For a separate comparison of stream delivery problems, YouTube Live’s “excellent connection” message and viewer buffering explains why the broadcaster’s local status and a viewer’s experience are not the same signal. Likewise, troubleshooting packet loss on an Indian ISP is relevant if OBS disconnects despite the computer remaining awake. Those are different failure paths from display capture, but checking them prevents a sleep setting from becoming the explanation for every interruption.
Repeat the test long enough to cover the situation you expect: the display timeout, the planned stream duration and any routine that might change power state. This is a practical verification, not a guarantee of future behaviour. An operating-system update, a changed GPU driver, a new monitor, a different USB dock or a revised OBS scene can alter the setup. Retest after a material change, especially before a broadcast that matters to viewers.
Diagnose what stopped: OBS, the source or YouTube
When a stream fails, identify the last layer that was still working. If the computer slept, resolve the power configuration. If OBS is open and reports a live connection but the output is black, focus on the source and capture path. If the image and sound are fine locally but viewers report buffering, inspect network delivery rather than changing the screen timeout. This sequence is more useful than treating every interruption as “OBS stopped”.
There is also a broadcast-lifecycle setting in YouTube that can affect what happens after OBS stops sending. The OBS guide to streaming to YouTube with OBS Studio describes auto-stop behaviour: when enabled, it ends the broadcast after encoder streaming stops and disables reconnecting to that broadcast. That guide is older, so check the current wording and behaviour in YouTube Studio’s Live Control Room rather than relying on an old label.
YouTube’s official guidance on ending live streams is a primary reference for broadcast lifecycle behaviour. Auto-stop controls what YouTube does after encoder streaming stops; it does not keep your Windows PC or Mac awake. If OBS stops but YouTube still appears live or reconnecting, review the current broadcast setting and status. Do not change it as a substitute for fixing the host sleep or capture problem.
If the same stream is meant to run continuously from a recorded lesson or playlist rather than a live desktop, the operational question may be different. The CBSE revision stream guide covers a recorded-video use case. Whatever method you choose, confirm what OBS or the relevant playback setup is actually sending before relying on it through a long unattended period.
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 turning off the display mean my computer has gone to sleep?
No. A screen timeout and system sleep are separate power states. The computer may remain awake with the display off, but confirm the sleep setting for your operating system and power condition.
Will every OBS source keep working when the monitor turns off?
No. A media source, camera and display-capture source have different dependencies, and display or graphics behaviour can vary by setup. Test the exact source and monitor arrangement you plan to use.
Can I close my laptop lid during a YouTube stream?
Do not assume lid-close behaviour is equivalent to turning off the display. It depends on the computer and its settings, so check your model’s current guidance and test the exact arrangement before relying on it.
If YouTube says the broadcast ended, will changing the sleep timer fix it?
Only if the computer sleeping was the cause. Check whether OBS stopped sending, whether the source failed while OBS remained active, and what the Live Control Room reports; YouTube’s auto-stop setting affects broadcast lifecycle, not computer power.