What Is a Print Ready File for Print on Demand? DPI, Print Areas, and the Mockup Trap
A print ready file for print on demand is artwork that matches three things at once: the pixel dimensions of that specific product's print area, the resolution the provider requires for that print method, and a background that behaves correctly on the product. It's a per product spec, not one universal export setting. A file that's perfectly print ready for a t-shirt front can be unusable on a mug, a tote bag or a pair of socks, and the mockup won't always tell you.
That last part is what costs sellers money. Mockups and print files answer different questions, so a design can look great in the preview and still print soft, stretched or clipped at a seam. This guide covers what "print ready" actually means, the arithmetic behind DPI, why print areas differ per product, and the specific ways files fail after they've already passed the eye test.
What does print ready actually mean?
Four things have to be true before a file is genuinely ready to go to production.
Resolution. Enough pixels for the physical size it will be printed at. This is where most AI generated art fails, and it fails silently.
Dimensions. The file's aspect ratio should match the print area you're filling. If it doesn't, something gets cropped or stretched, and the decision about which one usually isn't yours.
Background. Transparent where you want the product colour showing through, and edge to edge colour where the design covers the whole surface. Getting this backwards is the single most common reason a design ships with a white box around it.
Format and colour. PNG is the safe default across providers because it carries transparency. Both Printful and Printify accept PNG and JPEG, with a 100 MB ceiling on both. Printify also takes SVG at up to 20 MB. For embroidery, Printful asks for PNG specifically, since a JPEG drags in a background that turns into unwanted stitches.
How many DPI does a print on demand file need?
Here's the part that trips people up: DPI isn't a property of your file. It's the result of dividing pixels by printed inches. The same 3000 pixel wide image is 250 DPI on a 12 inch chest print and 100 DPI on a 30 inch blanket. Changing the DPI number in your export settings without changing the pixel count changes nothing at all about what the printer receives.
So the only calculation that matters is:
pixels needed = printed inches x target DPI
A standard adult t-shirt front is roughly 12 by 16 inches. At 150 DPI that's 1800 by 2400 pixels. At 300 DPI it's 3600 by 4800.
The requirements themselves differ by provider and by print method:
| Provider | Most garments | Small, high detail items | Large format |
|---|---|---|---|
| Printful | 150 DPI minimum | 300 DPI for phone cases, stickers, posters and cards | 150 DPI |
| Printify | 300 DPI recommended | 300 DPI | 120 to 150 DPI accepted for leggings, blankets, tapestries |
Printful also advises against going much past 300 DPI. Past that you're adding file size, not print quality.
Now apply that to a typical AI generated design. A 1024 by 1024 image is a perfectly good looking square on screen. Printed 12 inches wide, it's about 85 DPI, which is below every floor in that table. It will still upload. It will still render a convincing mockup. It'll print noticeably soft, and you'll find out from a customer.
This is why the model you generate with matters more than it looks, and why choosing the right AI image model for t-shirt designs is partly a resolution decision, not just an aesthetic one. Upscaling afterwards helps a file clear a hard limit, but it can't invent detail that was never captured. Generate large, scale down. Never the reverse.
Why is the print area different for every product?
Every provider publishes a print area for each product variant: a width and a height in pixels, plus a placement name like front, back or sleeve. Those numbers aren't decoration. They're the canvas the printer actually runs, and they change from product to product for physical reasons.
A t-shirt front is a tall rectangle. A mug is a wide, short strip that wraps around a cylinder. A tote bag's print area often covers the front and the back as one continuous sheet folded at the bottom. Sublimation socks print as several narrow vertical strips, one per leg panel. An all over print backpack has separate panels for the front, the top, the bottom and the pocket.
Two consequences follow, and they're the ones that bite.
Aspect ratio mismatch means something gets sacrificed. Drop a square design into a 3 by 4 print area and either the sides get letterboxed or the top and bottom get cropped. On a wall art size variant that happens to be square while the template reports 3 by 4, a full bleed design can lose a noticeable band off the top and bottom before anyone spots it.
The print area is not always the visible face. This is the one that surprises experienced sellers. On a wrap good, the middle of your file might land on a seam, a fold, or the back of the product. Centre a logo on a tote bag's full print area and it can split across the bottom fold. Fill a sock strip edge to edge and the lettering wraps around the leg where nobody can read it. Print full bleed across a backpack front and a pocket seam can cut a figure in half.
None of that is a defect in the provider's data. It's the difference between the area the printer can reach and the area a customer looks at.
Why does a design look right in the mockup and wrong on the product?
Because a mockup and a print file are two different outputs made for two different audiences.
The print file is the flat artwork the production line runs. It's the truth about what gets printed, and it's usually unglamorous: a design sitting on a transparent background at exact print area dimensions.
The mockup is a marketing image. It exists to convert a shopper. It shows the product photographed or rendered at an angle, in a colour, at a size, usually cropped to look good in a storefront grid.
Both come from the same artwork, so people reasonably assume that a good mockup implies a good print file. It doesn't, in three specific ways:
- Resolution is invisible in a mockup. Mockup images are displayed at a few hundred pixels wide. An 85 DPI file and a 300 DPI file look identical there. The difference only shows up on fabric.
- A mockup often shows one angle. If your design has a problem on the back panel, the far side of a wrap, or the second sock, a front facing render won't reveal it.
- A generic mockup template isn't the same as the provider's render. A template that overlays your art on a stock photo is a design tool. It doesn't know that a specific supplier prints that garment's chest area lower than you expect, or that the tote's print area folds.
The practical rule: treat the mockup as the shopper's view and the print area geometry as the production view, and check both. If you only inspect a small thumbnail, you're checking neither.
Should the background be transparent?
It depends entirely on which of two categories the product falls into, and mixing them up is the classic mistake.
Placed prints (a chest logo on a tee, a design on a hoodie front, art on a tote panel) want a genuinely transparent background. Transparent means "don't print anything here", so the garment colour shows through. Save as PNG with a real alpha channel.
All over and fill products (cut and sew apparel, pillows, blankets, mugs, rugs) have no garment colour to show through. The blank is white and the design covers everything, so your background colour has to be part of the artwork and it has to reach every edge. Leave a transparent margin and you get a white border where the blank shows through.
Two traps worth naming:
- AI models can't generate true transparency. Ask for a transparent background and you'll often get a checkerboard pattern drawn into the actual pixels, which prints as a checkerboard. Generate on a solid, contrasting colour instead, then key that colour out afterwards.
- Removing a background can leave a halo. Semi transparent edge pixels carry whatever colour sat behind them. On a black shirt, leftover white edge pixels read as a glow around your artwork.
The print ready checklist
Before a file goes to production, confirm all six:
| Check | What good looks like |
|---|---|
| Pixel dimensions | Match the specific variant's print area, not a generic guess |
| Resolution | Meets the provider's floor for that print method, ideally 300 DPI for small detailed items |
| Aspect ratio | Matches the print area, so nothing is cropped or stretched without your say so |
| Background | Transparent for placed prints, edge to edge colour for all over products |
| Format | PNG for anything with transparency or going to embroidery |
| Visible face | The subject and any text land where the customer actually looks, clear of seams, folds and hardware |
How ApparelHub handles this part
We built the platform around the assumption that this is the step sellers shouldn't have to do by hand, so here's specifically what happens and where it stops.
When you build a product, ApparelHub reads the real print area for the variant you selected from your own connected provider account, so the file is composed against that product's actual geometry rather than a default. Where the print area doesn't line up with the visible face, the platform carries a layout library for those products, built by rendering test files against live providers and checking the result, so designs land on the panel people see rather than across a fold. Mockups are generated by the fulfillment provider itself, which means what you're looking at is that supplier's own render of that variant rather than a generic overlay. Uploads that come in under a working resolution floor get scaled up so they don't dead end, and there's a design quality check before anything syncs to a store.
The boundaries, stated plainly. Upscaling clears a minimum, it doesn't add detail that was never in the image, so generating at a large size is still on you. You still choose placement and size. Embroidery is a separate pipeline with its own constraints around thread colours and stitch density, and a file that's print ready for direct to garment isn't automatically embroidery ready. And providers publish their own specs that change over time, so their documentation stays the final word.
Printful, Printify and Gelato are all live, and you can build against any of them from the same catalog, which is what makes connecting multiple print providers to one storefront practical rather than a chore. Shopify, WooCommerce, Wix and TikTok Shop are all live sales channels. If you'd rather your own AI agent ran this whole loop instead of clicking through it, the Agent API, MCP connector and Claude skill expose the same pipeline. If you're coming from a design tool and wondering about the handoff, we covered uploading AI designs to Printful and Printify separately.
FAQ
Is 300 DPI always necessary for print on demand? No. Printful accepts 150 DPI on most garments and reserves 300 DPI for small, detailed items like phone cases and stickers. Printify recommends 300 DPI generally but accepts 120 to 150 DPI on large format products like blankets. Match the floor for the specific product and print method rather than applying one number everywhere.
Can I just upscale a small AI image to make it print ready? Upscaling gets a file past a hard minimum, and it's better than being blocked. It can't recover detail the original never had, so an upscaled 1024 pixel image printed large will still look softer than one generated large from the start. Use it as a rescue, not a workflow.
Why does my design have a white box around it on a dark shirt? The file almost certainly has no real transparency. Either it's a JPEG, which can't store transparency at all, or it's a PNG that was flattened onto white. Export as PNG with an alpha channel, and check it against a dark background before you build the product.
What size should my print file be for a t-shirt? For a standard adult front print of about 12 by 16 inches, 1800 by 2400 pixels gets you to 150 DPI and 3600 by 4800 gets you to 300 DPI. Confirm the exact print area for the specific blank you're using, because it varies by garment and by supplier.
Does the same file work across Printful, Printify and Gelato? Often yes for a simple chest print, since the print areas are similar. It's not guaranteed, because each supplier defines its own print area dimensions per variant and its own resolution floor. If you're comparing suppliers for the same product, our Printful vs Printify vs Gelato breakdown covers where they diverge.
Getting this right without doing it by hand
Print ready isn't a single export preset. It's a per product agreement between your artwork and a specific supplier's print area, and the mockup is the wrong place to verify it.
If you'd rather the geometry, the resolution floors and the visible face problem were handled as part of building the product, start free at ApparelHub. You bring the designs and the storefront, and you keep your own provider accounts and your own margins.
Sources: Create the perfect DTG file, Printful, What type of print files does Printful require?, What type of print files does Printify require?, What dimensions should my design be?, Printify