# Lively Wallpaper: Animated Windows Desktops, Screensavers and the Limits of the WinUI 3 Build

> Lively Wallpaper is a GPL-3.0 C# application that turns video, web pages and full applications into Windows desktop wallpapers and screensavers. This review covers how it renders, how to install it and where the documented behaviour stops.

**rocksdanister/lively** — Free and open-source software that allows users to set animated desktop wallpapers and screensavers powered by WinUI 3.

- Repository: https://github.com/rocksdanister/lively
- Website: https://rocksdanister.com/lively
- Stars: 19,704 · Forks: 1,366
- Language: C#
- License: GPL-3.0
- Published: 2026-09-21 · Updated: 2026-09-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/rocksdanister-lively

## The Windows-only problem Lively Wallpaper addresses

Windows has no native mechanism for animated desktop wallpaper. The static image is drawn by the shell, and anything that moves has to be a separate process drawing behind the icons. Lively Wallpaper exists to manage that process, one wallpaper at a time, and to keep it from eating the machine while you work.

The project is aimed at Windows 10 and Windows 11 users who want motion on the desktop without paying for it. The README is explicit that it is "fully opensource & free; no blackmagic, no features behind paywall." That positions it against commercial wallpaper engines rather than against the operating system itself.

The scope is wider than video loops. The feature table lists three wallpaper types: video and GIF files with fixed resolution and performance, web pages with variable resolution and performance, and applications or games, including Unity and Godot builds, which are interactive. Screensavers reuse the same wallpapers, and the README states that any wallpaper can be used as one.

That last point is the real differentiator. A screensaver mode that accepts the same content as the desktop means you configure one library, not two. The README notes multiple monitor support for screensavers, which is where most simple screensaver tools fall down.

## How Lively renders wallpapers: mpv, Chromium and WinUI 3

There are three rendering paths, and which one runs depends on the wallpaper you set. Video and GIF files go through hardware accelerated playback using mpv or vlc, with customizable video filters. Web pages and Shadertoy URLs go through what the README calls a "minimal webpage renderer powered by chromium." Applications and games run as their own process, which is why the feature table marks them interactive with variable resolution and performance.

The shell around all of this is WinUI 3 plus WindowsAppSDK, which is where the Windows 11 visual style comes from. The repository's primary language is C#, and the default branch is named core-separation, a hint that the core is being split from the UI, though the README does not document what that split will contain.

The performance story is about suppression rather than raw speed. The README states that wallpaper playback pauses when a fullscreen application or game runs, at roughly 0% CPU and GPU usage. It also pauses on battery power, and pauses during a remote desktop session. Playback rules can be set based on the running foreground application, so you can, for example, let a wallpaper run while a browser is focused and stop it while an editor is.

For developers, Lively exposes an API for interactive wallpapers that the README says can read hardware sensors, the audio graph and music information. Machine learning inference is also listed as a way to build dynamic wallpapers. Both are documented in the project wiki rather than in the README, and the wiki badge is marked WIP, so expect gaps.

## Installing Lively Wallpaper and setting your first wallpaper

There are two distributions. The Microsoft Store listing requires Windows 10 1809 or above. The standalone installer from the GitHub releases page requires Windows 10 1903 or above. The README links a wiki page titled Differences Between Distributions for choosing between them, and notes that the installer may produce a SmartScreen warning, linking to issue 9 for discussion.

Download the installer from the releases page and run it. If SmartScreen blocks it, the project points to that issue thread rather than offering a workaround in the README.

Once installed, the documented first workflow is drag and drop. The README states: "Just drag'n'drop media or webpages into lively to set as wallpaper." A video file dropped onto the window becomes a video wallpaper; a URL becomes a web wallpaper.

The README also documents command line control, which is the path for scripting and for integration with Python or AutoHotKey. The wiki page Command-Line-Controls is the reference for the argument names, and the README does not reproduce them.

```bash
# The README states Lively can be controlled with command line arguments.
# Argument names live in the wiki page Command-Line-Controls.
```

The same pattern applies to screensavers. The README says any wallpaper can be used as a screensaver and links the Screen-Saver wiki page for the setup steps, which are not in the README itself.

## Where Lively Wallpaper fails or is the wrong tool

The first limitation is the platform. This is a Windows application built on WinUI 3 and WindowsAppSDK. There is no macOS or Linux build in the repository, and the README does not discuss one. If your team is mixed-platform, Lively covers only the Windows machines.

The second is the installer experience. The README acknowledges that the installer may give a SmartScreen warning. That is a real friction point in managed environments where users cannot click through warnings, and the README offers a discussion link rather than a signed-installer guarantee.

The third is performance variance. The feature table itself marks web and application wallpapers as variable in both resolution and performance. A heavy web page or a game running as wallpaper will consume what it consumes; the pause rules mitigate this but do not cap it. The ~0% CPU and GPU figure in the README applies to the paused state during fullscreen applications, not to active playback.

