PDF Not Opening or Unable to Read QR Details: Fixed

A PDF not opening, unable to read QR details, is one of those errors that sends people looking for a repair tool when the file is usually intact. You downloaded an e-Aadhaar, a DigiLocker certificate, a vehicle registration copy or a marksheet, you pointed a scanner at the square in the corner, and the app told you it could not read the QR details. The instinct is to assume the document is corrupt. In most cases it is not, and running a repair or a compressor at that point makes the situation worse rather than better.

The useful move is to work out which of two very different failures you are looking at, because they have opposite fixes. This guide separates them, then walks six checks in the order that resolves the most cases first.

What the error actually means

Scanning a document QR is a two-stage operation, and the wording of the error tells you which stage broke.

The first stage is decoding. The camera captures the black-and-white grid, and the decoder reconstructs the bytes those squares encode. This stage is purely optical. It cares about resolution, focus, contrast, glare and whether the whole code is in frame. When this stage fails you see wording like “unable to read QR details”, “no QR code found” or a scanner that simply sits there and never locks on.

The second stage is validation. Government-issued QR codes are not plain text. They carry a structured payload signed by the issuing authority, and the reader checks that signature before it shows you anything. When this stage fails, the data came through fine and the signature did not check out. Aadhaar readers report this as “QR Code not verified” rather than a read failure.

That distinction is the whole diagnosis. A read failure is an image quality or wrong-app problem. A verification failure is a provenance problem, which means the file has been altered, regenerated or is no longer the issuer’s original. Chasing an image-quality fix for a verification failure wastes an afternoon.

Cause 1: the reader app cannot decode a signed QR

This is the single most common reason an Aadhaar QR appears unreadable, and it has nothing to do with your PDF. The secure QR code on e-Aadhaar is meant to be read by a UIDAI reader: the official Aadhaar app, the separate Aadhaar QR Scanner app, or the Windows QR code reader UIDAI publishes for desktop use. UIDAI organises this under QR code verification in its FAQ section.

Both apps are verifiable on Google Play rather than taken on trust. The Aadhaar QR Scanner is published under the package name in.net.uidai.qrcodescanner (Play Store listing), and the Aadhaar app UIDAI currently links from its own site is in.gov.uidai.pehchaan (Play Store listing). If a link into UIDAI’s site fails, note that uidai.gov.in has been rebuilt and many older FAQ URLs still circulating in search results now return 404 even though the site itself is up. Start from the FAQ section above rather than from a cached link.

The reason a general-purpose QR app fails is structural. A URL QR code holds a short string that any decoder can hand straight to a browser. The Aadhaar secure QR holds a compressed binary block containing the masked Aadhaar number, name, date of birth, gender, address and photograph, wrapped in a digital signature. A generic reader can often recover those bytes and then has no idea what they are, so it either shows nothing or reports that it cannot read the details. The pixels were fine. The vocabulary was not.

If a verifier at a bank, a telecom counter or an employer tells you your QR does not scan, this is worth raising politely, because the person holding the phone is often using whatever QR app came with it.

Cause 2: you are scanning a copy of a copy

The second cause is the one people create for themselves without noticing. The QR that verifies is the one in the file the issuer generated. Every transformation after that point costs detail, and a dense QR has very little detail to spare.

Each of these is a common way to lose it:

• Screenshotting the PDF instead of saving it. A screenshot captures the code at screen resolution, which is far below the resolution stored in the file.
• Printing and then photographing the printout. Two lossy conversions stacked on each other, plus paper texture, plus whatever your room lighting does to the contrast.
• Print-to-PDF or “save as PDF” from a viewer. This re-renders the page into a new document. Even where the image survives, the issuer’s digital signature does not carry across, so a file that decodes fine can still fail verification.
• Running it through a compressor to satisfy an upload size limit. Covered in detail below, because this is the one people do deliberately and regret.
• Cropping the QR too tightly. QR codes need a clear margin, the quiet zone, to be located at all. Trim it flush and many decoders stop finding the code.

For DigiLocker documents there is an additional wrinkle worth knowing. DigiLocker documents can be verified either by validating the digital signature on the PDF copy or by scanning the QR through the DigiLocker app’s scan facility, and both routes depend on issuer-side signing infrastructure rather than on your copy alone. An old printout that verified when you made it is not guaranteed to verify indefinitely. Re-downloading the current PDF from the DigiLocker app costs a minute and removes the question.

Six checks, in order

Work down this list rather than across it. The order is deliberate: the cheap checks that fix the most cases come first, and nothing here modifies your file until step five.

