▮ Depth Paper

Generator · Pair mode

Matching wallpapers for two phones

One pair-seed, two coordinated wallpapers. Split a single gradient across both screens so the phones reassemble one picture, or render the same composition in complementary palettes — then export each side separately at its own phone's exact native pixels. The link is the pair: share this page's URL and the other phone gets its half from the same seed.

Pair seed— Mode— Device A— Device B— Exportidle
A B

How this pair mode works

Everything on this page hangs off one integer: the pair-seed in the readout. In split-field mode, the engine builds a single mesh gradient on a virtual canvas as wide as both phones together, then cuts it — phone A's wallpaper is the left window, phone B's the right, each vertically centered and rendered at its own native resolution. There is no seam to blend because there is only one field; the grain, the blobs, and the color flow continue across the gap between the phones.

Complementary mode uses the pair-seed differently: both phones get the full composition — the same seeded control-point layout, scaled to each screen — but phone B's palette is derived from phone A's by rotating every color stop halfway around the color wheel at the same saturation and lightness. The two wallpapers are recognizably the same picture in opposite color worlds, which is what makes them read as a deliberate set rather than a coincidence. In both modes each export button renders its side at that device's exact native pixels, from the same two-source-verified device table the rest of this site uses, in short slices so the page stays responsive.

The honest limits: the pair is deterministic — the same pair-seed, mode, devices, palette, and point count reproduce the same two wallpapers, forever — but the downloaded files' bytes can differ between browsers, because PNG encoders differ. Split-field pairs are composed for phones of broadly similar height; pairing a phone with a much taller one crops the shorter window from the shared field's middle, which is deliberate and reported by the preview rather than hidden. And what happens after download belongs to the phones: perspective zoom or launcher cropping can shift edges, which is a setting on each phone, not a property of the pair.

Frequently asked questions

What makes these wallpapers a matching pair?
They come from one recipe. A single pair-seed drives both renders, in one of two modes: split field cuts a single continuous gradient across the two screens, so the phones set side by side reassemble one picture; complementary palette renders the same composition twice, once in the palette you chose and once in its hue-opposite. Either way the pair is coordinated by construction, not by eyeballing two separate wallpapers.
What is the difference between the two modes?
Split field is one gradient shared across two phones — colors flow off the right edge of phone A and onto the left edge of phone B, because both wallpapers are windows into the same mathematical field. Complementary palette gives each phone a complete gradient of its own with the identical layout, but phone B's colors sit opposite phone A's on the color wheel at the same depth and saturation — a matched pair rather than a jigsaw.
Do both phones have to be the same model?
No — that is the point of the two device pickers. Each side exports at its own phone's exact native pixels, taken from the same two-source-verified device table the maker uses, so an iPhone and a Pixel can share a pair with neither wallpaper stretched or cropped. The previews render at one common scale, which is why a larger phone honestly previews larger.
How do two people share one pair?
Send the link. The pair-seed, mode, both devices, palette, and point count all ride this page's URL, so whoever opens it sees exactly the same pair — then each person presses their own export button and downloads their side at their phone's resolution. There is no account and no stored image; the link itself is the pair.
Is anything uploaded or stored?
No. Both renders are computed and drawn entirely inside this page — no server rendering, no account, and nothing you make is sent or kept anywhere. 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