DPI vs PPI

Why it matters in a DAM

DAM users routinely ask 'what DPI is this file' when the number that actually determines print sharpness is stored as PPI in the image itself — DPI belongs to the output printer, not the file. Ingest validation rules or search filters written around the wrong term (checking a file's 'DPI' field, for instance) can reject print-ready assets or wave through unprintable ones, because DPI isn't a property a static image file even has.

A worked example

PPI Applies to the digital image — pixels per inch of the source file

DPI Applies to the printer/output device — ink dots per inch it lays down

Common print target 300 PPI in the file at final print size, regardless of printer DPI

Common mistake

Writing a DAM validation rule such as 'reject anything under 300 DPI' when the field actually being checked is the file's PPI tag — the two terms aren't interchangeable, and a static image file doesn't have a DPI value at all.

PPI describes pixel density within a digital file: how many of the image’s pixels are packed into one inch when displayed or printed at a given size. DPI describes something physically different — how many individual dots of ink or toner a printer deposits per inch on paper. A file can have any PPI value stored in its metadata (and that value can be changed without touching a single pixel), while DPI is a characteristic of the print device itself, not something a screen or a JPEG file possesses.

The two terms get conflated constantly because both describe ‘sharpness,’ but a DAM that treats them as synonyms will misfire on print-readiness checks. The practical rule most print vendors work to is 300 PPI in the file at the final printed dimensions; below that, detail starts to look soft on close inspection, no matter what DPI the printer itself is capable of.

Frequently asked

What's the difference between PPI and DPI?

PPI (pixels per inch) measures the pixel density of a digital image file; DPI (dots per inch) measures the ink dots a printer physically lays down — they describe different stages of an image's life.

Does a static image file actually have a DPI value?

No. DPI belongs to the output printer, not the file; a static image file doesn't have a DPI value at all, only a PPI value stored in its metadata.

What's the common print-readiness target?

300 PPI in the file at the final printed dimensions, regardless of what DPI the printer itself is capable of.

What's the mistake DAM validation rules often make?

Writing a rule like "reject anything under 300 DPI" when the field actually being checked is the file's PPI tag — using the wrong term can reject print-ready assets or wave through unprintable ones.

Can a file's PPI value be changed without altering the image?

Yes. PPI can be changed in the metadata without touching a single pixel, unlike the underlying pixel dimensions, which are fixed.

Why do PPI and DPI get confused so often?

Both terms describe "sharpness", but they're properties of different things — PPI of the file, DPI of the printer — and treating them as synonyms causes DAM print-readiness checks to misfire.

Why it matters in a DAM

A worked example

Frequently asked

Sources