"200 DPI" Upload Errors, Explained (It's Not About Your Screen)

A wrong dpi 200 dpi error explained in plain terms: the portal read embedded print metadata (often 72 or 96 DPI from web exports) while the notification expects 300 DPI — your monitor settings are irrelevant.

Key takeaways

• DPI in JPG files is metadata describing intended print density, not screen resolution or photo sharpness by itself.
• Wrong dpi 200 dpi error explained messages usually mean DPI tag missing, set to screen default, or set below the published minimum — commonly 300 for Indian passport digital spec.
• Pixel dimensions (630×810) and DPI metadata are independent fields; both may be checked even though pixels alone define on-screen size.
• Fixing DPI does not replace fixing wrong width×height — set both on export from one master.
• Re-saving in tools that strip EXIF can drop DPI back to 72 without changing pixels.
• Verify DPI in file Properties after every export, not in the editor canvas dialog only.

Upload forms mention DPI beside millimetre print size. Applicants raise laptop display scaling or phone "screen DPI" — unrelated. The wrong dpi 200 dpi error explained text refers to the JFIF density tag inside the JPG header.

Use how to best passport photo maker india exports that write 300 DPI alongside 630×810 pixels in one pass.

Government upload validators read pixel width, height, kilobyte size, and format from the file header before any human reviewer sees your face. That mechanical gate means editing workflow order matters as much as capture quality.

Portal help text on the live upload screen overrides generic blog ranges when the two disagree. Read the screen you will actually use before final compression.

Keep an uncompressed cropped master between export attempts so KB fixes do not force full re-crop from the original phone capture.

Transfer exports via cable or cloud with a Properties check at destination — messaging apps re-compress in transit.

Zoom to one hundred percent on all four corners before upload. Thumbnails hide background tint and compression softness.

Indian passport digital upload pairs 630×810 pixels with 300 DPI metadata for 35×45 mm print alignment.

Face height roughly seventy percent of frame height keeps chin and crown inside bands PSK reviewers expect.

Start here: DPI error vs other failures

Read Properties: pixel width×height, DPI or resolution field, KB, format. Match against notification. Route using table — do not change monitor settings.

Cause 1: DPI metadata never set on export

Cause 1 covers exports from web tools, screenshots, and social saves that embed 72 or 96 DPI — historical screen defaults — or omit density entirely so parsers assume 72. Indian passport digital guidance pairs 35×45 mm with 300 DPI in the same bullet as 630×810 pixels.

Some portals flag anything under 300 as "200 DPI error" generically even when the file reads 96 or 144. The wrong dpi 200 dpi error explained label is shorthand for "density tag too low," not literally exactly 200.

Fix: re-export from master with Resolution / DPI field explicitly 300 and resample disabled if pixels already correct — you are writing metadata, not resizing geometry.

Compare tool behaviour in free vs paid passport photo tools — free tiers sometimes strip EXIF on download.

Rename each corrected export before retry when a portal cached a failed filename in the same browser session.

Baseline JPG export avoids alpha-channel surprises that PNG and some WebP files carry into upload parsers.

Each lossy save stacks compression artifacts — work from one master and export fresh copies for every adjustment pass.

Cause 2: DPI stripped or overwritten on second save

Cause 2 is correct first export followed by KB compression or format conversion that strips EXIF/JFIF density. Pixels stay 630×810 while DPI reverts to 72 — upload fails with same error applicants thought they fixed.

Iterative compression must preserve DPI flag on each quality step or re-apply 300 on final file. See jpg quality vs file size tradeoffs for compression order that avoids metadata loss where possible.

Some command-line tools default --strip-all — avoid on final upload copy.

DPI vs pixels vs millimetres

At fixed 630×810 pixels, changing DPI metadata alone changes implied print mm without changing digital pixel grid. Portals want consistent triple: pixel pair, DPI tag, and stated mm.

Math: print width mm ≈ (pixel width / DPI) × 25.4. Wrong DPI tag misaligns mm even when pixels correct — validators enforce consistency.

Why screen DPI does not matter

Monitor scaling, phone display density, and browser zoom do not write into JPG headers. Only export dialogs and save pipelines set JFIF density.

The wrong dpi 200 dpi error explained confusion keeps applicants tweaking display settings while the file on disk stays at 72 DPI from a web resize tool.

Setting 300 DPI without changing pixels

In Photoshop, GIMP, and most passport tools: Image Size → disable resample → set 300 DPI → pixel count unchanged → export JPG. In exiftool: rewrite XResolution/YResolution without touching geometry.

Wrong order — enable resample while changing DPI — accidentally changes pixel count and triggers dimension invalid errors. See 630x810 pixels exact spec for pixel lock discipline.

Portal-specific behaviour

Some gates read DPI only after pixels and KB pass. Others show generic "photo invalid." Always fix pixels first, then DPI, then KB — but verify all three on final attachment.

Common DPI mistakes

Assuming 300 DPI fixes wrong pixels, trusting editor canvas DPI while saved file differs, stripping metadata for privacy then uploading government form, and using "Save for Web" presets that drop EXIF.

Verify after every export

Windows Properties → Details → Horizontal/Vertical resolution. macOS Get Info → More Info. Must read 300×300 dpi or equivalent with pixels still 630×810.

If KB pass requires iterative compression, use iterative compression method from a 300 DPI master export.

FAQ

What does wrong dpi 200 dpi error explained mean? The JPG embedded print density is below portal minimum (usually 300 DPI) or still at screen defaults like 72/96 — not your monitor setting.

Is 200 DPI exactly the problem? Portals often use generic text — any sub-300 tag may trigger the same message.

Do I need to change pixel size to fix DPI? No — set DPI without resampling if pixels already match spec.

Will 300 DPI alone fix dimension errors? No — width and height integers must match notification first.

Why did DPI revert after compression? Some compressors strip EXIF — re-apply 300 on final file or use tool that preserves density.

Does DPI affect on-screen sharpness? Not directly — sharpness comes from pixel content and compression; DPI is print metadata.

Screenshot at 630×810 — DPI ok? Screenshots usually embed 96 DPI — re-export with 300 tag.

Can I use exiftool to fix DPI? Yes — rewrite resolution tags without resampling if pixels already correct.

Passport Seva and exams same DPI? Verify each notification — both often state 300 with pixel pair.

Phone export shows no DPI field? Treat as fail until desktop Properties confirms 300 on upload copy.

Fix it now

Re-export your portrait at 630×810 with resample off, DPI set to 300, baseline JPG, then compress to KB without stripping metadata. A wrong dpi 200 dpi error explained message clears when the saved file Properties show 300 DPI and correct pixels together.