Live Wallpaper Not Working on a Mac: What Actually Causes It

"Live wallpaper not working" turns out to be at least six unrelated problems wearing the same sentence. A wallpaper that never moved is a different thing from one that moved and stopped, which is a different thing again from a file that will not import. The generic advice you find first, restart the Mac and free up storage, fixes almost none of them.

So this is sorted by what you are actually seeing. Find your symptom, and the cause is underneath it.

It never moved in the first place

Before anything else, check which kind of wallpaper you set, because the built-in macOS ones are not what most people mean by a live wallpaper.

Apple's own documentation is explicit about this. Of the aerials in System Settings, under Wallpaper, it says:

Landscape, Cityscape, Underwater, and Earth aerials: These aerial images animate as you lock or unlock your Mac, showing dramatic views. By default, the aerial wallpaper you select is also used as your screen saver.

That is the whole feature. The animation is a transition at lock and unlock, not continuous motion while you work. The other category people mistake for a live wallpaper is Dynamic Wallpapers, which Apple describes as images that "brighten and darken, based on the time of day for your current location". Those are stills that change slowly through the day.

If you picked one of those and expected a moving desktop, nothing is broken and no amount of restarting will change it. A desktop that animates continuously needs an app that draws it, which is what Vivid Walls and the handful of apps like it do.

It was moving, then it stopped on its own

This is the most common report we get, and it is almost always an idle timeout doing exactly what it was asked to do. You walk away, you come back, the desktop is a still frame.

In Vivid Walls the default is to pause after 15 minutes with no keyboard or mouse input. To change it, open Settings, choose Performance, and look under Pause Rules:

• Pause after idle timeout is on by default. Turn it off to keep the wallpaper running while you are away.
• Timeout underneath it offers 5, 10, 15 and 30 minutes and 1 hour. It ships at 15 minutes.

It is worth being honest about the tradeoff rather than just telling you to turn it off. Rendering an animated wallpaper to an unattended screen is the least useful work a laptop can do, and the setting exists because it saves real battery. If your Mac lives on a desk with power, turning it off costs you nothing you will notice.

It stops whenever a game or a full screen app is open

Also deliberate, also on by default: Pause when a fullscreen app is active, in the same Pause Rules section. The reasoning is that a wallpaper nobody can see should not be taking GPU time away from the thing in front of it, which matters most in exactly the case people notice it, gaming.

Turn it off if you would rather the wallpaper keep running behind full screen windows. You will pay for it in power and a little frame rate in the foreground app.

It is smooth plugged in and choppy on battery

Nothing is failing. It is being throttled on purpose, and there are two separate controls that do it.

The first is under Pause Rules. Manage on battery power is on by default, and the Battery behavior menu next to it ships set to Reduce to 15 FPS. The other option is Pause entirely. Fifteen frames a second is a deliberate compromise, visibly less smooth than mains power but far cheaper on the battery, and it is the reason a wallpaper looks fine at your desk and stuttery on a train.

The second is the Frame Rate section further down the same tab. FPS Cap defaults to 30 FPS and can be set to 15, 24, 30, 60 or Unlimited. Sixty is noticeably smoother on a 120 Hz display. Unlimited is there for people who want it and the app warns you that it costs power, which it does.

If your wallpaper is choppy on mains power too, raise the FPS cap first, before assuming the file or the Mac is the problem.

Nothing happens when you drag a folder onto the window

This one is our fault and we would rather write it down than let you spend twenty minutes on it.

Drag and drop in Vivid Walls accepts individual media files. It does not accept folders. What makes it worse than a plain limitation is that the app takes the drop, finds nothing it recognises inside it, and then says nothing at all: no error, no alert, no new wallpaper. From the outside it looks exactly like the app is broken. It is queued to be fixed, and the fix is either accepting folders or telling you plainly that it cannot.

Until then, there are two routes and which one you want depends on whose files they are:

• Your own videos, GIFs or images. Open the folder and drag the files themselves, not the folder around them. Or use the picker and press Command A to select everything inside, since it accepts multiple files at once.
• A Wallpaper Engine library folder. That has its own route and it does read folders: File, then Import Wallpaper Engine Library. Point it at the copied library and it scans for wallpapers inside.

Worth knowing, because it explains a confusing case: the library importer looks for Wallpaper Engine wallpapers specifically. Pointed at a folder of your own MP4s it finds nothing and comes back empty, which reads like a second bug and is not one. That is the case where you want the file route above.

The file simply will not import

A file that vanishes on import is usually a format the app never accepted. Vivid Walls reads these and nothing else:

• Video: mp4, mov, m4v, webm
• Animated: gif
• Stills: png, jpg, jpeg, heic, webp

Anything outside that list is ignored, silently, for the same reason the folder case above is silent. AVI, MKV and WMV are the three that come up most; converting to MP4 first is the fix. WebM does import, but it is converted on the way in, so it takes longer than the rest and a large one can look like it has hung when it has not.

The lock screen or the screen saver is black

This one was a real defect, reported by customers rather than found by us, and version 1.2.4 addresses two separate causes of it. If you are seeing a black lock screen after installing an animated wallpaper, update before doing anything else.

What changed is that every lock screen export is now decoded and checked for actual picture before it is installed. If it comes back blank, the app retries once and then tells you it failed rather than quietly installing a black screen. Separately, the part that resets the lock screen after each unlock was not doing anything in earlier builds, which is the case where the first lock looks right and every one after it is black.

If it still goes black after updating, that is worth an email to support with your Mac model and macOS version. We will not pretend the check catches every case; it logs its own failures, and the ones it cannot fix are the ones we want to see.

The app will not open at all

Check the two requirements first, because between them they explain most of it:

• macOS 14 or later.
• Apple Silicon. An M1 or newer Mac. It does not run on Intel Macs, and there is no build that does.

If your Mac meets both and it still will not launch, send us a note rather than reinstalling. That combination is rare enough to be worth looking at properly.

The short version

• Built-in macOS aerials animate at lock and unlock only. Apple documents this. They are not a moving desktop.
• Stopped after a few minutes: idle timeout, 15 minutes by default. Settings, Performance, Pause Rules.
• Stops in games: Pause when a fullscreen app is active, on by default, same place.
• Choppy on battery: Battery behavior is set to Reduce to 15 FPS by default. FPS Cap defaults to 30.
• Dragged a folder and nothing happened: drag the files instead, or File, then Import Wallpaper Engine Library for a Wallpaper Engine library. Our defect, and it is queued.
• File will not import: mp4, mov, m4v, webm, gif, png, jpg, jpeg, heic and webp are the whole list.
• Black lock screen: update to 1.2.4, then email support if it persists.
• Will not launch: macOS 14 or later, Apple Silicon only.

If your symptom is not on this list, we would genuinely like to hear it. The two entries above that are our own faults got written down because somebody took the time to report them.