A background is manufactured here, not edited
Everything on this page is drawn from numbers. There is no photograph anywhere in it and no place to put one — a background comes out of a base colour, a stack of layers and a pair of dimensions, and nothing else goes in. That is a narrower product than it sounds, and it is the reason the dimension field is a first-class control rather than an export option.
The thing most tools get wrong is treating the size as the last question. A background exists to be exactly some number of pixels: the panel it sits behind, the card a link preview crops to, the sheet it will be printed on. So the size sits in the action bar next to the download, six common figures are one keypress away, and any other pair of numbers can be typed. A physical size with a resolution beside it resolves to pixels in the same control.
| Size | What it is for | Megapixels |
|---|---|---|
| 1920 × 1080 | The commonest desktop panel | 2.1 |
| 3840 × 2160 | A large external display | 8.3 |
| 1080 × 1920 | An upright phone screen | 2.1 |
| 1200 × 630 | The link preview card | 0.8 |
| 1500 × 500 | A profile banner | 0.8 |
| 2480 × 3508 | A4 at 300 dots per inch | 8.7 |
Working the stack from the ground up
A design is a ground colour with layers over it. Most are two or three; the ceiling is eight, past which the preview stops being interactive and the result stops being a background. Each layer carries a blend mode, an opacity and a seed, and the order is yours to change.
A gradient layer is a shape, an angle and a list of stops, interpolated in OKLCH by default. A flat layer is one colour, which is more useful than it sounds once a blend mode is on it — a multiply of a warm tone over a cold ramp costs one layer and changes the whole surface. A noise layer is a value per pixel or per cell, usually at a low opacity over everything else, and it is what stops a generated background looking generated.
Every generative layer shows its seed in the toolbar. Rolling it again replaces that layer’s parameters with a new set derived from a new number, and the design in the address bar keeps up, so a link reproduces what is on the canvas rather than a design that happens to share a seed with it.
- G S N
- add a gradient, a flat colour or a noise field
- R
- roll the selected layer again
- Shift R
- roll every layer in the stack
- D
- turn the dither pass on and off
- 1 – 6
- jump to one of the six output sizes
- Enter
- draw at full size and save
- Ctrl Z
- step back through fifty changes, Shift to step forward
What the preview is and is not
The canvas shows the design at roughly a quarter of the pixels it will be saved at, and half of that again while a slider is moving. That is a deliberate trade: a 4K design is eight million pixels through a per-pixel loop, and computing all of them on every frame of a drag would make the control feel broken. The renderer is the same one either way, and geometry is measured in fractions of the frame, so what you approve is what you get.
One thing genuinely differs. Grain is counted in output pixels, so a one-pixel cell in a 3840-wide file is drawn as a one-pixel cell in a 1400-wide preview and therefore looks about three times coarser on screen than in the file. That is stated beside the control rather than left to be discovered after a download.
Above about thirty megapixels the export stops being one allocation the browser will make happily, so it is drawn in horizontal bands instead. The page asks first, says how many bands, and produces a file identical to the one a single pass would have produced — every value in the renderer is a function of the absolute pixel coordinate, so a band boundary leaves no seam. Past a hundred megapixels the canvas cannot be allocated at all and the export is declined with the measured figure named.
Two things this generator will not do
Both are limits of the operation, not of this build.
- Banding cannot be removed from an eight-bit file, only traded. A long flat ramp has fewer available levels than it has pixels to cross, and no amount of care in the renderer changes that — the dither pass swaps a visible step for about one level of noise, which is a better artefact but is still an artefact. A ramp that has to be perfectly smooth needs a format with more than eight bits per channel, and none of the three formats offered here has one.
- This page reads no photograph. A colour cannot be lifted from a picture you drop here, because there is nowhere to drop one; what comes out is a rectangle of manufactured pixels. Putting a design behind a person or a product is the change-background page's job, and it uses the same library.
Questions the pixels raise
How big should a desktop background be?
Why does my gradient come out in stripes?
Can I take the CSS rather than the file?
What is OKLCH actually doing to the ramp?
PNG, JPG or WebP for a background?
Can I add shapes, or take the colours from a photo?
Can I put one of these behind a person?
The same canvas, opened differently
Five routes open this generator in a different starting state, because the first thing on screen should match what you came for. Each one is the same instrument with a different preset and a different size already selected; nothing is locked off, so a size route will still take a typed pair of numbers and the flat-colour route will still take a gradient on top.
Where the arithmetic is set out
Three written pages carry the reasoning the controls only assert. One works through the dimensions — screens, cards, banners, paper at 300 dots per inch — and the conversion from millimetres. One takes the banding apart: 256 levels, a ramp longer than that, and what the dither switch trades to hide the steps. The last weighs the same design as a PNG, a JPG and a WebP and says which number goes up when the grain goes on.
They are the long form of four of the answers above, and they are the only pages here that are meant to be read rather than used.
Pictures you open and backgrounds you draw never leave this page. They are cut out and drawn by your browser, and the file is written straight to your disk.