Passport Photo File Size Limits by Portal

Every figure on this page was read off the issuing authority's own page on 2026-08-14.Each row links to the source it came from. Where an authority does not publish a figure we say so instead of estimating one.

Getting the pixel dimensions right is the part everyone knows about. The part that actually blocks submissions is the file size: almost every government upload form also caps how many kilobytes it will accept, those caps were set for the form's own plumbing rather than for image quality, and a modern phone photo overshoots them by a factor of ten or more. Worse, the forms rarely tell you which rule you broke — you get a generic failure, and the natural response is to shrink the picture, which breaks the pixel rule instead. This page lists what each major portal allows, explains why the numbers are so small, and shows the order of operations that satisfies both constraints at once.

The short answer

Most passport and visa portals want a JPEG somewhere between a few tens of kilobytes and a few hundred. The US visa form is the tightest of the ones below and the one most people meet first; the UK is the outlier in the other direction, and is the only one here where a phone photo will usually pass untouched. Every figure in the table links to the page it was read from.

Why the caps are so small

A few hundred kilobytes sounds like a limit from another era, and in a sense it is — but it is not a judgement about how good the photo needs to be. These caps size the form, not the picture. An immigration system accepts millions of applications from every kind of connection in the world, stores each photo for decades, and replicates it between systems that were not designed together. A small, predictable ceiling per file is what makes that tractable.

The reassuring part is that the ceiling is not actually restrictive at the dimensions these portals ask for. A passport photo is a small, evenly-lit image of one face against a plain background — close to the easiest thing a JPEG encoder will ever be given. At the pixel sizes in the table above, a good-quality export lands comfortably inside most of these caps without any visible loss. The reason your file is too big is almost never the crop. It is that a phone camera wrote a 12-megapixel image with full sensor metadata, and nothing has yet thrown away the parts the portal does not need.

What actually happens when you go over

Nobody looks at it. The size check runs in the form, before your application reaches a queue, and the failure comes back as a validation error rather than as a decision. That is genuinely good news — an oversized file is not a black mark, it is a form that would not submit — but it does mean the message you get is written by the upload widget rather than by a person, and it is usually unhelpful.

The common failure modes are worth naming, because the error text often does not distinguish between them:

• Too large. The most common one, and the easiest to fix without touching the crop.
• Too small. Less well known and genuinely surprising. Some portals set a floor as well as a ceiling, so a file compressed too aggressively is rejected for the opposite reason. If you have been compressing harder and harder and it still fails, this is why.
• Wrong dimensions. Fixed by resizing, not by compressing — and shrinking the pixels to fix a size error is exactly how people land here.
• Wrong format. Every portal in the table wants JPEG. A phone that saves HEIC, or a file renamed from .png to .jpg without being re-encoded, fails before any other check runs.
• Not square, when square is required. A rule that trips up anyone reusing a printed 35 × 45 mm photo for a portal that wants a square frame.

That HEIC case deserves a note of its own, because it is now the most common one on iPhones and it does not look like a problem: the file previews normally and the name may even end in .jpg. If your photo came off a recent iPhone, convert it to JPG before anything else.

Resizing and compressing are not the same operation

This is the distinction the whole page turns on, and it is why so many people bounce between tools. Resizing changes how many pixels the image has. Compressing changes how many bytes those pixels are stored in. The portal checks both, separately, with different rules — and only one of them is allowed to move.

The pixel dimensions are fixed by the specification. The byte count is yours to spend. So the operation you want is: set the dimensions exactly, then reduce quality until the file fits, and never the other way round. Shrinking a correctly-sized photo to save kilobytes trades a rule you must satisfy for one you already had room on.

Order matters for a second reason too. Compressing first and resizing afterwards wastes the effort — the resize re-encodes the image anyway, from data you have already degraded, so you pay the quality cost twice and end up with an unpredictable final size. Crop and resize first. Compress last. Check the number once, at the end.

A worked example: iPhone photo to a US visa upload

This is the most common route, and each step has a number you can check against your own file. A standard 12-megapixel iPhone photo is 4032 × 3024 pixels and lands somewhere around 2–4 MB as a HEIC, or rather more as a JPEG — call it an order of magnitude over the DS-160 cap before anything has been done to it.

1. Convert, if it is a HEIC. Nothing downstream works until the file is a real JPEG. The pixel dimensions do not change; the size usually goes up, which is fine and temporary.
2. Crop to square. The US form requires equal height and width, so a 4032 × 3024 photo has to lose a strip off the sides — it cannot be squashed. This is the step that decides where the head sits, and it is the one worth spending time on.
3. Resize to the target. Take it to the smallest size the portal accepts — 600 × 600 – 1200 × 1200 px is the accepted range, and the bottom of it leaves the most byte budget per pixel. Dropping from 12 megapixels to that does the overwhelming majority of the size reduction on its own, before any quality is traded away.
4. Compress to the cap. Now set the byte target and let quality bisection find the highest quality that fits. At these dimensions a passport photo has plenty of headroom, so the result generally sits at a quality level you cannot distinguish from the original by eye.
5. Check both numbers once. Dimensions square and inside the accepted range, file under the cap, extension .jpg. Then upload.

Two details about that last step. Resizo reads 1 KB as 1 000 bytes, not 1 024, and aims just under the figure you type — upload forms disagree about which they mean, and the decimal reading is the only one that clears both. And the compressor only shrinks the pixel dimensions if quality alone cannot reach the target, which for a passport photo essentially never happens; the frame the portal expects stays intact.

If your portal is not in the table

Most are not, and the list above is deliberately short: it covers only the portals whose own pages we could open and read. The approach that works for the rest is the same one that produced this table.

• Find the figure on the form itself, not in a search result. Upload widgets usually state their limits in the help text beside the file picker, and that text is the rule that will actually be enforced.
• Check for a floor as well as a ceiling. It is the constraint people forget, and the one that makes further compression counterproductive.
• Note the format and whether square is required, before you crop rather than after.
• Treat any figure you find on a photo-tool site — including a wrong one on this one — as a hint to verify, not as the specification.

That last point is why one row in the table above is deliberately blank rather than filled with the number that circulates everywhere else. We could not open a government page stating it, so we do not state it either. An applicant who trusts a plausible-looking figure and has their form rejected is worse off than one who was told to go and look.

Frequently Asked Questions

In short

The pixel dimensions are a constraint you have to match exactly, and the file size is a budget you should spend nearly all of. Set the frame first, compress second, and check both numbers once at the end rather than guessing which one the form objected to.

And when a portal does not publish its limit, read it off the form rather than off a search result. The cost of a wrong number here is not a bad-looking photo — it is a rejected application and another appointment.