300 DPI vs 72 DPI: Why Product Images Only Need Pixels

A printer tells you the catalog files are "only 72 DPI" and must be 300. You open the same photo, type 300 into a box, hit save, send it back — approved. Nothing about the image changed. Not one pixel was added. That round trip is the cleanest proof of what the 300 DPI vs 72 DPI argument really is: an argument about a number written in the file's header, not about how much detail your product photo contains.

This costs foreign-trade suppliers real money. Catalogs go to print looking soft. Buyers get spec sheets they can't read. Someone spends a weekend "upscaling" 800 photos to 300 DPI and achieves precisely nothing. Below are the questions that come up every single time, answered with the arithmetic that settles them.

300 DPI vs 72 DPI: what is that number actually doing?

DPI is a tag stored in the image file that says what physical size the image should default to when placed into a print layout — it does not change the pixels, and screens ignore it entirely.

Every JPEG carries density fields. The JPEG File Interchange Format specification (ITU-T T.871) defines them: a units field plus horizontal and vertical density values. That's it. It's a label riding along with the picture, like a shipping mark on a carton. Changing it re-labels the carton; it doesn't change what's inside.

Strictly, the number belongs to two different words that get used interchangeably:

Your image file has PPI. Your printer has DPI. The industry says "DPI" for both, and that's fine in conversation — just know that when a printer asks for "300 DPI files," they're asking about your PPI, and what they actually mean is: send enough pixels.

Here's the one line worth remembering: a photo's quality is its pixel count, and DPI is just the note attached telling print software how big to place it.

"So why did my printer reject the files?"

Because the printer wasn't wrong — they were using shorthand for a real problem.

Physical print size, pixels, and PPI are locked together by one formula:

printed inches = pixel width ÷ PPI

When your printer opens a 1000 × 1000 pixel photo tagged at 72 DPI, their layout software drops it onto the page at 1000 ÷ 72 = 13.9 inches wide. At that size, on paper, it looks terrible — because you're spreading 1000 pixels across nearly 14 inches. The DPI tag caused it to be placed huge. The softness came from not having enough pixels for 14 inches of paper.

Retag the same file to 300 DPI and it lands at 1000 ÷ 300 = 3.3 inches. Same pixels, sharp at that size. Nothing improved — you just told the software to place it at a sane size.

That's why the retag "worked," and why it's also a trap. If your photo genuinely doesn't have enough pixels for the size you're printing, retagging hides nothing and fixes nothing. Retagging changes where the picture lands on the page. It never adds detail.

The trap in the other direction is worse: resampling. Some tools, when you change DPI, will invent pixels to keep the physical size the same. Now the file is bigger, the numbers look right, and the image is mush. If you're changing DPI, make sure resampling is off.

"How many pixels do I actually need?"

Decide the printed size first, then multiply. That's the whole method.

pixels needed = printed inches × 300

That last row matters and almost nobody says it out loud: 300 is not a law of physics. It's a convention for material held at reading distance. A booth banner seen from two metres away doesn't need 300 PPI, and demanding it will send you hunting for photos you don't need. Offset printing is specified by screen ruling, not by your file's PPI tag — ISO 12647-2:2013 covers the screening and tone parameters for offset lithography, and the familiar "300" is a rule of thumb of roughly twice a 150 lines-per-inch screen. Useful default, not a written requirement. Ask your printer what they actually need at your actual size.

For a sense of how a serious institution words this: the US federal government's own FADGI Technical Guidelines for Digitizing Cultural Heritage Materials (3rd Edition, 2023) defines resolution as "sampling frequency" — the physical pixel count in pixels per inch of the original — and sets conformance tiers per material category. For paper-scale originals (unbound documents, bound volumes, newspapers, oversize maps and posters), the 1- to 4-star thresholds land at ≥190, ≥242.5, ≥294 and ≥396 ppi — that is, 200/250/300/400 ppi minus a reproduction-scale tolerance. Small originals like film run far higher, into the thousands of ppi, precisely because those pixels are being counted across a tiny physical original.

Which is the whole lesson in one place: a ppi number means nothing until you say "per inch of what." Pixels across a known physical size is a real measurement. A number in a header is not.

"Do marketplaces care about DPI?"

No. Not one of them. They care about pixels, and they say so in pixels.

Google Merchant Center's image requirements are a clean example — every constraint is dimensional or file-based, and DPI appears nowhere:

Read the whole spec and you will not find the letters D-P-I. Same story across the marketplaces — the numbers that get your listing rejected are pixel counts, file weight, and framing. This is exactly why the DPI folklore that circulates in vendor forums deserves a hard look before you act on it; when we went through the Home Depot product image requirements, the widely-repeated DPI figure turned out not to appear in the official vendor documentation at all.

So the rule splits cleanly:

• Screens (marketplaces, your website, a buyer's phone): pixel dimensions decide everything. DPI does nothing.
• Paper (catalogs, spec sheets, booth graphics): pixels ÷ PPI decides physical size. DPI decides placement.

"One photo set for print and web — what size do I shoot?"

Shoot for the biggest destination once, then export down. Downscaling is free and looks great; upscaling is a lie.

• Capture master: the largest your camera gives you, kept as the untouched original.
• Print master: sized for your largest printed use — for a full A4 page, about 2500 × 3500 px, tagged 300 PPI so it drops in correctly.
• Web/marketplace export: 1500–2000 px on the long side covers essentially every platform minimum with room to spare.

Suppliers building a printed book for a show hit this hardest, because the same SKU photo has to survive a full-bleed page and a 500-pixel listing thumbnail. The sequencing in the product catalog for the Canton Fair playbook applies here: settle your largest print size before the shoot, not after the printer emails you.

"What about the dimension labels on my spec diagrams?"

This is where the DPI confusion stops being academic and starts costing orders, because text and arrows behave differently from photographs.

A slightly soft photo of a cabinet still reads as a cabinet. A slightly soft "1200 mm" stops being a number. Buyers don't squint at an ambiguous dimension and ask a clarifying question — a good share of them just move to the supplier whose drawing they can read.

Two failure modes, both avoidable:

1. Print: you sized your labels to look right on a 27-inch monitor, then the diagram printed at 3 inches wide in the catalog and the dimension text became a grey smudge.
2. Screen: you built the diagram for the printed page, then a buyer opened it on a phone and the labels are three pixels tall.

The fix isn't a better camera and it isn't a bigger DPI number. It's producing the spec diagram from the measured geometry rather than from hand-drawn arrows on a flattened JPEG — snap the dimension to the product's real edge so the label is anchored to the actual measurement, then export the same diagram twice: once at print pixel dimensions, once at the platform's pixel spec. Tools built for dimension and spec annotation keep the label attached to the geometry instead of baking it into pixels, which is why re-exporting at another size stays sharp instead of forcing you to redraw. It's also the difference that matters against AI image generators: those restyle a photo or invent a plausible-looking number, but they can't hold your product's actual measured size — and a confidently wrong "1200 mm" on a spec sheet is worse than no number at all. What that looks like on a live listing is visible in this wall cabinet size-label case study.

Quick-reference summary

The entire 300 DPI vs 72 DPI question collapses into seven answers:

FAQ

Does 72 DPI mean my product image is low quality?

No. DPI says nothing about image quality. A 4000 × 3000 pixel photo tagged 72 DPI has exactly the same detail as the identical file tagged 300 DPI. Quality lives in the pixel count and the photography. Check the pixel dimensions and ignore the tag.

Will changing my images from 72 DPI to 300 DPI make them print better?

Only in the sense that it makes print software place them at a smaller, correct physical size. It adds no detail. If your tool resamples while changing DPI, it invents pixels and the result is softer than the original. Turn resampling off, and judge the file by pixels ÷ intended print width.

How many pixels do I need for a printed product catalog?

Multiply the printed size in inches by 300. A 5 × 7 inch product shot needs about 1500 × 2100 pixels; a full-bleed A4 page needs roughly 2500 × 3500. Large-format graphics viewed from a distance need far less — a trade-show banner is fine at around 100 PPI.

Does Amazon or Google Shopping require 300 DPI images?

No. Google Merchant Center specifies a 500 × 500 px minimum, recommends around 1500 × 1500 px, caps images at 64 megapixels and 16 MB, and requires the product to fill 75–90% of the frame. All pixel and file rules — DPI is not part of the spec. Marketplace requirements are written in pixels because screens only understand pixels.

What's the difference between DPI and PPI for product photos?

PPI (pixels per inch) describes how many image pixels fall in an inch of printed output; DPI (dots per inch) describes ink dots a printer physically deposits. Your image file carries PPI; the press has DPI. Everyone says "DPI" for both. When a printer asks for 300 DPI files, they mean: give me enough pixels for the size I'm printing.

Sources & References

• ITU-T Recommendation T.871: JPEG File Interchange Format (JFIF) — defines the JFIF density units and X/Y density fields that carry an image's DPI/PPI tag
• Google Merchant Center Help: image link [image_link] requirements — minimum 500 × 500 px, recommended ~1500 × 1500 px, 64 MP / 16 MB caps, 75–90% product framing, overlay and watermark prohibitions
• FADGI Technical Guidelines for Digitizing Cultural Heritage Materials, 3rd Edition (2023) — defines resolution as sampling frequency in pixels per inch of the original and sets 1- to 4-star conformance tiers per material category (≥190 / ≥242.5 / ≥294 / ≥396 ppi for paper-scale categories such as unbound documents, bound volumes and newspapers)
• ISO 12647-2:2013 — Graphic technology: process control for offset lithographic processes — specifies screening and tone-value parameters for four-colour offset printing