Reduce photo size without losing quality — the right order of steps

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

This applies across documents and exams — pick yours and we will set the exact size automatically.

Crop first, then resize to the required pixel dimensions, then compress last. Doing these steps out of order — especially compressing before resizing — is the most common reason "reducing file size" also blurs the photo.

The order that actually works

1. Crop first

Crop to the required ratio and framing before touching resolution or file size. Cropping after resizing means you're throwing away pixels you've already spent quality on.

2. Resize to exact pixel dimensions

Resize to the exact width and height the portal asks for — not larger "to be safe." A larger-than-needed file just means more data has to be thrown away in the next step, which increases blur for the same target KB.

3. Compress last, and only as much as needed

Compression (JPEG quality) is what actually reduces file size once the dimensions are already correct. Compressing more than necessary to hit a lower KB target is what visibly blurs a photo.

Why doing it backwards fails

Some people compress a large photo heavily first (to get the file size down), then resize it smaller. This double-loses quality: heavy compression at large size creates blocky artifacts, and shrinking a blocky image doesn't remove the blockiness — it just makes it smaller and still visible on close inspection, which is why the exported file still "looks bad" despite technically being small enough.

Getting under a very tight KB limit (like 20 KB)

Very tight limits — common for signatures, or NSDL's PAN photo spec — need the crop step to matter most. A smaller, tightly cropped image compresses to a lower file size at the same visual quality than a loosely cropped one with a lot of empty background.

Fix it

Upload above and pick your document or exam. The crop, resize and compression steps run in the correct order automatically, and the compliance checklist shows whether the result actually meets the KB range before you download.