Screen Recording Stops By Itself on Mac

You start a recording, walk through a twelve-minute demo, hit stop — and the file is four minutes long. Or QuickTime shows "QuickTime Player encountered an error while recording your screen" and hands you nothing. Or New Screen Recording is greyed out before you even begin.

Three different symptoms, and they share a short list of causes. This walks the list in the order that finds the problem fastest, rather than the order that looks most technical.

Quick comparison

Method 1: disk space, and the number that actually matters

The most common cause, and the one people rule out incorrectly.

Screen recording writes continuously. QuickTime records to a temporary file and only finalises on stop; when the volume fills, the write fails and the recording ends where it ran out. The bar you need to clear is not "some free space" — it is roughly 1 GB per minute for 1080p ProRes-ish capture, and considerably more at 4K.

# free space, human readable
df -h /

# what macOS considers purgeable is NOT what a recorder can use
diskutil info / | grep -i "free\|available"

That second command matters. Finder cheerfully reports 40 GB free when much of it is purgeable — Time Machine snapshots and caches macOS will release under pressure, but not always fast enough for a sustained write.

# list and thin local Time Machine snapshots
tmutil listlocalsnapshots /
sudo tmutil thinlocalsnapshots / 10000000000 4

Rule of thumb: for a twenty-minute 1080p capture, have 30 GB genuinely free, not purgeable-free.

Good for: recordings that stop at inconsistent times and leave a playable file.

Bad for: recordings that stop at exactly the same moment each time — that is a limit, not a resource.

Method 2: display sleep, screen saver, and Low Power Mode

macOS is trying to save your battery, and it does not know you are recording.

Step 1 — stop the display sleeping. System Settings → Lock Screen → Turn display off on battery when inactive and …on power adapter. Set both to Never for the duration.

Step 2 — disable the screen saver in the same pane. A screen saver activating mid-capture ends some recordings and produces a very confusing file in others.

Step 3 — turn off Low Power Mode. System Settings → Battery. Low Power Mode throttles the GPU, and hardware-accelerated encoders can fail rather than degrade under throttling.

Step 4 — for long unattended captures, use caffeinate:

# keep the display awake for two hours
caffeinate -d -t 7200

Leave that running in a Terminal window while you record.

Good for: recordings that die after a suspiciously round interval — five, ten, fifteen minutes — matching your sleep setting.

Bad for: anything under a minute. Sleep is not your problem there.

Method 3: the QuickTime error dialog

"QuickTime Player encountered an error while recording your screen." An unhelpfully generic message covering several distinct failures.

Check permission first. A permission revoked during a session produces exactly this. See fix macOS screen recording permission.

Check the audio device. If QuickTime is set to record from a device that disappears — AirPods disconnecting, an interface unplugged, a virtual device removed — the recording fails on the audio path and takes the video with it. Set input to None and test.

Check for a stuck process from a previous run:

pgrep -x screencapture && pkill -x screencapture

Try a smaller region. Full-screen capture on a multi-display setup at scaled resolution is the heaviest case. If a region records fine and full screen does not, it is throughput, not configuration.

Good for: an error that appears reliably.

Bad for: intermittent errors, which are usually thermal or disk — see methods 1 and 7.

Method 4: "New Screen Recording" is greyed out

The menu item is disabled before you start. Two causes, in order of likelihood.

Permission. QuickTime needs Screen & System Audio Recording, and if it was never granted the menu item is inert. Grant, then quit and relaunch — QuickTime reads permission at launch.

A stuck capture session. macOS allows one screen-capture session at a time from the built-in tooling. A screencapture process left over from a crashed run holds the slot:

pgrep -fl screencapture
pkill -x screencapture

If neither works, log out and back in. That clears both conditions without a reboot.

Good for: the specific greyed-out case.

Bad for: recordings that start and then fail — different problem entirely.

Method 5: the file will not open afterwards

The recording ran, the file exists, and nothing will play it.

QuickTime writes an unfinalised file during capture and writes the index on stop. Force quit or lose power before that, and you have data without a map. untitled.mov in ~/Library/Containers/com.apple.QuickTimePlayerX/Data/Library/Autosave Information/ is sometimes recoverable.

ffmpeg can occasionally rebuild one:

ffmpeg -i broken.mov -c copy repaired.mov

It works when the index is missing but the media data is intact. It cannot help if the write stopped mid-frame.

