WallpaperMachine: playing Steam Workshop wallpapers on a Mac desktop

What the app is for, and who cannot use it

WallpaperMachine is a Mac app that plays Wallpaper Engine scene, video and web wallpapers on the desktop, taking them straight from the Steam Workshop. The project describes it as a free, open-source app for anyone who wanted Wallpaper Engine on a Mac.

The scope of what works is stated precisely in the README, and it is worth reading twice because the two halves are different. What works right away is the bundled video wallpaper Aurora Drift, pixiv illustrations, your own videos and pictures, and browsing the whole Workshop without signing in. What requires a Steam account that owns Wallpaper Engine is Workshop downloads, and scene wallpapers, which use shared resources from the Wallpaper Engine you own.

That split is the honest shape of the project. It is a Wallpaper Engine compatible player, and the parts of Wallpaper Engine that depend on shared resources from a licensed copy cannot be reproduced without that copy. A user with no Steam account still gets a working app with local media, a Workshop browser in browse-only mode, and the pixiv integration.

The platform requirements are narrow and stated up front: macOS 15 Sequoia or later, and Apple silicon, meaning M1 or later. The project description adds that the app is free and open source, and the topics list covers animated wallpaper, dynamic wallpaper, live wallpaper, lock screen, screensaver, Metal, Vulkan, SwiftUI, Swift and Rust, with pixiv and Steam Workshop among the sources it works with.

The interface is one window, a menu bar player, and a login item

The application window has tabs across the top. The Library tab holds all wallpapers, favorites and your collections, the Steam Workshop and pixiv tabs are for browsing, and Settings holds configuration. A bar along the bottom shows what is currently playing, and the right-hand inspector shows the selected wallpaper's preview, compatibility check and options.

The distinction the README draws is between selection and apply. Choosing a wallpaper only selects it. Apply is the action that makes it your desktop, and it works the same for scene, video and web wallpapers. There is a separate Preview feature, which tries an installed scene, video or web wallpaper in its own window with the current options and separate playback controls, and where sliders, colours and switches show as you change them. That is a useful design for a wallpaper engine, because a scene wallpaper has live parameters and applying one blind is a bad way to find out what a parameter does.

Closing the window does not quit the app. It keeps running in the menu bar, where you can pause, resume, mute, or go to the previous, next or a random wallpaper, on each display separately when you have more than one. When it launches at login it starts there without opening the window.

The per-display control is the detail that separates a wallpaper player from a screen saver. A multi-monitor Mac user can run different wallpapers on different displays, and the random and next controls act per display, which is the behaviour a user with a laptop and an external monitor expects.

Installing the disk image, and the first launch macOS blocks

The quick start is a drag-and-drop install, and the README is honest about the one friction point.

The first step is to download the free disk image for the latest version from the project's download page. The second is to open it and drag WallpaperMachine to Applications. The third is to open it, and here the README warns that the download is not notarized yet, so macOS holds the first launch. The fix is to click Open Anyway in System Settings, under Privacy & Security, once. A first-run guide takes it from there, and the app updates itself from then on.

The install guide linked from the README walks through every step with pictures, and there is a separate documentation directory in the repository under `docs/`.

For people who would rather build it, the README says it takes two commands and points to its own Open source, Free to build section. The repository layout supports that claim. There is a `WallpaperMachine.xcodeproj/` for the Xcode project, a `project.yml` for the project definition, an `App/` directory for the SwiftUI application, an `Extension/` directory, `Shared/` for shared code, `Resources/` for assets, `Packaging/` and `Formula/` for the distribution artefacts including a Homebrew formula, `scripts/` for the build helpers, `Tests/` for the test targets, and an `upstream/` directory.

The primary language is Swift, and the presence of a Rust topic alongside Swift points to a native component written in Rust, which is consistent with a project that renders WebGL or Vulkan content from Workshop scenes.

Workshop downloads need a qualifying Steam account, browsing does not

The Workshop tab is where the licensing constraint shows up, and the README separates browsing from downloading.

Browsing the live Steam Workshop needs no sign-in. The tab gives you collections, each author's wallpapers, and your subscriptions. Downloads run inside the app, several at once, and they require a Steam account that owns Wallpaper Engine. Updates to the wallpapers you already have are found once a day and installed in one click.

So there are three distinct levels of access: browse anonymously, download with a qualifying account, and get updates for what you have already downloaded. The daily update check being a once-a-day poll rather than a live feed is a sensible choice, since the Workshop is a large catalogue and a client that polled it constantly would be both slow and rude to the service.

The pixiv tab is separate and simpler. It offers pixiv's illustration rankings and tag search, and you can save any page of a work as a still wallpaper, with sign-in to pixiv mentioned as part of that flow.

The scene wallpaper story deserves emphasis. The README states that scene wallpapers use shared resources from the Wallpaper Engine you own, which is why they sit in the second group rather than the first. A scene wallpaper is not a video file, it is a bundle of assets and a script, and the resources it references live in the licensed product. That is the technical reason a compatible player cannot simply render them from the Workshop alone, and the reason the app is positioned as a player for people who already own Wallpaper Engine rather than as a replacement for it.

