PAN Card Photo Rejected? The NSDL-Specific Reasons

Spec pending verification against the official source — confirm on the official portal before you submit.

PAN card photo rejected reasons cluster around operator mismatch — NSDL expects 213×213 px at 200 DPI; UTIITSL expects 640×640 px at 600 DPI — and submitting the wrong square is the fastest failure path.

Key takeaways

NSDL and UTIITSL publish different square specs; pan card photo rejected reasons on NSDL uploads often mean UTIITSL-sized file attached or vice versa.
DPI metadata rejections happen when pixels look correct but embedded tag reads 72 or missing.
KB over ceiling fails after dimension pass — compress without shrinking pixels.
Background off-white, shadow halos, and HEIC format trigger generic rejection messages.
Passport rectangular exports fail PAN upload even when visually acceptable — square re-crop required.
Measure saved file properties before retry; pan card photo rejected reasons map cleanly when width, height, DPI, and KB are logged.

Generic error text — "photo does not meet requirements" — hides specific pan card photo rejected reasons until you measure the export. This article routes NSDL-specific failures first, then UTIITSL contrasts, then cross-operator mistakes.

Visa specs like how to us visa photo 2x2 are irrelevant to PAN square uploads — do not crop PAN from visa presets.

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.

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.

Start here: identify your operator and measure the file

Before editing, confirm portal branding (NSDL Protean vs UTIITSL) and read width, height, DPI, format, and KB from file Properties on disk.

What you measured	Operator	Interpretation	Next step
640×640 px, 600 DPI	NSDL	Wrong operator spec	Cause 1
213×213 px, 200 DPI	UTIITSL	Wrong operator spec	Cause 1
Correct px/DPI for operator	Either	KB or background	Cause 2
630×810 px rectangle	Either	Passport file on PAN form	Cause 1 — re-crop square
PNG or HEIC	Either	Format gate	Convert JPG baseline
Properties blank / absurd	Either	Corrupt export	Re-export from source

The pan card photo rejected reasons you see should correlate with a row after measurement — guessing by thumbnail wastes application time.

Cause 1: Wrong operator pixel and DPI spec

NSDL (Protean eGov) targets 213×213 pixels with 200 DPI embedded metadata. UTIITSL targets 640×640 pixels with 600 DPI. These are not approximations of one spec — they are different validators on different portals.

Submitting 640×640 to NSDL fails dimension check immediately. Submitting 213×213 to UTIITSL fails equally fast. Upscaling NSDL size to UTIITSL size without fresh capture blurs detail — rebuild from high-resolution source.

DPI-only mismatch: file shows 213×213 but DPI reads 72 — NSDL may reject despite correct pixels. Set DPI at export, not in a separate metadata-only pass that some tools skip.

Passport 630×810 rectangles fail both operators — square crop centred on face required. Glasses rules overlap passport guidance — passport photo glasses india for glare avoidance when keeping spectacles on PAN photo.

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

Official notification PDFs lag live portal validators — measure the file you attach, not the screenshot from last cycle.

Spec stability in print does not mean validator stability online; KB ceilings move more often than millimetre dimensions.

Operator	Pixels	DPI	Shape
NSDL	213×213	200	Square
UTIITSL	640×640	600	Square
Passport (wrong here)	630×810	300	Rectangle

Cause 2: KB, background, or format after dimensions match

When pixels and DPI match operator spec, pan card photo rejected reasons shift to file size, background colour, compression blur, or wrong format.

KB too large: reduce JPEG quality in small steps — do not change pixel count. KB too small or quality error: slightly raise quality after confirming dimensions still exact.

Background: off-white walls, corner shadows, halos from bad cutout — re-run white background pass and inspect at 100% zoom on all four corners.

Format: PNG transparency and HEIC from iPhones fail upload parsers. Export baseline JPG. Multiple re-saves on same JPG stack artifacts — restart from camera original if blur persists.

Parallel passport troubleshooting patterns apply to rectangular uploads — passport photo rejected passport seva (29) — but PAN square exports need operator table from Cause 1, not passport pixel pair.

Symptom	Likely cause	Fix
File too large	KB ceiling	Compress; keep pixels
Invalid image / generic	HEIC/PNG	JPG export
Quality too low	Over-compression	Raise quality slightly
Background error	Tint/shadow	White background pass

NSDL-specific rejection patterns

NSDL's small 213×213 canvas magnifies compression mistakes — facial blur after aggressive KB reduction triggers manual review failures even when upload widget accepted file.

Grayscale-compatible colour mode appears on some NSDL flows — verify live portal help if colour export fails repeatedly at correct dimensions.

UTIITSL-specific rejection patterns

UTIITSL 640×640 at 600 DPI produces larger files — KB ceiling hits before NSDL-sized exports do. Tune compression after pixel+DPI lock.

600 DPI tag missing while pixels correct is the signature UTIITSL automated failure — set at export in advanced save dialog.

Operator identification before you fix anything

Read URL domain, portal logo, and application receipt footer. City does not determine operator — both serve nationally. Wrong-operator fix always means rebuild, not tweak.

Retry workflow after pan card photo rejected reasons identified

Log measured width, height, DPI, KB, format. 2. Match operator row. 3. Re-export once from source master. 4. Rename file. 5. Retry upload in fresh browser profile. 6. Capture exact error text if still failing and compare to live portal help.

Common mistakes that repeat rejection

Fixing UTIITSL file while on NSDL portal. Operator first.
Shrinking pixels to fix KB. Moves off spec.
Trusting generic "PAN photo" preset. Preset may pick wrong operator.
Re-uploading identical bytes. Rename and re-export.
Using passport photo file directly. Wrong shape entirely.

FAQ

What are the main pan card photo rejected reasons on NSDL? Wrong pixel size (not 213×213), wrong DPI (not 200), KB over limit, off-white background, or non-JPG format.

Why UTIITSL rejected my 213×213 photo? UTIITSL requires 640×640 at 600 DPI — NSDL-sized file fails UTIITSL validator.

Can passport photo work for PAN after rejection? Not without square re-crop at operator-specific pixels and DPI from original source.

Does DPI matter if pixels look fine on screen? Yes — many validators read embedded DPI metadata independent of display preview.

Why generic error with no details? Portals often hide specific gate — measure file properties to infer cause row from Start here table.

How to fix KB rejection without new photo? Reduce JPEG quality in steps holding pixel dimensions fixed for your operator row.

Will glasses cause PAN rejection? Usually allowed without glare — same practical rule as passport; remove tinted lenses.

Can I switch operator after photo rejection? Operator follows application channel — switching operators means new application path, not resizing same form.

How many retry attempts before support? After two measured re-exports fail, screenshot error and compare live portal help text to logged properties.

Does pan card photo rejected reasons differ for minors? Same photograph upload rules for minor PAN — framing and operator specs identical to adult applications.

Fix it now

Processed on your device. Your photo is never uploaded.

Upload a photo

Upload a photo to see the compliance checklist.

India Passport (ICAO 2026) specs are sourced from official notifications and may change. Always confirm against your portal before submitting. PhotoFix does not guarantee acceptance — we build to published requirements.

Confirm NSDL vs UTIITSL, export square at 213×213/200 DPI or 640×640/600 DPI, measure KB and background on disk, then upload renamed JPG.

Pan card photo rejected reasons become actionable once operator and measurement row match. Do not resize passport rectangles — square crop from source, one clean export, verify Properties before retry.