I Built an LED World Clock That Lives Behind Your Desktop Icons — Without Eating Your CPU

Live wallpapers have a deserved reputation: they look great for a week and then you notice your laptop fan. This one draws vector 7-segment digits that change once a second, and the rest of the time it does nothing at all.

Vector-drawn segments with unlit "ghost" segments behind the lit ones — the detail that makes an LED display look like an LED display.

The LED world clocks on trading floors and in airport halls are one of the great pieces of industrial design nobody thinks about. A grid of cities, 7-segment digits, no decoration, readable from across the room. I wanted one on my desktop.

Every live wallpaper I tried to do it with had the same problem. They are built on the assumption that something is always moving, so they render continuously, and a clock that redraws sixty times a second to show you a digit that changes once a second is an insult to your battery.

A clock has a natural frame rate of one

That is the whole design argument. A display that changes once a second does not need to be redrawn sixty times a second, and a wallpaper that is completely hidden behind a maximised window does not need to be drawn at all.

General-purpose wallpaper engines cannot assume any of that, because they have to be ready for video and shaders and particle fields. A clock can assume all of it. That is the only reason this one can sit behind your icons all day without turning up in your fan noise — not cleverness, just a much narrower problem.

The digits are vector-drawn segments, not a font. That matters more than it sounds: a 7-segment font gives you lit digits on a flat background, and a real display always shows the unlit segments too, faintly. That ghosting is most of what your eye uses to recognise the thing as an LED panel. Drawing the segments as geometry also means it stays crisp at 4K and that the glow is adjustable instead of baked into a bitmap.

Daylight saving is handled automatically per city, which is the kind of feature nobody thanks you for and everybody notices the one morning it is wrong.

Light theme, dot-matrix style. Themes and styles switch live, no restart.

Five ways to install it, which was not the plan

This started as one Windows build. It is now:

• Windows standalone — installer or a portable .exe you can keep on a USB stick. No Steam, no wallpaper manager, no account.
• Microsoft Store — for people who, reasonably, do not download .exe files from strangers.
• Mac App Store — macOS 13 or newer, universal for Apple silicon and Intel.
• Wallpaper Engine — a separate edition in the Steam Workshop, for the large number of people who already have a wallpaper manager and do not want a second one.
• Browser — the whole clock runs on a web page, which turns a spare monitor or an old tablet into a wall clock with no install at all.

Shipping the same idea five ways taught me something unglamorous: the build and release work is not the expensive part. Keeping five store listings, five sets of screenshots and five changelogs consistent is. If you are weighing up a second distribution channel for a side project, budget for the paperwork, not the port.

The Windows version sits on the desktop layer beneath your icons and windows — the same place Wallpaper Engine puts things, without requiring Steam.

What costs money

Twelve cities are free, forever, in both themes with the standard LED style.

Pro is €4.99, once — unlimited cities and the extra display styles. Business is €49 per office, once, for putting it on the screens in a room where people actually need to know what time it is in Singapore.

No subscription, no account, no telemetry. The app does not need a server and does not have one.

There is also an iOS version, which I localised into 51 languages mostly because a clock is one of the rare apps where that is genuinely tractable — the interface is numbers and city names.

Where it is likely to annoy you

It has been out since late September and I have no ratings yet, so this list is what I suspect rather than what I know:

• Multi-monitor setups with mixed DPI, which is where every desktop-layer app eventually goes wrong
• Manufacturer utilities on Windows that also want to own the wallpaper layer
• Very long city names in some locales pushing the grid out of alignment
• macOS spaces and full-screen apps, where "behind the icons" means something slightly different than it does on Windows

If you hit one of these, tell me. There is no crash reporting in it.

Download for Windows and Mac · Microsoft Store · Mac App Store · Wallpaper Engine edition

---

Felix Helleckes — QA & Test Automation Engineer in Cologne. More of what I build: felix-helleckes.github.io