The fourth is documentation maturity. The docs badge is labeled WIP. The API, machine learning, command line and screensaver pages are all wiki links from the README, which means the authoritative details sit outside the repository and can drift from the code. If you are building an interactive wallpaper against the API, budget time for reading the source under src/.

Finally, this is a desktop personalization tool, not an infrastructure component. There is no server mode, no fleet management and no policy layer described in the README.

## Lively Wallpaper versus Wallpaper Engine

The obvious comparison is Wallpaper Engine, and the difference is not the feature list. It is the distribution model and the content ecosystem. Wallpaper Engine is a paid product on Steam with a Workshop for sharing wallpapers. Lively Wallpaper is GPL-3.0 and free, with no paywall, and its content comes from files and URLs you supply yourself.

That changes the workflow. With Lively you drag in a video, point at a web page, or run an application. There is no built-in marketplace to browse, and the README does not describe one. If discovering other people's wallpapers matters more to you than controlling your own, the Workshop model is a better fit.

The second difference is extensibility. Lively exposes an API for hardware readings, the audio graph and music information, plus machine learning inference for dynamic wallpapers. That is a developer-facing surface, and it is the reason someone would pick Lively over a closed engine even if both render video equally well. The trade-off is that you are writing against a WIP wiki.

The third difference is licensing. GPL-3.0 means if you distribute a modified Lively, the source has to travel with it. That is fine for personal use and for contributions back to the project, and it is a constraint for anyone hoping to embed Lively in a closed product.

## Maintenance, releases and what GPL-3.0 means for you

The last push to the repository was on 2026-04-30, and the repository is not archived. The most recent release is v2.2.1.0, tagged "Big Update - Follow Up" and published on 2025-09-18. Before that, v2.2.0.0 ("Big Update") landed on 2025-09-03, and v2.1.0.8 ("Better Everything + hotfix") on 2024-05-31.

That release cadence is worth reading carefully. There was a gap of more than a year between v2.1.0.8 and v2.2.0.0, then two releases two weeks apart, then no release for roughly seven months up to the last push. The project is not abandoned, but it does not ship on a predictable schedule. If you depend on a specific behaviour, pin a version rather than tracking latest.

The default branch is core-separation, which is not the name you would expect for a stable branch. The README does not explain the branch strategy, so anyone building from source should check which branch the release tags point at before assuming the default branch is production-ready.

On licensing: Lively is GPL-3.0. For an individual installing it on a personal machine, that is straightforward. For an organization distributing a modified build, the GPL requires the corresponding source to be made available under the same license. This is not legal advice, and the LICENSE file in the repository is the authoritative text.

Upgrade cost is low for end users, since the Microsoft Store distribution updates through the Store. The standalone installer is a manual download each time, and the README does not describe an auto-update mechanism for it.

## Conclusion

Adopt Lively Wallpaper if you run Windows 10 1903 or above, want video or web wallpapers without a subscription, and can accept that the installer may trigger a SmartScreen warning. Do not adopt it if you need macOS or Linux support, or if the wallpapers you want are DRM-protected files that no renderer can decode. Before installing, confirm which distribution matches your Windows build by reading the Differences Between Distributions wiki page, and check the release notes for the version you intend to run.

## FAQ

### How do I install Lively Wallpaper?

Install it from the Microsoft Store if you are on Windows 10 1809 or above, or download the installer from the GitHub releases page if you are on Windows 10 1903 or above. The README notes the installer may give a SmartScreen warning, and links a wiki page for choosing between the two distributions.

### How do I use Lively Wallpaper on Windows 11?

The README states you can drag and drop media or webpages into Lively to set them as wallpaper. Windows 11 is supported through the WinUI 3 and WindowsAppSDK shell, and the Microsoft Store listing covers Windows 10 1809 or above.

### Can Lively Wallpaper be used as a screensaver?

Yes. The README states that Lively supports the Windows screensaver, that any wallpaper can be used as a screensaver, and that multiple monitors are supported. Setup steps are in the Screen-Saver wiki page rather than the README.

### Does Lively Wallpaper support two monitors?

The README documents multiple monitor support for the screensaver feature. It does not describe per-monitor wallpaper assignment in the README itself, so check the wiki for the current behaviour.

### How do I use Lively Wallpaper on a laptop?

The README states that wallpaper playback can be set to pause when running on battery power, which is the laptop-specific behaviour it documents. Otherwise the workflow is the same as on a desktop: drag and drop media or webpages into Lively to set them as wallpaper.

### How do I use Lively Wallpaper on a PC?

Install it from the Microsoft Store or the GitHub releases installer, then drag and drop media or webpages into Lively to set them as wallpaper. The README also documents command line control from a terminal and integration with Python or AutoHotKey.

## Sources

- [License: GPL-3.0](https://github.com/rocksdanister/lively/blob/core-separation/LICENSE)
- [Project website](https://rocksdanister.com/lively)
- [README](https://github.com/rocksdanister/lively/blob/core-separation/README.md)
- [Releases](https://github.com/rocksdanister/lively/releases)
- [rocksdanister/lively on GitHub](https://github.com/rocksdanister/lively)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/rocksdanister-lively