You can handle this directly in your browser with our free pdf to images tool — nothing gets uploaded.
Government portals reject more file uploads than many people expect. A scan that looks clean on your screen can still be bounced by an agency's validation layer. The result is the same whether you are applying for a visa, filing taxes, renewing a license, or submitting proof of income: the form returns, the deadline ticks down, and you have to figure out what went wrong.
This post breaks down the technical reasons a scanned PDF gets rejected, shows how to check and fix each issue, and points to a practical workflow you can run entirely in your browser using NoFilePDF, a free local PDF tool that never uploads your documents to a server. No account, no upload, no waiting.
Most official forms do not simply check that a file is named .pdf. They run a chain of validations on the client side, the upload gateway, and sometimes again on the backend after the file lands on disk.
A native PDF is generated by software like a word processor, a browser's print dialog, or a design tool. It carries a text layer built from actual characters, not images. A scanned PDF is produced by a camera or flatbed scanner: every page is a JPEG or CCITT image, often with no text layer at all. Many agencies explicitly require native or machine-generated documents. The rationale is simple: a native PDF can be searched, validated against schemas, and indexed by downstream systems. A scanned PDF is a flat picture that has to pass through OCR before any of that works, and the OCR step is where most rejections happen.
Most portals cap uploads between 2 MB and 10 MB per file, and some cap the total batch size as well. A 200-page scanned bundle can easily hit 40 MB before anyone has opened it. The limit is enforced on the gateway, not the browser, so you will see the failure only after a long upload.
Some systems accept one PDF containing every page of a form; others require one page per file, or one file per applicant. The rule is usually buried in a help page, and the error message will just say file invalid. Reading the portal's upload section carefully before you start saves a round trip.
A PDF that contains real text is searchable. A PDF that is only an image is not, even if the image looks sharp. Portals that auto-index submissions, or that run downstream text extraction, will reject image-only files. The fix is an OCR pass that adds a text layer on top of the existing image, not a re-scan.
The table below maps the typical error message to the underlying cause and the quickest fix.
| Symptom you see | Likely cause | Quickest fix |
|---|---|---|
| File exceeds maximum allowed size | Scan at 300 or 600 dpi, or many pages in one bundle | Compress to 150 dpi and target under 3 MB, or split into smaller files |
| Text layer missing or unreadable | Pure image scan, no OCR | Run OCR to add a searchable text layer; verify with a text search inside the PDF |
| Pages rotated or out of order | Phone scan or manual page capture | Rotate and reorder pages before re-export |
| Blank or partial pages | Duplex scan miss, or phone camera clipping a corner | Rescan the missing pages and merge back into the file |
| Wrong MIME type | Renamed .jpg to .pdf, or exported from a viewer as an image | Re-export as a real PDF from the original source, not by renaming |
| Encrypted or password protected | Source PDF had a security layer | Remove the password with a PDF tool that preserves content |
| Form fields not filled natively | Printed, signed, scanned, then submitted | Re-fill the original interactive form in a PDF editor, sign digitally, export without flattening if the portal supports it |
The pattern you should take away is that most rejections are fixable without rescanning from scratch. You usually already have a usable document; it just needs a targeted correction.
Step one is to read the rejection message word by word. Portals differ, but the message usually names the failing check: size, type, text layer, page count, or format. Do not just resubmit the same file; that will fail the same way.
Step two is to open the file in a browser-based PDF tool and look at the structure. NoFilePDF lets you inspect pages, rotate them, reorder them, extract text, add an OCR text layer, split into individual pages, and compress, all on your local machine. Because the file never leaves the browser, sensitive personal data stays on your device, which matters a lot when the document contains an ID, a passport, or a bank statement.
Step three is to apply the fix that matches the cause. If the issue is size, run compression and aim for 150 dpi for text-heavy documents. If the issue is the missing text layer, run OCR and verify the result by selecting text in the preview and reading it back. If the issue is page count, split the bundle into one file per requirement, named clearly, for example page1.pdf through page3.pdf.
Step four is to re-test before hitting submit. Open the corrected file in a second tab, search for a known string, scroll through every page, and confirm no page is blank. Most rejections you encounter are caught at this stage, not at the gateway.
Different government portals set different caps. The numbers below are typical, not exhaustive, and you should always confirm against the specific portal you are using, because they change without much notice.
Tax filing portals in many countries accept a single document up to 5 MB and a batch total of 25 MB. Visa and consular applications often cap at 10 MB per file and 15 MB total, with a hard requirement for PDF format only, no images and no zips. Social security and benefits sites are usually more permissive, around 20 MB, but still reject encrypted files. Driver license and identity renewals commonly demand a specific page count, for example photo on one page, signature on another, and refuse multi-page bundles entirely.
The practical takeaway is that size limits are not the whole story. Page count, encryption status, and format purity all matter, and the most restrictive rule wins. When in doubt, prepare two versions of the same document, one under 2 MB and one under 10 MB, so you can fall back fast.
Uploading a passport scan to a third-party cloud service feels risky even when the provider is reputable. Government-grade documents carry identity data, financial data, and sometimes medical data. A local processing tool removes the transfer step entirely. The file is parsed, OCR-processed, split, and compressed in the browser using the same engine as the desktop version, then it never leaves your machine.
NoFilePDF is built for exactly this. It runs in the browser, requires no signup, and exposes the operations that government portals actually test for: compression, page rotation, page reordering, page splitting, OCR text layer insertion, password removal, and metadata cleanup. The workflow is short: open the file, run the needed operations in order, save the result, and submit. If something fails at the portal, you are one operation away from a corrected file, not one support ticket away.
It depends on the portal. Many agencies accept an image PDF that has a searchable text layer, because the downstream index reads the text, not the pixels. A small number of portals, usually identity-verification ones, require a native form PDF with filled interactive fields. Read the specific form instructions first, then apply OCR only if the rule says text-searchable rather than native-form.
For text documents, 150 DPI is usually enough to stay under size limits while remaining legible after OCR. For forms with a signature or a stamp, use 200 to 300 DPI on that single page. For passport or ID copies, 300 DPI with color enabled is the safe baseline. Do not exceed 300 DPI unless the portal explicitly asks for it; higher DPI inflates file size with no OCR benefit.
Yes, most portals accept a single multi-page PDF as one logical document. The exceptions are systems that require one page per file, usually for photo uploads or signature pages. If the help page says one file per requirement, split in NoFilePDF, name each page clearly, and attach them in order.
Run the corrected file through a quick pre-check list: under 5 MB, no encryption, every page visible, a known string selectable in the text preview, correct MIME type, no trailing spaces in the file name. If it passes all four checks and still fails, the portal has a hidden rule, usually page count or format purity. Prepare the smallest compliant variant and submit that first, then fall back to the larger version.
A rejected PDF is rarely a dead end. It is a list of failing checks, and each check has a one-step fix. Identify the cause, apply the fix locally, verify, resubmit. NoFilePDF covers the full set of fixes a government portal can ask for, and it does it on your machine, which is the right place for a document that carries your identity.
Related reading: annual review scan reconcile paper records, batch ocr scanned pdfs, car repair records scan before selling.
Why do government systems reject my scanned PDF?
Government portals often reject scanned PDFs because they lack searchable text layers, have low resolution, or contain non-standard metadata. These files may fail automated validation checks. Instead, upload native digital PDFs created from scratch or ensure scans are high-resolution (300 DPI) and OCR-processed to allow text recognition.
What is the difference between a scan and a digital PDF?
A scan is an image file converted to PDF format, containing only visual pixels. A digital PDF is native text-based, allowing selection and search. Government systems prefer digital files for easier processing and verification. Use your browser tool to convert images to searchable PDFs or merge documents to create clean, text-based files before submission.
How can I make my scanned document acceptable?
Run the scan through an Optical Character Recognition (OCR) tool to add a hidden text layer. Ensure the file size is under the portal's limit, often 10 MB. Use compression tools to reduce size without losing legibility. If the portal requires specific formats, convert your document to a standard PDF/A archive format using browser-based conversion utilities.
Can I fix a rejected PDF directly in my browser?
Yes. Use free browser tools to compress large files, merge split pages, or run OCR to add text layers. Check for corrupted data by re-saving the file. If the portal still rejects it, verify that the file is not password-protected, as many government systems cannot process encrypted documents securely during automated intake processes.