Why visa portal uploads fail silently — and how to make sure yours don't

The failure nobody warns you about

Most people assume an upload either works or shows an error. On visa portals, there is a third outcome, and it is the one that costs applications: the file quietly does not attach.

The page does not turn red. Nothing says "too large." You move to the next document, finish the session, and log out believing the bundle is complete. Days later the decision comes back as documents not provided — for a document you are certain you uploaded.

This is the single most common avoidable problem in online visa submissions, and it happens because of one mismatch: modern scanners and phones produce files far larger than these portals were built to accept.

The rule that prevents it: after every upload, refresh the page and confirm the file is listed. Do not trust the upload screen. Trust the list.

Why government portals are so strict

Visa portals are not built like consumer file-sharing services. They are long-lived government systems, often a decade or more old, sitting behind conservative infrastructure limits. Their upload caps were set when a typical scanned page was a few hundred kilobytes.

Meanwhile:

• A phone camera photo of a single page: 3–8 MB
• A 600 DPI colour scan of one A4 sheet: 5–10 MB
• A six-month bank statement PDF exported from online banking: 4–15 MB, mostly logos and vector graphics repeated on every page

So the gap is not small. A perfectly ordinary set of documents can be ten to fifty times larger than what the portal will take. The portal did not get stricter — the documents got heavier.

Find your portal's real limit — don't assume one

Published limits circulate widely on the internet and they are frequently wrong, out of date, or copied between blogs. Worse, the same country can enforce different limits at different application centres, because the intake system differs by mission.

Never plan around a number you read in an article — including this one. Find your actual limit this way, in order:

1. Read the upload page itself. Most portals print the limit in small text beside the upload button, or in a tooltip. It is the only number that is definitely current for your session.
2. Check the document checklist PDF issued for your specific visa route and centre. Limits and accepted formats are usually stated there.
3. Test with one file first. Upload your smallest document, refresh, and confirm it attached. You have now proven the mechanism works before you commit the whole bundle.
4. When nothing states a limit, plan for the strictest realistic case. In practice, application-centre portals are tighter than direct government portals, and a target well under any figure you have seen will pass both.

Typical ranges you will meet in practice

These are shapes of requirement, not values to trust for your submission. Verify against your own portal.

The important line in that table is the third one. Over-compression is a real failure mode, not a theoretical one — some portals reject a file that has been squeezed below their floor, and others accept it while the officer cannot read it.

Aim below the limit, not at it

If the limit is 2 MB, do not deliver a 1.99 MB file. Target roughly 85% of the stated cap, for three reasons:

• Encoding overhead. A file's size on disk is not always what the server counts after transfer encoding. A file sitting exactly at the boundary can be measured as over it.
• Timeouts. Larger uploads take longer, and a slow or unstable connection is far more likely to drop near the ceiling. A dropped upload is one of the ways a file silently fails to attach.
• Re-submission. If a caseworker asks for a corrected page later, you want headroom, not a rebuild.

For a 2 MB cap, target 1.7 MB. For 1 MB, target 850 KB.

Where the megabytes actually are

Compression works best when you know what is heavy. In a typical visa bundle:

Scans at 600 DPI. Archival scanning resolution. A visa officer reads the document on a screen; 200–300 DPI is entirely legible and a fraction of the size. This single setting is usually the biggest saving available.

Phone photos of documents. A 12-megapixel camera captures far more detail than a document page contains, plus shadows and background. Photographing on a flat surface in even light produces a smaller and much more readable file than a hurried angled shot.

Bank statements. The text is tiny; the weight is the bank's logo, background shading and header graphics repeated on every page. Where your bank offers it, download the statement as a plain PDF rather than the styled one, and include only the months requested — not twelve months when three were asked for.

Employment letters and booking confirmations. Company letterheads with high-resolution logos, and airline confirmations padded with advertising blocks and marketing imagery. Keep the page that contains the evidence.

Do not pad the bundle. Extra documents nobody asked for are not neutral — they consume the space your actual evidence needs, and on tightly-capped portals they are a common reason real evidence gets squeezed out or skipped.

Compress without making it unreadable

Compression trades detail for size. Past a point, the officer cannot read what you sent — and an illegible document is treated as a missing one.

Two checks before you upload anything:

1. Open the compressed file and zoom to 100%. Read the smallest text on the page — account numbers, dates, the signature line, stamp text. If you struggle, so will the officer.
2. Check every page, not the first one. Compression is applied across the document; a bank statement can look fine on page one and turn to mush on page four.

If a file is unreadable at the size you need, the answer is not more compression. It is a better source: rescan at 300 DPI rather than compressing a 600 DPI scan into the ground, or export a clean PDF from the source system instead of photographing a printout.

There is a full walkthrough of doing that properly — scan settings, what to check, and what to do when a file will not shrink — in how to compress a PDF for a visa application.

A checklist that prevents the silent failure

Run this in order, every time:

1. Find the real limit on the upload page before you start.
2. Set your target at ~85% of it.
3. Compress each file to its own target, not the bundle as a whole — most portals cap per file, not in total.
4. Open each compressed file and read the smallest text on the last page.
5. Upload one file first. Refresh. Confirm it appears in the list.
6. Upload the rest, refreshing after each. Never batch and hope.
7. Before logging out, reload the whole page and count the documents against your checklist.
8. Screenshot the completed list. If a document is later disputed, you have your record.

Step 5 and step 8 are the two most often skipped and the two that save applications.

Doing this for many applicants

For a consultant handling several files a day, the risk is not any single upload — it is that one document in one bundle fails quietly and nobody notices until the decision arrives.

Three habits reduce it to near zero:

• Name files so a gap is visible. CLIENT_Bank-Statement.pdf, CLIENT_Passport.pdf. A missing name in a folder listing is obvious; a missing file in a portal list is not.
• Prepare the full set before opening the portal. Compressing document-by-document inside the session is how limits get missed and pages get skipped.
• Keep the client's originals. Compression is one-way. If a caseworker asks for a clearer copy, you want the original scan, not a recompressed copy of a compressed file.

Where TravelPdfPro fits

TravelPdfPro was built for exactly this step: taking a set of visa documents and fitting each one under its own limit, without the documents leaving your device.

Compression runs entirely in your browser. Passports, bank statements and identity documents are never uploaded to us — there is no server to send them to. For anyone handling other people's documents, that is not a feature, it is the requirement.

Frequently asked questions