Muro answers live wallpapers with hardware decoding and no paywall

A live wallpaper app whose argument is what it does not cost

Muro plays looping video wallpapers on a Mac. The reason it exists, stated directly in the README, is dissatisfaction with what else was available: applications gated behind a subscription or a paid tier holding the better wallpapers back, and applications built as web pages in a desktop wrapper, which the author describes as sitting at three to four hundred megabytes of memory and keeping the processor warm all day for a picture that moves.

So the pitch is native construction and no paywall. It is written in Swift with the platform's own interface toolkit, hands video decoding to the Mac's media hardware rather than the processor, and pauses itself whenever you cannot see it. Everything is free with no tier, no licence key and no account.

Those two claims are related rather than separate. A web-wrapped application cannot easily reach hardware video decoding or the system signals that say a display went to sleep, which is why the resource cost it is criticising follows from the technology choice rather than from carelessness.

The audience is any Mac user who wants a moving desktop and has noticed their laptop getting warm.

Pausing is the feature, not the wallpaper

The feature that matters most for daily use is the list of conditions under which it stops.

Playback pauses on full screen applications, display sleep, screen lock, low power mode and low battery, and a paused wallpaper is stated to use no processor time at all. A separate mode holds the wallpaper still while you work and plays it only when the desktop is actually visible, per screen.

That is the correct design for this category. A video wallpaper is, by definition, entirely obscured most of the time, so the question is not how efficiently it renders but whether it renders at all when nobody can see it. Enumerating five separate conditions, including battery state, suggests the author worked through the cases rather than handling the obvious one.

A second efficiency control sits alongside it, offering each wallpaper either its original frame rate or a reduction to thirty frames per second, which the README says halves the power draw, chosen per wallpaper rather than globally.

Video is decoded in hardware using a modern codec, never on the processor, and imported videos are transcoded once into that codec when added. Paying the conversion cost at import rather than on every playback is the right trade for something that loops indefinitely.

Installing it, and the features gated on a very new system

Distribution covers a direct download from releases and a package manager cask.

brew install --cask MrRockySL/muro/muro

The application requires macOS 14 or newer and ships as a universal binary covering both processor architectures, so older Intel machines are included rather than dropped.

Two of the headline features carry a much higher requirement, and this is the detail most likely to disappoint someone. Lock screen wallpapers and the screen saver mode both require macOS 26 or newer. Those are the two capabilities that distinguish this from simply playing video on the desktop, and they are unavailable to anyone who has not moved to the newest system.

Anyone reading the feature list should map it against their own version before installing, because the base requirement and the requirement for the interesting parts are twelve major versions apart.

The rest of the feature set is substantial and available more broadly: a full screen gallery for browsing and previewing before downloading, playlists that rotate on a timer in order or shuffled, per-wallpaper scheduling down to individual hours of the day, a pause-after-a-period control measured in seconds through hours, bulk deletion, importing your own video, and menu bar controls for switching without opening the application.

The library updates without the app, which is worth thinking about

One feature is listed plainly and has an implication the list does not spell out: new wallpapers arrive on their own, with the library updating without updating the application.

That is convenient and it means the application fetches content from a remote catalogue the author controls. Two consequences follow. The wallpapers you browse are delivered over a network rather than bundled, so the gallery depends on that service continuing to exist. And content arriving outside the application update cycle also arrives outside whatever review an application update receives.

Neither is a problem, and both are the sort of thing a reader should know before installing something that runs continuously. The repository does carry a security policy and a notices file, the latter being where content attribution for the wallpapers would normally live, which is the right place to check what rights attach to the videos themselves. The application's own licence covers the code rather than the catalogue.

For anyone uncomfortable with that arrangement, the import feature provides a path around it, since your own videos are transcoded and added locally with no catalogue involved.

Where the enthusiasm should be tempered

A moving wallpaper costs power. The pause conditions mean it costs nothing when hidden, and while the desktop is visible your Mac is decoding video continuously. Hardware decoding makes that cheap rather than free, and the frame rate control exists precisely because it is not free. On a laptop away from power, the honest expectation is some battery cost whenever the desktop is in view.

Storage is the second cost. Downloaded wallpapers and imported transcodes are video files, and a library assembled over time occupies real space. Nothing in the README quantifies it, and the deletion tooling existing at all suggests it accumulates.

The comparison with other applications is the author's, and the memory figures attributed to web-wrapped competitors are not measurements anyone can check from this repository. The architectural argument behind them is sound; the specific numbers are a claim.

Finally the version cadence is brisk, at version 5.0 published on 2026-09-13 with the last push on 2026-09-17, which is good for fixes and means the feature set is moving.

The system's own wallpapers are the alternative

Recent versions of macOS ship dynamic video wallpapers of their own, and for many people that is the alternative already installed.

The difference is control and catalogue rather than capability. The built-in option costs nothing, is integrated with the system's own settings, receives updates through the operating system and cannot be accused of anything untoward, since it is the platform. What it offers is a fixed collection, chosen by the vendor, with no way to add your own video, no playlists, no scheduling, and limited control over when playback happens.

Muro's case is everything around the video: importing your own footage, rotating through sets on a timer, giving each wallpaper its own hours of the day, holding playback until the desktop is clear, and controlling all of it per display from the menu bar. That is a genuine product rather than a wrapper, and it is the reason to add an application for something the system nominally already does.

Take the built-in wallpapers if you want movement and nothing else. Take this if you want your own videos, or if the scheduling and playlist behaviour is something you would actually use, and accept in exchange an application running continuously and a catalogue served from elsewhere.

MIT terms and the separation between code and content

The application is MIT licensed, the permissive choice, and for a free desktop application it raises nothing. The distinction worth holding is between the code and the wallpapers, since a video catalogue is creative work with its own rights and is not covered by a licence on the source. The repository includes a notices file, which is where that attribution belongs and the right place to look before reusing anything from the library. This is not legal advice.

The repository is arranged as an application project rather than a library: the application source, assets, screenshots, a security policy and the notices file, with releases carrying the built artifact.

For anyone evaluating it, the order is short. Check your system version against the feature you actually want, since lock screen playback and the screen saver need macOS 26 while the application itself needs macOS 14. Then import one of your own videos early, because that path avoids the remote catalogue entirely and tells you whether the transcoding and playback behaviour suits your machine before you build a library on top of it.

Editorial conclusion

Muro suits a Mac user who wants moving wallpapers with their own videos, playlists and per-hour scheduling, and who would rather not run a web-wrapped application holding the processor busy for a picture. The system's own dynamic wallpapers remain the better answer if movement alone is what you want, since they cost nothing and add no running application. Check your system version against the specific feature you want before installing, because the application needs macOS 14 while lock screen playback and the screen saver both require macOS 26, and import one of your own videos early, since that path bypasses the remote catalogue the library otherwise updates from.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. MrRockySL/Muro on GitHub
4. README
5. Releases