Sweepfor Mac

Troubleshooting

Mac Screensaver Not Working? Here's How to Fix It

Mac screensaver won't start, freezes, or stays stuck on the wallpaper? Walk through the fix sequence — settings, energy saver, and corrupted prefs.

7 min read

You leave the Mac for ten minutes, come back, and the screensaver hasn’t started. Or it’s stuck on a single frame. Or you set “Sequoia” as your screensaver and you’re getting “Drift” instead. Or the screensaver shows for a second and then the Mac wakes itself back up.

Screensaver issues on macOS Sonoma and Sequoia have gotten weirder than they used to be — partly because Apple combined screensavers and lock-screen wallpapers into the same setting in macOS 14, and partly because the new aerial screensavers download large video files that can get partly broken.

Here’s how to sort it out.

Check the actual screensaver setting

On macOS Sonoma and Sequoia, screensaver lives at System Settings → Screen Saver (separate from Wallpaper). Confirm:

  • A screensaver is actually selected.
  • “Show as wallpaper” is set the way you want — if checked, the screensaver plays on idle and then becomes your static wallpaper, which can hide whether it’s actually starting.
  • Check System Settings → Lock Screen for “Start Screen Saver when inactive” and confirm it’s set to a reasonable time (1, 2, 5, 10, 20 minutes — not “Never”).

If “Start Screen Saver when inactive” is set to “Never,” that’s why nothing’s happening. Set a reasonable value.

Check Energy Saver / Battery settings

The screensaver only kicks in when the display is on but idle. If display sleep is set shorter than screensaver activation, you’ll never see it.

System Settings → Lock Screen → “Turn display off when inactive on power adapter” / “on battery.” If display sleep is set to 1 minute and screensaver is set to 5 minutes, the display sleeps before the screensaver starts.

Set display sleep longer than screensaver activation — for example, screensaver after 5 minutes, display sleep after 15 minutes.

Force the screensaver to start manually

Test that the screensaver itself works by triggering it manually:

  • Hot Corners: System Settings → Desktop & Dock → Hot Corners. Set one corner to “Start Screen Saver.” Move your cursor to that corner.
  • Lock Screen: press Control + Command + Q. This locks the Mac, which sometimes triggers the screensaver depending on settings.

If the manual trigger works but idle activation doesn’t, the issue is in idle detection or display sleep settings.

If the manual trigger doesn’t work either — the screensaver fails to start at all — keep going.

Reset corrupted display prefsSweep can wipe and rebuild stale display preference files when those are the cause. Get Sweep free →

Check what’s preventing idle

Background apps can keep the Mac from going idle. Common culprits:

  • Spotify or YouTube playing, even if the audio is muted.
  • A video conference app waiting for a meeting (Zoom, Google Meet open in browser).
  • Caffeine, Amphetamine, or KeepingYouAwake actively running.
  • A Time Machine backup in progress (during the active backup window, the system stays awake).
  • A Final Cut Pro export or a large file copy.

Activity Monitor → CPU tab → check what’s using CPU. If something’s preventing idle, the screensaver won’t start.

You can also use the Terminal command pmset -g assertions to see exactly what’s keeping the Mac awake. Anything in the PreventUserIdleDisplaySleep section is the cause.

Aerial screensavers and corrupt video files

If you use the “Aerial” or “Sequoia” or “Sonoma” screensavers (the ones that show drone footage of mountains, cities, etc.), the video files get downloaded to /Library/Application Support/com.apple.idleassetsd/ and ~/Library/Caches/com.apple.idleassetsd/. If a download was interrupted mid-stream, the screensaver tries to play a corrupt file and either freezes on the first frame or fails silently.

Symptoms:

  • Aerial screensaver works on one Mac but not another with the same configuration.
  • Screensaver shows a single still image instead of motion.
  • Activity Monitor shows idleassetsd using high CPU.
  • Console (Applications → Utilities → Console) shows errors related to com.apple.idleassetsd.

Fix: clear the cache, force a re-download. Manual cleanup is annoying — the assets folder has dozens of multi-GB video files, and you have to remove them carefully.

Skip the manual huntSweep clears the cached configs and broken plists that mess with macOS. Download Sweep free →

Reset screensaver preferences

Screensaver settings are stored in com.apple.screensaver.plist files in your preferences folder. Corruption here can cause the screensaver to either not start, or to use a fallback default different from what you actually selected.

Files involved:

  • ~/Library/Preferences/com.apple.screensaver.plist
  • ~/Library/Preferences/ByHost/com.apple.screensaver.<UUID>.plist
  • /Library/Preferences/com.apple.screensaver.plist (if managed by an MDM profile)

Manual cleanup: quit System Settings, Finder → Cmd + Shift + G → paste those paths, move the files to Desktop, restart. macOS will rebuild defaults — you’ll need to re-pick your screensaver.

Check Focus Modes and Stage Manager

A specific edge case: certain Focus modes disable screensaver activation. System Settings → Focus → click each enabled Focus → check that “Allow screen saver” or related options aren’t disabled.

Stage Manager doesn’t directly affect screensaver but can affect display sleep timing in subtle ways. If you use Stage Manager and screensaver is acting weird, try toggling Stage Manager off temporarily as a test.

External display interaction

If you have an external monitor connected and the screensaver only shows on one display:

System Settings → Screen Saver → “Show on all spaces” / “Show on all displays” — check this is set the way you want.

If you want the screensaver only on the active display, that’s a separate setting. Some macOS releases have toggled which one is the default — check what’s currently set.

Tip: If you connect an external display and the screensaver was working fine before but stopped after, try unplugging the external. If the screensaver works again, the EDID from the external is somehow blocking idle detection — common with TVs that send "user activity" signals on every frame.

Apple Silicon vs. Intel

This isn’t really architecture-dependent, but Apple Silicon Macs are stricter about background process scheduling. A screensaver-blocking background app that didn’t matter on Intel might prevent idle on M-series because the M-series scheduler keeps that app active even when it shouldn’t be doing work. If you’re on Apple Silicon and the screensaver won’t start, check Activity Monitor more carefully than you would on Intel.

Reinstall the screensaver from the picker

A nuclear option for stuck screensavers: in System Settings → Screen Saver, pick a different screensaver, apply, then switch back to the one you wanted. This forces macOS to re-initialize the screensaver path.

For aerial screensavers, you can also force re-download by quitting System Settings, deleting the asset cache (Sweep can do this in one click), and re-opening System Settings. The system will redownload fresh.

What Sweep handles

Sweep helps with the cache and preference side of screensaver issues:

  • Clearing corrupted screensaver caches in one click — particularly the multi-GB aerial screensaver assets that get half-downloaded.
  • Wiping corrupted preference files that prevent screensaver settings from sticking.
  • Removing leftover screensaver bundles from third-party screensavers you’ve uninstalled but that left files behind.

Sweep can’t change your screensaver settings or work around a Focus mode that’s blocking it — those are settings-level. But for cache-related screensaver issues, it’s the fastest way to clean up.

There’s a faster waySweep does this cleanup in seconds. Try Sweep free →

Check the screensaver and idle settings first. Make sure something isn’t blocking idle (Activity Monitor or pmset -g assertions will tell you). For aerial screensavers, clear the cache. Reset preferences if all else fails. Most cases sort out in the first two checks.

← Back to all guides