Format choice barely matters for a photo of a forest. It matters enormously for a sunset.
You can set almost any image as a wallpaper and it'll be fine. The exceptions are the images people most often want as wallpapers — night skies, sunsets, soft gradients, dark scenes with subtle shadow detail. Those are exactly the content types that compression handles worst, which is why format is worth five minutes of your attention.
| Format | Compression | Typical 4K size | Best for |
|---|---|---|---|
| PNG | Lossless | 6–20 MB | Anything with gradients, flat colour, or heavy dark areas. The safe default. |
| JPEG | Lossy | 1–6 MB | Dense, detailed photographic scenes where artefacts have nowhere to hide. |
| WebP | Either | 0.5–4 MB | Web delivery. Roughly 30% smaller than JPEG at the same visual quality. |
Take a sunset that fades from deep purple to orange across 2000 pixels. In an 8-bit image each colour channel has 256 possible values, so that fade might only have 40 or 50 distinct steps to work with. Each step covers 40+ pixels of screen. If nothing breaks up the transition, you see them as stripes.
Two things make this worse:
This is why a wallpaper can look perfect in your browser and visibly striped on your desktop — the browser is showing you the original, and your desktop is showing you the re-encoded copy.
Professionally, by adding a tiny amount of noise (dither) to gradients before export, so the boundaries between tonal steps are broken up. Practically, from your side: start with a lossless PNG so nothing is thrown away before it reaches your screen, and stop your OS re-compressing it afterwards.
Windows copies your image to%AppData%\Microsoft\Windows\Themes\TranscodedWallpaper and re-encodes it as a JPEG. The default quality has historically been around 85, which is enough to reintroduce banding into a clean PNG. You can raise it to 100 with a registry value — create a DWORD namedJPEGImportQuality set to 100 underHKEY_CURRENT_USER\Control Panel\Desktop, then sign out and back in.
Worth knowing: that transcoded file is a real JPEG. If you've lost the original of a wallpaper you liked, you can rename a copy of TranscodedWallpaper to .jpg and open it.
macOS references the original file in place and does not re-encode it. What you supply is what gets displayed, which is one fewer thing to worry about.
Android and iOS both scale the wallpaper to the display and typically compress it. Samsung's gallery is the most aggressive of the mainstream implementations. There's usually no exposed setting; the mitigation is the same as everywhere else — start from the cleanest possible source.
PNG, when it's offered. The extra ten megabytes buys you a file that hasn't lost anything, which matters most in exactly the dark and gradient-heavy scenes people pick as wallpapers. It also gives your OS's own re-encoder a clean input to work from.
JPEG at high quality is genuinely fine for busy, textured images — a dense forest, a detailed cityscape, anything where every region has fine variation. The artefacts are there, but there's nothing smooth for them to stand out against.
WebP is a delivery format. It's excellent at what it does and it's why the thumbnails on this site load fast, but there's no reason to prefer it for the file you actually keep.
AVIF compresses better than WebP and supports 10-bit colour, which raises each channel from 256 to 1024 levels and largely eliminates banding at the source. Support is now broad in browsers but patchy in OS wallpaper pickers, so it's not yet a practical wallpaper format. Give it a couple more years.
Every desktop wallpaper here downloads as a full-resolution 3840 × 2160 PNG. The gallery thumbnails are WebP, purely so the page loads quickly — they're never what you get when you hit download. Browse the gallery →