Printify image requirements, and preparing a whole collection at once

Two different sets of images leave your computer for every POD product: the file that gets printed, and the pictures that sell it. They have nothing in common.

Last checked against the platform's own documentation on 22 September 2026.

Two jobs, two kinds of file

A print-on-demand product needs a print file — the artwork that goes onto the garment or poster, at print resolution — and it needs listing images, the mockups a shopper actually looks at. Mixing them up is the most common way to end up with a blurry shirt or a 40 MB listing photo that will not upload.

The print file

Printify's guidance recommends 300 DPI for JPEG and PNG print files, while noting that a lower resolution can be enough depending on the product and how large the print area is. Its help centre puts the practical floor at around 150 DPI for sharp results on many products. PNG is the usual choice for garments because it carries transparency, so the design sits on the fabric rather than on a white rectangle.

One caveat worth keeping in mind: DPI on its own guarantees nothing. Resolution can be raised artificially, and an upscaled 72 DPI image relabelled as 300 DPI has no more detail than it started with. What matters is the pixel count relative to the physical print size.

Printify's Product Creator shows the requirements for each individual product once you click Upload, and reports the resolution of the file you gave it. That per-product figure beats any general rule, because the print area on a mug and the print area on an all-over hoodie are not remotely comparable.

The listing images

These follow the rules of wherever you are selling, not Printify's. If the products are going to an Etsy shop, that means at least 2000 px on both sides and a landscape shape — the Etsy image guide covers why. If they are going to Pinterest as well, that is a different shape again.

Where the time goes

Preparing one product is quick. Preparing forty is not, and the work is entirely mechanical:

1. Export the print file at the right size for each product type.
2. Produce listing mockups for each design.
3. Sort them so each design's files sit together rather than in one flat pile of four hundred JPEGs.
4. Upload, match each file to the right product, publish.

Step three is the one people skip and then regret. Once a folder holds several hundred images named after templates rather than designs, matching them back to products is guesswork.

A folder structure that survives contact with a real catalogue

The convention that works is one folder per design, with the print file and the mockups separated inside it:

Everything for one product is in one place, the names say what they are, and upload tools that expect this layout can read it without being told. The alternative — one folder of everything — works until roughly the tenth design.