Why Your Screen Recording Stops When the Screen Sleeps (and How to Prevent It)
Long recordings that end early or go blank are usually display sleep, a screen saver, or a lock screen. Here are the macOS and Windows settings to change first.
You start a recording of a long process — a build, a migration, a 40-minute training session — and step away. When you come back, the file is a fraction of the length you expected, or there’s a long stretch of nothing in the middle where your screen should have been.
Almost nobody suspects power settings first. But a screen recorder captures whatever your display is showing, and your operating system is under standing orders to stop showing anything once you stop touching the keyboard. Recording doesn’t count as touching the keyboard. Here’s what fires, in what order, and the settings to change before a long session.
Screen Recording Doesn’t Count as Activity
Idle timers on both macOS and Windows watch for input: keyboard, mouse, trackpad, sometimes controller. They do not watch whether pixels are changing, and they do not watch whether something is reading the screen.
So during a long unattended capture, from the system’s point of view, you have been idle the whole time. The countdowns run exactly as they would if the machine were sitting on an empty desk.
Recorded doesn’t override those timers. It doesn’t register a wake lock or alter your power plan when recording starts, so whatever your display-sleep, screen-saver, and system-sleep settings say is what happens. If you want the screen alive for 50 minutes, you have to tell the OS that yourself.
There are usually three separate countdowns, and they fire in this order:
- Screen saver starts after its own idle interval. Your actual content is now behind a screen saver.
- Display sleep turns the panel off. There is nothing meaningful on screen to capture.
- System (idle) sleep suspends the machine. The recording process is suspended with it.
A fourth one, the lock screen, usually rides along with the first two — macOS can require a password after the screen saver begins, and Windows can lock on resume. When it engages, the session you were recording is hidden behind a login prompt.
The symptom depends on which countdown you hit. A screen saver or display-off stretch tends to leave you with a file of the right length containing footage you can’t use. Full system sleep tends to end the recording: capture is suspended mid-write, and if the save never completes, the session shows up with a Recording failed badge in your library rather than as a playable video.
macOS: What to Change
All of these live in System Settings:
- Lock Screen. Set Turn display off on power adapter when inactive (and the battery equivalent, if you’ll be unplugged) to a value longer than your recording, or to Never. In the same panel, set Start Screen Saver when inactive to Never, and loosen Require password after screen saver begins or display is turned off so a quick glance away doesn’t put you behind a login prompt.
- Battery on laptops, or Energy Saver on desktops. Look for Prevent automatic sleeping when the display is off and turn it on, so a display timeout you forgot about doesn’t escalate into a full sleep. Turn Low Power Mode off too — on battery it can throttle performance enough to cost you frames.
- Don’t close the lid. On a MacBook, closing the lid sleeps the machine unless it’s on power with an external display attached. If you’re recording a laptop screen, the lid stays open.
If you’d rather not change persistent settings, Terminal has a one-session version:
caffeinate -dimsu -t 3600
That keeps the display and the system awake for 3600 seconds (one hour) and then exits on its own. Start it before you hit record, set the duration a bit longer than you need, and your normal power settings stay untouched.
Windows: What to Change
- Settings → System → Power & battery → Screen, sleep, & hibernate timeouts. Push both Turn off my screen after and Put my device to sleep after past the length of your session, or set them to Never. Laptops have separate values for battery and plugged in — change the one you’ll actually be on.
- Settings → Personalization → Lock screen → Screen saver. Either clear the screen saver or uncheck On resume, display logon screen so you aren’t locked out mid-session.
- Settings → Accounts → Sign-in options → Dynamic lock. If this is on, your PC locks when a paired phone walks away from it. Turn it off before recording.
- Windows Update → Advanced options → Active hours. An automatic restart ends a recording as decisively as sleep does. Set active hours to cover your session.
The command-line equivalent, in an elevated prompt:
powercfg /change monitor-timeout-ac 0
powercfg /change standby-timeout-ac 0
Zero means never, -ac applies to plugged-in power (use -dc for battery), and you can set the values back afterward.
What Recorded Won’t Do For You
Two limits are worth planning around before a long session:
There’s no pause and resume. A recording runs from start to stop. If something interrupts the middle of a 40-minute take, you can’t suspend and pick it up later — you trim the dead stretch out afterwards, or you re-record. Splitting at the playhead with C and deleting the segment does the trim cleanly, with everything after it rippling earlier to close the gap. Our guide to trimming and cutting covers the mechanics.
There’s no global stop shortcut. Recording is started and stopped with the on-screen controls, so stopping means coming back to the machine and clicking the stop button on the control bar. There’s no hotkey from another app and no scheduled stop. The control bar shows an elapsed timer while you record, which is the thing to glance at when you return.
The Better Answer: Don’t Record One Long Unattended Take
Power settings fix the interruptions. They don’t fix the deeper problem, which is that an hour-long unattended capture is a lot of risk in one file.
- A single failure costs you everything. One interruption at minute 38 jeopardises the whole session, not the last two minutes of it.
- The storage adds up fast. Capture writes continuously for the full duration, and audio is stored as uncompressed WAV alongside the video. How much disk space screen recording uses has the arithmetic, and the short version is to check free space before, not during.
- Long files are slow to edit. Scrubbing an hour-long timeline to find the four moments that matter is its own kind of tax.
- Export of anything over 25 seconds needs a Pro license (shorter exports are free, with a small watermark), so a long take is also a decision about the account you’re exporting from.
Recording in several shorter takes caps the damage from any one problem and usually produces tighter video. We wrote that up in recording in takes. If the thing you’re capturing genuinely runs long — a slow install, a data import — record the start, stop, and record the finish as a separate take rather than filming the waiting.
And if the recording was choppy rather than interrupted, power settings are the wrong lead. Throttling, disk contention, and competing GPU work are the usual causes; the performance optimization guide works through those, and laptop-only recording covers the battery-and-heat version of the same problem.
Pre-Session Checklist for Anything Over 10 Minutes
- Display sleep and system sleep set longer than the session, or off
- Screen saver off, or at least not locking the machine
- Dynamic lock off; automatic update restarts outside your window
- Plugged in, low-power mode off, lid open
- Free disk space checked, with room for the export as well as the capture
- A plan for who clicks stop, since no shortcut will do it for you
Two minutes of settings beats re-staging a 40-minute session you can’t easily reproduce. If you haven’t installed the app yet, grab Recorded and run a deliberately boring five-minute test with your power settings as they are now — it’s the cheapest way to find out which countdown fires first on your machine.