Image DPI Explained: What It Is and When It Actually Matters

The print shop says the file is "only 72 DPI" and won't run the job. The visa portal rejects a photograph for not being 300 DPI. So you open the image, type 300 into the resolution box, save, and resend — and either nothing changes, or the file balloons to four times the size, or it gets rejected again for a different reason.

Image DPI explained in one line: it is a printing instruction attached to your file, not a measure of how much detail the file contains. Almost every problem people have with the number comes from that one misunderstanding. Once you can see which situations read the instruction and which ignore it completely, the fix for each rejection becomes obvious.

What the DPI Number Actually Is

Two terms get used interchangeably and shouldn't be.

PPI (pixels per inch) describes a digital file: how many of its pixels you intend to fit into each inch of printed width. DPI (dots per inch) describes a printer: how many ink dots the hardware lays down per inch of paper. An inkjet advertising 1200 × 4800 dpi is telling you about its own nozzles, not making a demand of your file.

In practice, print shops, portals and every dialog box in every editor say "DPI" when they mean PPI. Correcting them is a losing battle; just translate as you read.

The part that matters is this. Your image holds a fixed number of pixels — say 1800 × 1200. That count is the only real information in it. The DPI value lives somewhere else: a metadata field in the JFIF or Exif header of a JPEG, the optional pHYs chunk of a PNG. It is a note to whatever software prints the file, telling it how tightly to pack those pixels.

Same 1800 × 1200 file, tagged as	Prints at	Pixels in the file	Detail
72 DPI	25 × 16.7 inches	1800 × 1200	unchanged
150 DPI	12 × 8 inches	1800 × 1200	unchanged
300 DPI	6 × 4 inches	1800 × 1200	unchanged
600 DPI	3 × 2 inches	1800 × 1200	unchanged

Nothing in the image changed across those four rows. Only the intended physical size did.

Why "72 DPI for the Web" Stopped Being True

Browsers do not read the tag. Under the CSS spec one image pixel maps to one CSS pixel by default, and the image-resolution property that could override it isn't supported by any shipping browser. A 1200-pixel-wide JPEG tagged 72 DPI and the identical file tagged 300 DPI render at exactly the same size, and weigh within a few bytes of each other on disk.

So for anything that will only ever be looked at on a screen — site images, social posts, email, app assets — the DPI field is inert. Export whatever it happens to be set to. What decides how your image looks online is the pixel width and, on high-density displays, whether you exported at roughly twice the CSS size. Our image resizer changes that in the browser, on your machine.

The Four Cases Where DPI Genuinely Decides Something

1. Print. The tag sets the physical size, and the pixel count sets whether that size holds up. 300 PPI is the conventional benchmark for anything held in the hand, because at normal reading distance the eye stops resolving individual dots. It is not a universal law — see the viewing-distance note below.
2. Scanning. Here PPI is a real capture setting, not a label: it controls how much of the original you record. The US federal digitisation guidelines recommend 400 PPI for grayscale scans of text — especially originals that are faded, stained or low-contrast — and 300 to 600 PPI for bitonal capture, with 600 preferred for archival masters. OCR engines are broadly tuned for 300 PPI and gain little above 400 on clean text.
3. Upload portals that validate the metadata. Some government systems parse the DPI field and reject anything that reads below their threshold, even when the pixel dimensions are perfectly adequate. The US State Department, for instance, asks for a digital passport photo of at least 600 × 600 pixels at 300 DPI, up to 1200 × 1200 — 600 pixels square is exactly 2 × 2 inches at that density, so the two requirements are the same requirement stated twice. India's Passport Seva portal is the same idea at different numbers: 35 × 45 mm at 300 DPI works out to 413 × 531 pixels.
4. Page-layout software. Word, InDesign, LaTeX and their relatives size a placed image using its DPI tag. Drop in a photo tagged 72 DPI and it lands enormous; the same file tagged 300 arrives at a quarter of the width. This is why a document can look fine on screen and print with an image spilling off the page.

Working Back From the Print Size

The arithmetic is one line: pixels needed = print size in inches × target PPI.

Print size	At 300 PPI	At 150 PPI
4 × 6 in (photo)	1200 × 1800	600 × 900
5 × 7 in	1500 × 2100	750 × 1050
8 × 10 in	2400 × 3000	1200 × 1500
A4 (8.27 × 11.69 in)	2480 × 3508	1240 × 1754
A3 (11.69 × 16.54 in)	3508 × 4961	1754 × 2480
A2 poster (16.5 × 23.4 in)	4960 × 7016	2480 × 3508

Run it in reverse to find the biggest honest print from a file you already have. A 12-megapixel phone photo at 4000 × 3000 pixels divides down to 13 × 10 inches at 300 PPI — a genuine A4 print with room to crop.

Treat 300 as a default rather than a rule, because the real variable is viewing distance. A poster read from two metres holds up at 150 PPI, and a trade-show banner seen from across a hall at 100 or below. Insisting on 300 PPI for a six-foot banner produces a file nobody can open for a difference nobody can see.

Changing DPI Without Wrecking the Image

Every editor's resize dialog performs two different jobs, and the resample checkbox decides which one you get.

• Resampling off — you are editing the metadata only. Pixel count is untouched, file size stays put, quality is exactly as it was. This is what you want when a portal or printer demands a particular DPI reading and your dimensions are already correct.
• Resampling on — you are adding or removing pixels. Going from 72 to 300 with resampling on means roughly 94% of the pixels in the result were interpolated rather than captured. The file gets much bigger and slightly softer.

For the common portal case — an ID photo that must be 35 × 45 mm at 300 DPI — the order that works is:

1. Crop to the required aspect ratio first, using the crop tool with the head placement the portal specifies. Cropping after resizing throws away resolution you just paid for.
2. Resize to the exact pixel target, in this case 413 × 531. Hit the pixels and the DPI reading follows arithmetically.
3. Set the DPI tag to 300 with resampling off, so the field reads what the validator wants.
4. Check the file-size ceiling last. Most portals cap the upload — Passport Seva wants JPEGs under 1 MB — and that is a compression question, not a resolution one.

Our compressor handles step 4, and the 20KB, 50KB and 100KB guide walks through hitting a specific limit without visibly degrading a face. Country-by-country ID dimensions are collected in the passport photo size guide. All of it runs in your browser rather than on a server — your ID photograph and its metadata never leave your device, which is the default our parent company NoCubical builds every tool to.

When DPI Is the Wrong Thing to Fix

• The rejection mentions file size, not resolution. Compress instead. Changing the DPI tag moves the file size by a few bytes.
• The rejection mentions dimensions. Crop and resize to the stated pixel values. The DPI reading will then take care of itself.
• The print came out soft despite a 300 DPI tag. You don't have enough pixels. A 600 × 400 image tagged 300 DPI prints 2 × 1.3 inches beautifully and A4 terribly, and no tag edit changes that.
• It's for a screen. Nothing on the web reads the field. Spend the effort on pixel width instead.
• You scanned at 1200 PPI "to be safe." For plain text that quadruples the file size, slows the OCR down and gains no accuracy over 400. Reserve high settings for photographs.

The short version worth remembering: pixels are the substance, DPI is the label. Get the pixel count right for the physical size you need, then set the label to whatever the receiving system is asking for. Doing it in that order means you almost never have to think about the number again.

Frequently Asked Questions