Passport and visa photo limits: what actually gets your upload rejected
You took the photo properly. Lighting is fine, the background is plain, you are not wearing glasses. The form rejects it anyway — or worse, accepts it and rejects the application weeks later. This is one of the most common and least understood failures in the whole process of filling in an official form, and almost always the cause is something the portal measured that you could not see.
The important thing to understand is that these systems are not looking at your photograph. They are reading the file.
Three limits, and confusing them is the actual problem
Nearly every form you will meet asks for three separate things, and they are checked independently:
| Limit | What it measures | How you fix it |
|---|---|---|
| Pixel dimensions | Width × height in pixels, and sometimes the aspect ratio | Resize the image |
| File size | Weight of the file in kilobytes | Compress it |
| Format & colour | JPEG vs PNG vs HEIC, and sRGB vs Display P3 | Convert it |
Resizing and compressing are different operations and people constantly assume the first handles the second. It does not. Halving each dimension cuts the pixel count by four and usually takes about three quarters off the file size — which sounds like it would solve everything, and for a flat document scan it nearly does. But a detailed photograph at the required passport dimensions can still be well over the limit. A 240 KB cap is a byte limit, and bytes are only reduced by encoding.
The trap specific to iPhones
Two iPhone defaults cause most of the failures we hear about. Photos save as HEIC, which most portals do not accept at all, and they use the Display P3 colour profile, which is a different colour space from the sRGB that portal checks expect. A perfectly good photo can fail both ways without ever having looked wrong. The HEIC explanation covers why the format causes this much trouble; the short version is that it is efficient in a way that older upload systems were never built to read.
Real limits, from the official source where one exists
A warning before the table: aggregator sites routinely disagree with each other and sometimes with the official requirement. We checked the US figures directly against the Department of State's published digital image requirements rather than trusting a third-party summary, and we have marked where a number is a commonly-cited figure rather than a verified one. Where the official source is unambiguous, we link it — check it yourself rather than trusting any table, including this one.
| Application | Dimensions | File size cap | Notes |
|---|---|---|---|
| US visa (DS-160) — official | 600×600 to 1200×1200, square | 240 KB | JPEG only, sRGB, 24-bit. Official source: travel.state.gov |
| US visa — printed at interview | 2×2 in (51×51 mm) | — | Same image, different spec from the upload |
| Schengen visa — physical | 35×45 mm → 413×531 px at 300 DPI | No single official cap | Light grey or off-white background; white is rejected at some consulates |
| Schengen — VFS Global upload | 400×514 px minimum | 100 KB | Frequently cited; the window varies by the specific centre |
| UK passport | 35×45 mm → 413×531 px | Varies by submission route | Digital and in-person specs differ |
| Canada passport | 50×70 mm → 600×840 px | 240 KB | Commonly cited figure — verify on the current IRCC page |
Every file-size figure in the last column opens the compressor with that number already entered. Where the table says a cap is only commonly cited, treat the link as a starting point rather than as a promise — the verification still has to happen on the official page.
Notice how inconsistent those caps are: 240 KB for the US, but anywhere from 10 KB to 300 KB depending on which application centre handles a Schengen file. There is no universal limit to learn — you have to read the specific form in front of you. What you can generalise is the technique for hitting whatever number it asks for.
How to hit an exact file size limit
This is the part that actually solves it. Setting a quality slider to 70 and hoping is unreliable — for some images 70 is far too generous, for others it is unnecessarily destructive. What you want is a search: try a quality, measure the resulting file, and adjust until the output lands just under the target. Our compressor does exactly that, running the search for you.
- Get the dimensions right first. Resizing before compressing is much cheaper. There is no point spending compression effort on pixels the portal will discard, and hitting the dimension requirement often gets you under the cap on its own. Use the resizer.
- Convert the format if needed. Most portals want JPEG. If your file is HEIC, or PNG, convert it before targeting a size. The converter handles JPG, PNG and WebP.
- Then target the KB. Open the compressor, switch on the exact-size option, and enter the number the form asks for. It will find the highest quality that still fits under your limit.
- Aim slightly under. If the cap is 240 KB, land near 230 KB. Portals sometimes measure size marginally differently, and a few kilobytes of headroom costs you nothing visually.
A note on very small limits
Below roughly 20–30 KB, quality alone is often not enough, because a face photographed against a plain background still carries enough detail that even very low quality leaves the file above the target. When that happens the tool steps the dimensions down and tries again. This is also why cropping tight before compressing makes such a large difference: a signature on a large sheet of paper contains far more bytes than the signature itself.
PNG will not get you there
PNG is lossless, which means you cannot tune it toward a byte target by degrading quality — you can only make it more or less detailed, and it stays enormous either way. If a form asks for a specific KB number, it wants JPEG or sometimes WebP. Anyone who tells you to compress a photo as PNG and then shrink it is going to send you in circles.
The privacy question nobody asks about this task
This is the one task on the site where "just upload it somewhere" deserves a second thought. A passport photo is not a holiday snapshot — it is a biometric identifier that will sit in a government database, travel with your application, and often appear on every visa you hold for the next decade. And these are precisely the files people end up pasting into whatever free converter they found first.
Any site that processes your file in the browser has no copy of it. There is no upload endpoint, no storage bucket, no retention policy that could apply to you, and no operator who could be compelled to hand it over. If you compress locally, your passport photo does not exist anywhere except your own device — which is also the easiest privacy claim to verify: open the network tab in your browser and watch nothing leave. The full reasoning is in why we built the tools this way.
What this tool does not do
Being clear about the limits of any tool matters more than the feature list. SnapTools does not crop your photo to a passport frame, replace the background, remove shadows, or judge whether your expression complies. Those are judgement calls a photograph has to be made for, not corrected afterwards — and every automated "passport photo maker" that offers them is really a template crop with a compliance claim attached.
It also cannot read HEIC, so if your iPhone photo will not open at all, that is a different problem with a specific cause. What it does handle is the mechanical half of the task: correct dimensions, correct format, and a file that lands under the exact byte limit the form demands, produced without your photo leaving the machine.
Frequently asked questions
Why did the portal reject my photo when it looked fine?
Because the automated check rarely looks at how the photo looks. It reads the file's technical properties: pixel dimensions, byte size, format and colour profile. A photo that is perfectly exposed can still fail on a file that is 3 MB when the limit is 240 KB, or that is in the wrong aspect ratio.
Does resizing my photo to the right pixel size also get it under the KB limit?
No, and this is the most common misconception. Pixels and bytes are independent limits. Halving each dimension cuts the pixel count by four and usually the file size by roughly three quarters, but a detailed image can still exceed the limit at the required dimensions. You need to do both: resize to the specified pixels, then compress to the specified KB.
Can I check these limits without giving my passport photo to a website?
Yes, and you should. Compressing in your browser means the file never leaves your device, so a tool that works locally has no copy of your passport photo at all. That matters more for this task than for most, because the image is a biometric document that follows you through the application process.
What file size should I aim for to be safe?
Aim for just under the stated maximum rather than exactly at it. Upload forms often measure size slightly differently, and a file landing a few kilobytes under the cap removes the risk of an off-by-a-few-KB rejection.
Does compressing to a KB limit make the photo unusable?
For passport and visa sizes, usually not. At the small dimensions these forms require, a face has relatively few pixels, and a face compresses well. The result is visibly softer when zoomed in on a large monitor but fine at the size it will actually be printed and examined.
Related guides & tools
- Compress a JPEG to exactly 100 KB — the single most common limit
- Compress a photo to an exact file size — including 20 KB and 50 KB cases
- Remove metadata from photos — location and camera data travel with the file
- Image sizes for every platform