1. Read the error wording again. If it says the signature or verification failed rather than that it could not read the code, skip straight to step six. You have a provenance problem, not an image problem.
2. Switch to an official reader. For Aadhaar, use the official Aadhaar app or the Aadhaar QR Scanner app. For DigiLocker documents, use the scan facility inside the DigiLocker app. If the code reads now, you are finished and the file was never at fault.
3. Scan from the screen, not from paper. Open the original PDF on a laptop or tablet, zoom until the QR fills a good part of the display, and scan that with the phone. This removes printing, paper and photography from the chain in one move and is the fastest way to prove the code itself is intact.
4. Check you are holding the original download. Look at where the file came from. If it arrived over WhatsApp, was forwarded by email, or you cannot remember saving it from the issuer, download it again from the source. WhatsApp in particular is a common way for a document to arrive already degraded.
5. Pull the QR out at its stored resolution. If you want to see exactly what the code looks like inside the file rather than what your viewer draws on screen, extract the embedded image itself. Extract images from PDF finds the image objects a page paints and pulls each one out at the dimensions stored in the document, so a QR that is sharp in the file comes out sharp rather than at whatever size your screen happened to render it. If the extracted image is visibly coarse or blotchy, the file has already been through a lossy step and no amount of rescanning will help.
6. Go back to the issuer. If the extracted code is damaged, or the reader reports a verification failure, the answer is a fresh original. Download e-Aadhaar again from UIDAI, or re-download the document from DigiLocker. There is no recovery path from a degraded QR, and any tool promising one is guessing.

When the PDF will not open at all

Everything above assumes your viewer can display the document. If it cannot, the QR is not the problem yet and the file structure is the suspect.

PDFs carry a cross-reference table that tells a reader where every object in the file lives. Truncate a download, and that table can end up pointing at the wrong byte offsets while the page content underneath is completely intact. That specific damage is repairable: a tool can scan the file for surviving objects and rebuild the table around them. Repair PDF does exactly that, and reports GREEN, YELLOW or RED for what it could and could not recover.

Be clear about the limit, though. Rebuilding an index only works when the index is the damaged part. If the content streams themselves are corrupted, or the file no longer starts with a PDF header at all, in-browser repair cannot bring it back and the tool says so rather than handing you a file that silently fails later. For that case, a desktop pass with qpdf is the next step, and a fresh download from the issuer is better than both.

Shrinking the file without killing the QR

Plenty of portals cap uploads at 1 MB or 2 MB, and a scanned document with a photograph in it can land well above that. This is where a QR usually dies, so it is worth being precise about what compression does.

There are two different operations sold under the same word. One re-serialises the file structure and squeezes redundancy out of it without touching how the page looks. The other re-renders each page into an image at a chosen resolution and saves that image as JPEG. The second one is where QR codes go to die, because it does both things a QR cannot survive: it drops resolution, and it applies a lossy codec that smears the hard edges between modules.

Our own PDF compressor is explicit about which profile does what, and the numbers are worth reading before you pick one. The Low profile is lossless: it re-serialises the PDF with object-stream compression, keeps text selectable, does not rasterise, and typically saves 5 to 15 percent. The Medium profile re-renders every page at 144 DPI and stores it as JPEG at quality 0.65. The High profile drops that to 96 DPI at quality 0.45.

So on any document whose QR you still need to work, Low is the only profile worth considering. Medium and High are the right tools for a photo-heavy deck you are emailing, and the wrong tools for an identity document.

There is also a step people hit before any of this. An e-Aadhaar downloaded from UIDAI is password-protected, and so are many DigiLocker documents. Our compressor cannot read an encrypted file at all: it stops and points you at Unlock PDF, which removes the password in your browser so the file can be opened by any tool afterwards. Unlock first, then compress. If you are not sure what the password is, our guide on the e-Aadhaar password format covers it.

If Low does not get you under the portal’s limit, upload the original through a different route, or ask whether the portal accepts the DigiLocker share link instead of a file. Both are better outcomes than a 900 KB file with a QR nobody can read.

It is also worth saying plainly: once a QR has been downsampled and JPEG-compressed, it is gone. The modules that carried the data were averaged away, and no sharpening filter or upscaler reconstructs them, because the information is not there to reconstruct. Keep the issuer’s original as the master copy and compress a duplicate if you must compress at all.

Why this runs in your browser

The documents in this guide are identity documents. An e-Aadhaar PDF carries a name, address, date of birth, gender and photograph, and a DigiLocker certificate is no less sensitive. Handing one to an anonymous web converter to shave a few hundred kilobytes off it is a poor trade.

Every tool linked here processes files inside your own browser tab. The PDF is read by JavaScript running on your device, the work happens in local memory, and the result is written back to your downloads folder. Nothing is uploaded, so there is no server copy to leak, subpoena or forget to delete. For a document you are only touching because a portal demanded a smaller file, that is the correct default.