The documentation lives in the repository, feature by feature

This project documents itself in a way that is worth borrowing. Instead of a single long README, the features are separate documents under `docs/features/`, and the README's own feature table links directly into them.

The links visible in the README point to `docs/features/control-panel.md` for the selection versus apply distinction, `docs/features/wallpaper-properties.md` for live preview, `docs/features/web-wallpapers.md` for the web wallpaper type, `docs/features/workshop-downloads.md` for downloads, collections, authors, subscriptions and updates, and `docs/features/pixiv.md` for the pixiv integration.

The topic list on the repository gives the rest of the feature surface, and the presence of a lock-screen and screensaver topic alongside animated and dynamic wallpaper suggests those are separate modes rather than one generic playback. The listed rendering backends are Metal and Vulkan, which is the expected pair for a modern Mac, and the presence of both in the topic list suggests the renderer can target either.

The repository also carries `AGENTS.md` and `CLAUDE.md` at the top level, which are the files used to instruct coding agents working on the project, plus `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, `SECURITY.md`, `CHANGELOG.md` and `SPONSORS.md`. The presence of `AGENTS.md` next to `CLAUDE.md` is a signal about how the project expects to be worked on by both humans and automated tooling, and the fact that the README itself is mirrored in `README.zh-CN.md` with a comment at the top of the English file instructing that both are changed together is a small but genuine sign of process discipline.

Where WallpaperMachine is the wrong choice

The platform limits are not subtle. The app requires macOS 15 Sequoia or later on Apple silicon, so an Intel Mac is out, and so is anything older than macOS 15. That is a hard floor rather than a preference, and it is the first thing to check.

The second case is wanting Wallpaper Engine content without owning Wallpaper Engine. Scene wallpapers depend on shared resources from a licensed copy, so the app cannot deliver them. A user in that position should look at what the app does offer, the bundled video wallpaper, local media, pixiv stills and browse-only Workshop access, and decide whether that is enough. If it is not, the honest position is that this project is not a way to obtain Wallpaper Engine content for free.

The third case is a Windows or Linux desktop. The project is a Mac app, and the shared-resource design means it is not a general Wallpaper Engine player for other platforms.

The fourth is a locked-down Mac. The download is not notarized, so the first launch requires clicking through a System Settings warning, and in a managed environment that is a policy decision rather than a user preference. The README states this plainly, which is better than discovering it after an installation policy has already been written.

The alternative worth naming is a native macOS video wallpaper, which the system supports on its own for still and dynamic desktop pictures. The difference in approach is that the system gives you a background image or an animated image you supply, with no scripting, no parameters, no Workshop content and no per-scene options. WallpaperMachine gives you a running scene with live controls, a preview window, and a library, and it asks for a Steam account to do the parts that come from Wallpaper Engine's own assets.

Release pace, the licence, and the cost of building it yourself

Maintenance is visible in the release history. Version 1.5.8 was tagged on 2026-10-20, 1.5.7 on 2026-10-19 and 1.5.6 on 2026-10-17, and the last push to the default branch was on 2026-10-20. Three releases in four days, and a patch-level numbering scheme, which is what you would expect for a project that ships a signed disk image and a Homebrew formula and has to keep both in step.

The licence is GPL-2.0, and the repository carries both a `LICENSE` file and a separate `LICENSING.md` file. The presence of two files is not redundancy, it usually signals that the standard licence text and a project-specific note about what the licence covers are both needed, and in this case the repository contents give a plausible reason. The app links to and plays wallpapers that other people created and uploaded to the Steam Workshop, and the project also ships a `SPONSORS.md` file, which tells you that funding is handled separately from the code.

Whether the GPL-2.0 terms cover the third party wallpaper content is exactly the kind of question the `LICENSING.md` file exists to address, and the answer to it is not something the README states. Anyone planning to redistribute a build, bundle it with other software or run it for an organisation should read that file rather than assume. This is a description of the file layout, not legal advice.

Building it yourself is presented as a two-command affair, and the repository is set up for it with an Xcode project, a `project.yml` project definition, packaging directories and a `Formula/` directory for the Homebrew formula. The cost of that path is that you now own the build, and the README's own recommendation is the prebuilt disk image that updates itself.

Editorial conclusion

Adopt WallpaperMachine if you are on an Apple silicon Mac running macOS 15 or later, you own Wallpaper Engine on Steam, and you want its scene wallpapers to run natively instead of asking you to keep a Windows machine or a virtual machine awake for the privilege. Do not adopt it on Intel Macs, on Linux or on Windows, and do not expect the Workshop subscription content to work without a qualifying Steam account. Before you install, check that your hardware and OS meet the stated floor, since the disk image is not notarized yet and macOS will hold the first launch until you click Open Anyway, and read the licensing note, because the GPL-2.0 terms and the separate `LICENSING.md` file in the repository govern what you may redistribute from a build.

Frequently asked questions

Official sources

1. License: GPL-2.0
2. Project website
3. README
4. Releases
5. WallpaperMachine/WallpaperMachine on GitHub