The durable fix is to use a recorder that writes progressively rather than finalising at the end, so a crash costs you the last few seconds instead of the whole session.

Good for: one-off recovery.

Bad for: anything you cannot afford to lose. Do not rely on repair as a workflow.

Method 6: it stops at exactly the same time

If every recording ends at 5:00, or 10:00, or 30:00, stop looking for a resource problem. That is a limit.

• A free-plan cap. Many recorders limit free-tier recording length. Screenify Studio's free plan caps export at five minutes, not recording — but other tools cap the capture itself.
• A configured maximum in the app's settings.
• A conferencing app's own limit if you are recording through Zoom or Teams rather than capturing the screen.
• FAT32 or exFAT 4 GB file limit if you are writing to an external drive formatted for Windows compatibility. At 1080p that lands around the same duration every time. Reformat to APFS or ExFAT with a modern implementation, or record locally and copy afterwards.

The 4 GB one catches people out constantly, because the failure looks like a time limit when it is a size limit.

Method 7: thermal throttling on long captures

On fanless Macs — MacBook Air especially — a long 4K capture heats the SoC until the encoder is throttled. Symptoms: fine for ten minutes, then dropped frames, then failure.

# watch thermal pressure while recording
pmset -g thermlog

Mitigations: record at 1080p rather than 4K, close other GPU-heavy apps, keep the machine off a soft surface, and use hardware encoding rather than software.

A related trap: recording while something else is encoding. A background Final Cut export, a Time Machine backup, or a Photos library analysis will compete for the same media engine. Check Activity Monitor's Energy tab before a long take.

Method 8: where the file is being written

The destination matters more than people expect, and two destinations cause failures that look nothing like storage problems.

iCloud Drive, Desktop and Documents. If Desktop & Documents Folders sync is on, a recording saved to the Desktop is being written to a folder that iCloud is simultaneously trying to upload. On a long capture, sync can begin evicting or relocating the file mid-write. The recording ends, sometimes with a file that is present but unplayable.

# is Desktop/Documents sync on?
ls -la ~/Library/Mobile\ Documents/com~apple~CloudDocs/ 2>/dev/null && echo "iCloud Drive active"

Record to a local folder outside the synced tree — ~/Movies is not synced by default — and move the file afterwards.

External and network drives. A USB drive that sleeps, a bus-powered drive that browns out under sustained write, or an SMB share that drops for two seconds will all end a recording. External SSDs over USB-C are generally fine; spinning drives and hubs are not. Network shares should never be a recording destination — record locally, copy after.

The FAT32 and exFAT limit again, from a different angle: even where the 4 GB cap does not apply, exFAT's allocation behaviour under sustained write is markedly worse than APFS. If the drive came formatted for Windows and you have not reformatted it, that is worth doing.

Method 9: interruptions macOS treats as ordinary

Several ordinary system events end a capture, and none of them announce themselves.

A display disconnecting. If you are recording a specific display and that display goes away — a hub reset, a cable nudge, a monitor sleeping independently — the capture target ceases to exist. Recording a window rather than a display survives this; recording the display does not.

Fast user switching. Switching to another account, or a screen lock that switches session, ends the capture.

Focus modes and Do Not Disturb. These do not stop recording directly, but a Focus that triggers Sleep or a screensaver does. Check whether a Focus schedule overlaps your recording window.

Hot corners. A cursor parked in a corner assigned to Start Screen Saver or Put Display to Sleep is a genuinely common cause of a recording that ends while you were talking and not moving the mouse. System Settings → Desktop & Dock → Hot Corners.

Bluetooth audio dropping. If AirPods are the input and they disconnect or switch to another device, some recorders stop rather than continue silently. Use a wired mic or the built-in one for anything long.

A software update prompt or a forced restart. Automatic updates can reboot the machine on a schedule. For a long unattended capture, turn automatic updates off for the day.

Prevention worth building in

Most of this is avoidable with three habits.

Do a ten-second test recording before anything long, and open the file. It catches permission, audio device and disk problems in fifteen seconds instead of after a twelve-minute take.

Record in segments. Three four-minute takes beat one twelve-minute take, and not only for failure recovery — editing is easier and re-recording one bad section does not cost the whole session.

Check free space before you start, and clear purgeable space if it is close.

