Wallper 1.0.8: A Rewritten Engine With Lower CPU and RAM Use
The playback engine rebuilt from scratch for lower CPU and memory use, a menu bar runtime, and a live usage graph so you can check the cost yourself.
Three weeks after the first release we rewrote the part of Wallper that actually draws the wallpaper.
That is a mildly uncomfortable thing to say in public. Version 1.0 worked, and people were using it. But it worked in a way that would not have survived the next year of features, and the cost of that showed up in the number that matters most for an app like this: how much of your Mac it spends doing nothing but looking good.
Why the First Engine Had to Go
The honest version is that 1.0 treated a live wallpaper as a video player that happened to sit behind your icons.
That framing is quick to build and expensive to run. A video player is designed to be watched. It decodes every frame at full quality, keeps buffers ready in case you seek, and assumes dropping a frame is worse than spending power. None of those assumptions hold for a wallpaper, which is covered by windows most of the time and looked at directly almost never.
The rewritten engine starts from the opposite premise. It is built to be unwatched, and to spend as little as possible on frames nobody is looking at.
In practice that means faster playback with fewer edge cases, transitions that no longer stutter when switching between videos, and substantially lower CPU and RAM use during ordinary desktop work.
Living in the Menu Bar
1.0.8 also changed where Wallper lives.
The app now runs from the menu bar and sits quietly in the background, rather than occupying the Dock as a window you are expected to keep around. That is the right shape for a utility you configure once and then forget about, and it has a practical benefit: the main window does not need to exist for your wallpaper to play, so the memory that window would have used is simply never allocated.
Windows also remember where you left them. Reopen the app and it returns at the size and position you had it, in the section you were last looking at.
Check the Cost Yourself
Claiming a wallpaper app is lightweight is easy to say and hard to verify, so 1.0.8 shipped the means to verify it.
There is now a live usage graph inside the app showing what Wallper is consuming in real time, and CPU and RAM readouts in the menu bar showing overall system load.
You do not have to take our word for it, and you do not have to go digging through Activity Monitor. If you are a creator previewing several videos in a row it is also a practical way to see what a particular file costs before you publish it.
Current numbers live on the performance page, and the general version of this question is answered in live wallpaper performance on Mac.
What Lightweight Ought to Mean
A wallpaper app is in an unusual position. It runs all day, every day, on a machine where every other process has a better claim to the resources. It is the least important thing on your Mac by definition, and simultaneously one of the only things running continuously from login to shutdown.
That combination means the correct amount of overhead is close to zero, and anything more is a bug rather than a tradeoff.
1.0.8 is where Wallper started treating that as a requirement. Everything since, from Battery-Aware Mode to pausing playback behind full-screen apps, is built on the engine that landed here.
