Seamless pattern guide
What resolution and DPI should a seamless pattern have?
Pixel dimensions determine how much image information a raster tile contains; PPI or a printer’s DPI requirement determines how large those pixels can be printed.
Pixels and physical size are different measurements
A raster pattern might be 8192 by 8192 pixels, but pixels alone do not specify inches or centimeters. Physical size appears only when those pixels are assigned a density. Divide pixel width by pixels per inch to estimate print width. The same file can therefore print at different dimensions without changing its stored pixel count.
At 150 pixels per inch, an 8192-pixel tile spans about 54.6 inches, or 138.7 centimeters. At 300 pixels per inch, it spans about 27.3 inches, or 69.3 centimeters. The higher-density version uses more pixels within every inch and normally preserves finer detail at close viewing distance. Because the tile repeats, it can still cover a surface larger than either measurement; those figures describe one repeat unit.
Use the destination specification
There is no single correct DPI for every material. Many general print workflows request 300 PPI for close-viewed paper products. Spoonflower uses 150 DPI as its platform reference for fabric and converts uploads to that density. Large wallpaper, signage, and stage graphics may use lower effective resolution because viewers stand farther away. Always check the current specification of the exact printer, product, and substrate.
DPI technically describes printer dots, while PPI describes image pixels, but upload interfaces often use the terms interchangeably. The safe calculation is based on pixels and the service’s stated value. If a service requires a four-inch repeat at 150 PPI, prepare 600 pixels across. If it requires the same repeat at 300 PPI, prepare 1200 pixels across.
Changing metadata is not the same as resampling
Turning off resampling in an image-size dialog changes the reported physical size and PPI relationship without inventing pixels. Turning resampling on adds or removes pixel data. Downsampling a large master for a smaller output is usually predictable. Upsampling a small tile asks software to estimate detail that was never captured and can soften edges, amplify compression, or disturb a repeat.
Some AI and content-aware upscalers process the edges as if they were unrelated image boundaries. That can break a tile that was seamless before enlargement. If upscaling is unavoidable, use a wrap-aware method and retest the result in a 3 by 3 grid. Keep the original dimensions proportional and avoid cropping a few pixels from only one side.
Prepare separate print and web copies
For print, retain the high-resolution original, select the intended physical repeat size, and export according to the printer’s format and color instructions. For the web, dimensions and compressed byte size matter more than a 72 or 300 PPI metadata label. Browsers render the requested CSS pixels and device pixels; downloading an 8K original for a small background wastes bandwidth.
Create an optimized web derivative while preserving the complete tile boundaries. Test both versions independently, label them clearly, and never overwrite the master. A small CSS tile may repeat more often and reveal compositional tracking that was subtle at print scale. Resolution is therefore both a technical calculation and a design decision about how frequently the motif should appear.
