How to Make Your Own Live Wallpaper on a Mac

Most guides about live wallpapers on a Mac are really guides about downloading somebody else's. This one is about the other half: you already have the thing you want on your desktop. A clip you shot, a render you made, a looping animation a friend sent you, a photo from a trip. The question is how to get it out of your Downloads folder and onto the desktop, and what happens to it along the way.

The short answer is that three kinds of file work, one route is reliable, and there is exactly one kind of custom wallpaper you cannot make yourself. All four of those are worth knowing before you start converting anything.

What macOS gives you on its own

Worth saying first, because it saves some people the rest of the article. macOS has built-in moving wallpapers under System Settings, then Wallpaper. Those macOS wallpapers are good, and they are free, and on a recent Mac some of them carry over to the lock screen.

What that panel does not do is take your file. Apple supplies the aerials and the dynamic desktops; there is no button there for adding your own video. So the moment the wallpaper you want is one you made, you need something else to hold it. That is the gap this article is about.

The file types that actually work

Vivid Walls reads three families of file, and it is worth being exact because a format that is not on this list is skipped rather than converted:

• Video: MP4, MOV, M4V, and WebM
• Still images: PNG, JPG, JPEG, HEIC, and WebP
• Animated GIF

MP4 and MOV cover almost everything people already have. MP4 is what a screen recorder, a phone, or a stock site will hand you. MOV is what QuickTime and most Mac editors export by default, so if you cut the clip on the Mac you are already holding a file that works.

Two absences are worth naming rather than leaving you to discover them. AVI and MKV are not on the list, which matters because a lot of older downloaded footage is MKV. Converting an MKV to MP4 is usually a container change rather than a re-encode, so it is fast and it does not cost you quality. And ProRes in a MOV wrapper will import, but the files are enormous for something that loops on your desktop all day; exporting a normal H.264 or HEVC MP4 instead is the better trade.

Getting the file in

There are two routes, and one of them has a trap in it.

The reliable route: File, then Import Wallpapers

Open Vivid Walls, choose File in the menu bar, then Import Wallpapers. A standard macOS file chooser opens, filtered to the formats above so anything unsupported is greyed out and you cannot pick a file that will fail.

The chooser allows selecting many files at once, which is the part worth knowing if you are bringing over a set rather than a single clip. Open the folder that holds them, press Command A to select everything inside, and import in one pass. Each file is copied into the app's own storage as it imports, which is what lets you tidy up the originals afterwards.

The quick route: drag the files in

You can also drag files straight onto the app window and they import the same way. For one clip this is the fastest thing available.

The trap: folders

Here is the mistake almost everyone makes once, and it is worth spelling out because the app does not currently warn you about it.

Drag and drop reads individual files, not folders. If you drag the folder that contains your videos, rather than the videos inside it, nothing happens. No error, no alert, no new wallpaper, just a drop that appears to land and then does not. It looks exactly like the app failing to work, when in fact it is reading a folder, finding no importable file at the level it was handed, and stopping.

The file chooser behaves the same way for the same reason: it selects files, not directories, so you cannot hand it a folder either.

So the rule for your own media is simply this: select the files, never the folder that holds them. Open the folder first, then select what is inside. Command A does the whole set at once, which gets you the convenience the folder drop looked like it was offering.

One clarification, since the two things get confused. There is a folder-shaped import, under File, then Import Wallpaper Engine Library, but it is a different job. That one goes looking for Wallpaper Engine wallpapers, each of which is a folder with a project file inside describing it. Pointed at a folder of your own MP4s, it finds nothing to describe and comes back empty. It is not the route for your own media, and reaching for it is a common second wrong turn after the first one.

Making the source file

Importing is the easy half. Whether the result looks good on a desktop is mostly decided before you import.

From a video

The two things that separate a wallpaper you keep from one you turn off after a day are the loop and the pacing. A visible jump at the loop point is the single most irritating thing a desktop can do, because you will see it every twenty seconds for a week. Clips that start and end on a similar frame hide the seam; clips that end mid-movement announce it.

Pacing matters for a reason people underestimate: this is going behind your work, not in front of it. Fast cuts and big camera moves read as motion in the corner of your eye all day and get tiring fast. Slow, continuous, low-contrast movement is what survives. We went into the video side in more depth, including trimming and what gets scaled, in using your own video as a live wallpaper.

From a still image

A still image imports and works as a wallpaper, and it is genuinely useful for a photo you like at full quality. But it is worth being blunt about what it does not do: importing a photo does not animate it. Nothing here invents motion that is not in the source. If you want the photo to move, the motion has to be added first, in a video editor, and brought in as a video.

From a GIF

Animated GIFs import and loop, which makes them the fastest way to get something moving on the desktop, especially for pixel art and hand-drawn animation where a GIF is often the original format. The tradeoff is inherent to the format rather than to any app: GIF is limited to 256 colours per frame, so photographic footage and smooth gradients band visibly at full screen size. Illustration and pixel art hold up well. A gradient-heavy sunset does not, and is better re-exported as a video.

Size it for the screen it will run on

