PAN correction — fixing a misspelled name, an old address, a changed date of birth — runs entirely online now, through Protean (formerly NSDL e-Gov) or UTIITSL. Both ask for scanned proof documents, and both reject an oversized file with the same unhelpful message: upload failed, try again. No indication of how far off you were.
Short version: aim for 300KB per document. That’s the figure Protean’s own PAN Change Request guidelines state for supporting proofs, and it’s the safe number to use for UTIITSL too. Compress PDF has a custom target-size field — type 300 (or 300KB), upload your scanned proof, and it searches for the highest quality that still clears that number, entirely in your browser.
What the portals actually specify
Protean’s official guidelines for the PAN Change Request / Correction form (published at tin.tin.proteantech.in/pan/correctiondsc.html) spell out three separate upload fields, each with its own cap:
| Item | Resolution | Type | Format | Max size |
|---|---|---|---|---|
| Photograph | 200 DPI | Color | JPEG | 20 KB |
| Signature | 200 DPI | Color | JPEG | 10 KB |
| Supporting documents (proof of identity/address/DOB) | 200 DPI | Black & white | PDF/A or JPEG | 300 KB per page |
UTIITSL runs its own correction portal with its own form, and its published figures for photo and signature differ slightly from Protean’s (commonly cited around 30KB for the photo and 60KB for the signature), but the supporting-document limit lands in the same place — around 300KB per document. Check your specific form before submitting, since the two providers update their pages independently.
The 300KB document row is what matters for a PDF compressor — your photo and signature are separate, smaller image uploads that a passport-photo cropping tool handles better than this one will.
Why PAN document uploads get rejected
The scan is a full-resolution photo of a small ID card. A phone camera shot of an Aadhaar card, voter ID, or utility bill at default settings routinely comes out at 2-6MB — the portal wants under a tenth of a megabyte. That’s the single most common cause of rejection, and it’s a resolution problem, not a formatting one.
Color got left in on a black-and-white requirement. Protean’s spec calls for black & white supporting documents — a color scan is heavier for no benefit, since the proof document doesn’t need color to stay legible. If compressing alone still leaves a color scan over 300KB, there’s a fix for that further down.
Multiple proofs got merged into one PDF. Submitting proof of identity and proof of address as one combined file also combines their size — and the form may expect one document per field, not a bundle. A two-sided ID is a related but separate case — some fields want the front and back merged into one file, others want them as two separate uploads — so check what that specific field is asking for rather than assuming either way.
The file quietly grew back up after editing. Opening a PDF to add an annotation and re-saving can re-embed the image at a higher resolution than the original scan.
The compressed copy never got uploaded. You compress the file, then the upload dialog defaults back to your Downloads folder and it’s easy to click the original scan out of habit. Check the file size shown in the picker before you submit — if it’s still megabytes, that’s the untouched original, not the file you just made.
How to hit 300KB with Compress PDF
- Scan or photograph each proof document separately, in decent light — no need for a high-DPI scan on something going to 300KB regardless.
- Open Compress PDF and upload the document.
- Use the custom target-size field and enter 300KB. The tool renders the page, re-encodes it as a JPEG at a quality level it searches for, and checks the result against your target — adjusting quality, and render scale if needed, until it lands under the number or reports honestly that it couldn’t.
- Zoom into the result before uploading. Check the document number, name, and date fields — those get cross-checked against your application, and blur first if a target gets pushed too aggressively.
- Handle the photo and signature as separate image files — this tool compresses PDFs, not passport photos.
If a color scan won’t shrink enough
Compress PDF’s quality search re-encodes every page as a JPEG, but it keeps whatever color your scan already has — it doesn’t strip color out on its own. If a color scan is still landing over 300KB after compression, the color information itself is usually part of what’s costing you bytes: skin tones in a photo ID, a colored seal, the blue of a ballpoint signature all give the JPEG encoder more to spend a byte budget on, even though none of it matters to someone checking a name and a document number.
Grayscale PDF removes the color before any JPEG encoding happens. Run your scan through that first, then feed the grayscale output into Compress PDF’s target-size field — you’re now compressing a lighter file to start with, instead of asking one tool to fight color and size at the same time. Grayscale PDF produces true grayscale — a full range of gray tones, not a 1-bit black-and-white image — which is what most scanning software means by “B&W” too and matches what Protean’s spec is asking for.
This only helps when the source is actually in color. A scan your scanner already saved as grayscale or black-and-white won’t get any smaller from a second pass through it.
Why it matters that nothing gets uploaded
A PAN correction proof is usually a government ID — Aadhaar, voter card, passport, a utility bill with your name and address on it. Running that through a typical web-based compressor means sending the actual file to someone else’s server before you get it back.
Compress PDF doesn’t do that. The rendering and JPEG re-encoding happen inside your browser tab using plain JavaScript — the same kind of in-browser processing covered in Can You Compress a PDF Without Uploading It Anywhere?. Check it yourself: open dev tools, go to the Network tab, clear it, run a compression. There’s no outbound request carrying your file, because the code path that would send one doesn’t exist here. For a document with your ID number on it, that’s different from a promise to delete the file later.
If a document won’t compress under 300KB
This mostly happens with one kind of file: a multi-page proof (a full bank statement, a long affidavit) where every page carries text that needs to stay legible. Squeezing several text-dense pages into a 300KB total pushes quality down fast, because the budget gets divided across pages.
If that’s your situation, upload only the specific page the portal needs rather than the whole document. Why Won’t My PDF Compress Any Smaller? covers the floor compression runs into, and why a text-heavy scan resists shrinking the way a plain photo doesn’t. Already rejected once without a clear reason? PDF Upload Rejected for Wrong File Size covers the other common causes worth ruling out.
Correcting Aadhaar details around the same time? Compress PDF to Under 2MB for Aadhaar Update Documents covers that portal’s considerably looser limit.
Start with the 300KB target in Compress PDF, zoom in on the result, and confirm the current figures on Protean’s correction guidelines page or your UTIITSL form before you submit.