Pricing

DPI means nothing without a size. The number in your file properties is metadata; what platforms calculate is pixels divided by print-area inches. An 800px-wide file printed across a 15-inch area is 53 DPI regardless of the tag. Change the tag and the pixel count stays exactly the same.

Merch by Amazon requires exactly 4500 × 5400 pixels and a file under 25 MB, and a transparent PNG at that size typically lands between 30 and 60 MB. The two rules genuinely conflict. This tool offers a re-encode that strips metadata and re-runs PNG compression without touching a single pixel dimension, which clears the ceiling in most cases.

No. Every check runs through the browser Canvas API on your own machine. You can disconnect from the network and run a check to confirm it.

No, and you should not want any tool to. Missing pixels means the information was never captured; upscaling algorithms invent plausible detail. It can look fine on screen and still print soft on fabric. Re-export from the source file instead.

There are none on single-file checks, and no account is needed. Paid plans exist for batch work: dozens of files at once, auto-fix, multi-platform export. Because the free checks run entirely in your browser, they cost us nothing, so they can stay free.

We track platform changes, but there can be a lag. Every platform spec page says the same thing at the bottom: check the official documentation before an upload that matters.