Match the display. A 1920 by 1080 file stretched across a 4K panel is being enlarged, and it will look soft against the crisp text and icons sitting on top of it, which is exactly the comparison that makes softness obvious.

The opposite is worth knowing too, because it is the more expensive mistake. Going substantially larger than the panel adds no visible detail, because the extra pixels have nowhere to go, and every one of them still has to be decoded continuously while the wallpaper runs. An 8K file on a 4K display costs real work for nothing you can see. Match the screen and stop there.

Aspect ratio is the other half. A vertical phone video on a horizontal desktop has to be pillarboxed or cropped, and neither is flattering. If the footage was shot on a phone, it is worth deciding deliberately which part of the frame survives the crop rather than letting it happen to you.

If you have more than one display

Wallpapers are assigned per display, so a custom clip can run on one monitor while something else runs on the other. It is a common setup for exactly the reason you would expect: something calm on the screen you work on, and the more eye-catching one to the side. The mechanics of assigning them are covered in running a different live wallpaper on each monitor.

Making one in the Wallpaper Engine editor

If you are coming from a Windows PC, there is a fuller version of "make your own" available to you, because Wallpaper Engine has an editor and it produces wallpapers that are more than a looping video.

Those come across, with one step people miss. The companion app scans two places: Steam's workshop content folder, and a projects workshop folder inside your Wallpaper Engine install. Wallpapers you built yourself in the editor are saved outside both of those, so they do not appear in the list and it looks as though they were not supported. Copy that wallpaper's folder into either scanned location, relaunch the companion, and it shows up with the rest of your library.

The transfer itself runs over your local network and takes about five minutes; the step by step is in importing your Wallpaper Engine library to a Mac.

The one you cannot make yourself

Worth stating plainly, because it is the reasonable next question and the answer is no.

You cannot point the app at your own web page or HTML file. Web wallpapers do exist in Vivid Walls, and they run, but they arrive as part of a Wallpaper Engine library import rather than by handing the app a URL or an HTML file of your own. There is no field for that, and adding your own web page is not a supported route today.

If what you want is something interactive or data-driven that you built yourself, the path that works is to build it as a Wallpaper Engine wallpaper on a PC and bring the finished wallpaper across, using the folder note above.

What it costs to run

A custom wallpaper costs the same as any other wallpaper of its type, and the honest answer to how much is long enough that it has its own article: do live wallpapers drain a MacBook battery. The one decision that belongs in this article is that the cost is mostly set by the file you make. Resolution and frame rate are yours to choose at export time, and a 4K 60fps file costs meaningfully more to run than a 4K 30fps one that, on a wallpaper of slow-moving footage, is very hard to tell apart.

The short version

• Video, still image, or GIF. MP4, MOV, M4V, WebM, PNG, JPG, HEIC, WebP, and GIF.
• File, then Import Wallpapers. Or drag the files in.
• Select the files, never the folder. Command A inside the folder does the whole set.
• Match the file to the screen's resolution. Bigger is not sharper, it is just more work.
• A still image stays still. Motion has to be in the source.
• Made it in the Wallpaper Engine editor? Move its folder into a scanned location first.
• Your own web page is the one thing you cannot bring.

Common questions

Can you make your own live wallpaper on a Mac?

Yes, from a video, a still image, or a GIF. macOS on its own only accepts Apple's supplied wallpapers under System Settings, Wallpaper, so using your own footage needs a wallpaper app. In Vivid Walls you add your own file with File, then Import Wallpapers, and it joins your library alongside everything else.

What file types can I use for a custom live wallpaper on Mac?

Video in MP4, MOV, M4V and WebM. Still images in PNG, JPG, HEIC and WebP. Animated GIFs. Anything outside that list is skipped rather than converted, so AVI and MKV need a quick container change first.

Why does dragging a folder of videos into the app do nothing?

Drag and drop reads individual files, not folders, so a dropped folder is ignored with no visible error. Select the files themselves rather than the folder that holds them. The file chooser under File, Import Wallpapers also selects files rather than folders, and it does allow selecting many at once, so pressing Command A inside the folder is the fastest way to add a whole set.

Can I use my own web page or HTML file as a live wallpaper?

Not as your own file. Web wallpapers exist in Vivid Walls but arrive as part of a Wallpaper Engine library import, not by pointing the app at a URL or an HTML file. To use something interactive you built yourself, build it as a Wallpaper Engine wallpaper on a PC and bring the finished wallpaper across.

What resolution should a custom live wallpaper be?

Match the display it will run on. A 1080p file on a 4K display is being enlarged and will look soft next to the text sitting on top of it. Going much larger than the panel adds no visible detail and only costs decoding work.

Can I make a live wallpaper from a photo?

You can import a still image and use it as a wallpaper, but importing a photo does not animate it. Nothing invents motion that is not in the source file. To make a photo move, add the motion first in a video editor and import the result as a video.

Can I make my own wallpaper in the Wallpaper Engine editor and use it on a Mac?

Yes, with one step people miss. The companion scans Steam's workshop content folder and a projects workshop folder inside your Wallpaper Engine install. Editor creations save outside both, so they are not listed. Copy that wallpaper's folder into either scanned location, relaunch the companion, and it appears with the rest of your library.