"Your image is too low DPI — please upload at 300 DPI" is one of the most confusing errors a print shop can send you. The reason it's confusing is because DPI is a metadata hint, not a property of your image — and that fact isn't obvious to anyone whose print-shop workflow is "email them a file and hope".
This piece explains what DPI really is, when the print shop's rejection means a metadata problem (which our DPI checker fixes in 3 seconds without touching pixel data), and when it means a genuine resolution problem (which no metadata rewrite can fix — you need more pixels, full stop).
Three concepts, often conflated
Nearly every DPI conversation confuses three different things. Fix that and the whole print-shop error stops feeling mysterious.
1. Pixel count (resolution)
The number of individual pixels in your image, expressed as width × height. A 3000×2000 pixel image contains exactly 6 million pixels, regardless of DPI, regardless of print size, regardless of anything else. This is a physical property of the file — it doesn't change unless you resize.
2. DPI (dots per inch)
A metadata hint stored in the file that tells print software "when you print this image, render it at N pixels per inch". That's it. DPI is a print-time instruction, not a description of the image itself. A 3000×2000 pixel image can be tagged 72 DPI, 150 DPI, 300 DPI or 600 DPI — the pixels are identical either way.
3. Print size (physical dimensions)
The size the image actually comes out on paper. This is a derived value: print size = pixel count ÷ DPI. Change either input and the print size changes:
- 3000 pixels ÷ 72 DPI = 41.7 inches (a huge poster)
- 3000 pixels ÷ 150 DPI = 20 inches (a large photo)
- 3000 pixels ÷ 300 DPI = 10 inches (a standard photo)
- 3000 pixels ÷ 600 DPI = 5 inches (a small print)
What the print shop is actually saying
"Please upload at 300 DPI" almost never means literally "change the DPI tag". What the shop means is:
"We're printing this at a specific physical size. At 300 DPI, that requires N × M pixels. Your file doesn't declare a DPI, or it declares 72 DPI, and when we compute what physical size your pixels correspond to at your declared DPI, the print size is too small — or the software is refusing to enlarge it beyond the declared print size."
Two very different fixes for what looks like one error. Which fix applies depends on whether you have enough pixels.
Diagnosis: do you have enough pixels?
The print shop's target print size (say 8×10 inches) times 300 DPI gives you the required pixel count (2400×3000). Compare to what your file actually has:
- If your file has 2400×3000 pixels or more: you have enough pixels. The problem is metadata — your file is probably tagged 72 DPI, so the shop's software thinks the image is meant to be printed 33×42 inches (2400÷72). Rewrite the DPI tag to 300 and resubmit. Our DPI checker does this in one click without re-encoding the image.
- If your file has fewer pixels: you have a real resolution problem. No metadata change fixes it. You need one of: (a) the original higher-resolution source, (b) to accept a smaller print size (say 4×5 inches instead of 8×10), or (c) to accept the slightly-soft print quality that upscaling produces.
Why the metadata rewrite works without quality loss
JPEG files store DPI in the JFIF header — specifically the density fields at bytes 11–15 of the APP0 segment. Those five bytes are completely separate from the compressed image data that occupies the rest of the file (typically millions of bytes). Rewriting the density fields is a five-byte patch. No decompression, no re-encoding, no quality loss. The output file is byte-identical to the input except for those five bytes.
This is why our DPI checker can rewrite DPI in about 20 milliseconds. It's not doing much work — it's patching a specific offset in the file header. The pixel data isn't touched.
Common DPI targets
- 72 DPI — the historical "screen" default from CRT-era Apple monitors. Utterly irrelevant to modern screen display (browsers render pixels, not inches) but still the default in many photo-processing tools. If your file was created by anything that outputs "web-optimised" images, it's probably tagged 72 DPI.
- 96 DPI — Windows default screen DPI. Also irrelevant to actual print.
- 150 DPI — draft-quality print. Posters viewed from more than 1 metre look fine at 150 DPI. Not recommended for anything held in hand.
- 200 DPI — decent print quality. Adequate for flyers, cheap postcards, promotional handouts.
- 300 DPI — the industry standard for anything held in hand. Photos, business cards, high-quality flyers, magazine pages, brochures.
- 600 DPI — fine-art print and typography-heavy layouts. Overkill for photography (the eye can't resolve the detail); useful when combining photos with fine printed text.
Practical workflow when the print shop rejects your file
- Read the actual DPI of your file with our DPI checker. It shows the current DPI plus the print size that DPI implies.
- Compute the required pixel count. Print size in inches × 300 = pixels needed on each edge.
- Compare to your actual pixel count. If you have enough, rewrite the DPI to 300 (metadata fix, no quality loss). If not, you need more pixels or a smaller print.
- Resubmit to the print shop. The shop's software will now correctly compute the print size and accept the file.
Bottom line
"Too low DPI" is a two-question diagnostic: do you have enough pixels? and does the file declare the right DPI?Most of the time both answers point at the same fix (rewrite the DPI tag). Sometimes only the pixel-count question matters (you need more pixels; no metadata change helps). Either way, the diagnosis takes 30 seconds if you know what you're looking at — and our DPI checker does the read and the rewrite in the same window.