If you would rather the recorder handled this, Screenify Studio checks permission and disk headroom before it starts rather than after, keeps the machine awake for the duration, and writes progressively so a crash costs seconds instead of the session. Recording length is unlimited on the free plan.

Troubleshooting

Fastest path from symptom to cause:

1. Does a ten-second test recording work? If yes, the problem is duration-related — go to 2. If no, it is permission or configuration — go to method 3 and 4.
2. Does it stop at the same time every run? Yes → method 6. No → go to 3.
3. Is there genuinely 1 GB per minute free? No → method 1.
4. Is the display sleeping or Low Power Mode on? Yes → method 2.
5. Is the Mac hot and fanless? Yes → method 7.
6. Where is the file being written? Desktop with iCloud sync on, or an external drive? → method 8.
7. Still failing → record a small region, to ~/Movies, with audio set to None. If that survives, add one variable back at a time.

A few symptom-specific notes that do not fit the flow above:

It stops the moment I stop touching the keyboard. Hot corner or screensaver. Method 9.

It stops when I switch apps. You are recording a window that is being minimised or hidden, not a display. Record the display, or keep the window visible.

It stops only when I record with the camera on. Two capture devices competing, or thermal. Try recording without the camera to confirm, then add it back at a lower resolution.

The recording continues but the audio cuts out partway. Bluetooth input dropping, or a device switching when something else claimed it. Wired or built-in mic for anything long.

It works on battery but not plugged in, or vice versa. Different sleep settings apply to each power state. Both need setting to Never.

It stops after exactly 30 or 60 minutes. Almost always an app-level setting rather than a system one. Check the recorder's preferences for a maximum duration field.

Nothing above and it is intermittent. Check Console.app around the timestamp of the failure, filtering for the recorder's process name. Sudden termination usually leaves a signal, and a crash report in ~/Library/Logs/DiagnosticReports/ narrows it far faster than guessing.

FAQ

Why does my screen recording stop on its own? In order of frequency: the disk filled, the display slept, a limit was reached, or the encoder failed under thermal throttling. A ten-second test plus checking whether it always stops at the same time separates these quickly.

Why is New Screen Recording greyed out? Either QuickTime lacks Screen & System Audio Recording permission, or a screencapture process from an earlier session is holding the capture slot. Grant permission and relaunch, or pkill -x screencapture.

How much disk space do I need? Roughly 1 GB per minute at 1080p, more at 4K. Purgeable space does not count — check with diskutil info /, not Finder.

What does "QuickTime Player encountered an error while recording your screen" mean? A generic message. Most often a permission revoked mid-session or an audio input device that disappeared. Set input to None and retest.

My recording file will not open. Can I recover it? Sometimes. ffmpeg -i broken.mov -c copy repaired.mov rebuilds a missing index. It cannot fix a write that stopped mid-frame.

Does Low Power Mode affect screen recording? Yes. It throttles the GPU, and hardware encoders can fail rather than degrade. Turn it off for long captures.

Why does it always stop at 4 GB? The drive is formatted FAT32 or older exFAT, which caps a single file at 4 GB. Record to internal storage and copy afterwards.

Does recording keep the Mac awake by itself? Not reliably. Some apps assert a power-management lock while capturing and some do not, and even those that do usually block system sleep rather than display sleep — which is the one that matters, because a sleeping display ends a screen capture. Set display sleep to Never, or run caffeinate -d alongside, rather than trusting the recorder to handle it.

Can I record to an external drive? Yes, if it is an SSD over USB-C or Thunderbolt and it does not sleep. Avoid bus-powered spinning drives, USB hubs, and anything formatted FAT32. Network shares should never be a recording destination — the first two-second dropout ends the take. Record locally and copy afterwards.

Why did it stop when I was not touching anything? Almost always a hot corner set to Start Screen Saver or Put Display to Sleep, triggered by a parked cursor. Check System Settings → Desktop & Dock → Hot Corners before blaming anything more complicated.

Is recording in segments actually better? For anything over five minutes, yes — and not mainly for safety. Re-recording one bad ninety-second section is far cheaper than redoing a twelve-minute take, and the edit is easier because the cut points already exist.

The short version

Run a ten-second test and open the file. Note whether failures happen at a consistent time. Those two facts eliminate most of this list before you have opened a single settings pane.

Related reading: Fix macOS screen recording permission · Why screen recordings are so large · Screen recording for beginners