▮ Depth Paper

Gallery · Curated seeds

Gradient wallpapers, curated as seeds

A hand-picked set of mesh gradient wallpapers — except nothing here is a stored image. Every entry is a visible seed rendered live by the same engine as the maker, so each one downloads at your phone's exact native pixels, and each one opens in the maker if you want to push it further. Pick your device once; every download below follows it.

Entries— Palettes8 Device— Native px— Exportidle

How this gallery works

Each card above is a recipe, not a file: an integer seed, one of the site's eight original palettes, and a control-point count. Your browser feeds that recipe to the same mesh-gradient engine behind the wallpaper maker and paints the result live — the thumbnail is the actual wallpaper at a lower sampling density, not a preview image someone exported once. Because entries are seeds, the gallery is exactly reproducible: the same card renders the same gradient on every visit, on every machine.

The device selector drives every download. Choosing a phone re-shapes the thumbnails to its aspect ratio and sets the export size to its native pixels — the dimensions in the readout come from a device table in which every entry was cross-checked against two independent published sources. Pressing a download button re-renders that entry's field at full resolution in short slices, so the page stays responsive, then hands the pixels to your browser's PNG encoder. "Open in maker" passes the same recipe on as URL parameters instead of rendering it, which is all a deep link needs to be when entries are seeds.

The honest limits: this set is curated by eye, and taste is not a measurement — the selection rule was to keep renders that hold up on a lock screen, cover all eight palettes, and reject any seed that collapses into a tight dark smudge, but your favorite seed may still be one the curators skipped, and the maker exists for exactly that case. Color values are deterministic; the downloaded file's bytes can still differ between browsers because PNG encoders differ. And your phone's own settings have the last word on display — perspective zoom and launcher cropping are properties of the phone, not of any file.

Frequently asked questions

Are these wallpapers image files stored on a server?
No. Every entry in this gallery is a recipe — an integer seed, a palette, and a control-point count — and your browser renders it live with the same engine the wallpaper maker uses. The thumbnail you see and the file you download are the same mathematical field, just sampled at different resolutions, so the gallery holds no image assets at all.
What does “Open in maker” do?
It hands the entry's full recipe — seed, palette, point count, and your selected device — to the wallpaper maker as URL parameters. The maker opens showing exactly the wallpaper you clicked, and from there you can change the seed, palette, device, or point count to make it your own.
Will the download match my phone's screen exactly?
Yes. Pick your model above and every download button renders at that panel's native pixels, taken from a device table in which each entry was cross-checked against two independent published sources. The readout shows the exact pixel dimensions before you download, and the composition you saw in the thumbnail is preserved because the gradient scales with the canvas rather than being cropped to it.
How were these entries chosen?
By eye. Candidate seeds were rendered through the real engine and reviewed, and only the ones that hold up as wallpapers were kept — the selection covers all eight palettes with calm and dramatic compositions in each, and any seed whose render collapses into a tight dark spot was rejected. Curation is editorial judgment, not an algorithm, which is why the set is small.
Can I use these wallpapers freely, and is anything uploaded?
Wallpapers rendered here are generated on your device from original palettes and are yours to use freely, personal or commercial. Nothing is uploaded, stored, or watermarked — the rendering happens inside this page, and the site's security policy blocks requests to other origins, so the no-upload claim is enforced by your browser rather than just stated.

Related