FAQ
Can I get a wallpaper with a single request?
Section titled “Can I get a wallpaper with a single request?”Yes. GET /api/wallpapers/random/image returns the image itself, ready to save
or set. See retrieving images.
Does Wallpaper Server have authentication?
Section titled “Does Wallpaper Server have authentication?”No. There is no built-in authentication or authorization. Keep it on a trusted network, or put it behind a reverse proxy that adds TLS and access control before exposing it. See the API overview.
Which image formats are supported?
Section titled “Which image formats are supported?”.jpg, .jpeg, .png and .webp by default, configurable via
supported_extensions. See supported formats.
Are there prebuilt binaries?
Section titled “Are there prebuilt binaries?”The documented installation paths are building from source, Docker (built locally), and a systemd service. See installation.
Does deleting a wallpaper remove the file?
Section titled “Does deleting a wallpaper remove the file?”Yes. Deletion removes the original file from disk, plus its cached copy and thumbnail. This is destructive — see uploading and managing.
How do I change the wallpaper on a schedule?
Section titled “How do I change the wallpaper on a schedule?”Fetch the direct-image endpoint from a scheduled task. See shell and cron and the other automation guides.
How do filters combine?
Section titled “How do filters combine?”With AND — every filter must match. An over-constrained query can match nothing. See the filter reference.
Where are cached files and uploads stored?
Section titled “Where are cached files and uploads stored?”In XDG-style directories by default (~/.cache/wallpaper-server and
~/.local/share/wallpaper-server/uploads), both configurable. See
caching and storage.
Do I need a database?
Section titled “Do I need a database?”No. Wallpaper Server is a single binary with an in-memory index and an on-disk cache. See architecture.