Resize a Photo to Under 100 KB for a Form
A form wants a photo under 100 KB and keeps rejecting yours. Here's the order of operations that gets there without turning your face into blocks.
To get a photo under 100 KB, reduce the pixel dimensions first and the JPEG quality second — in that order. Bytes scale with the number of pixels, so a 4,000 × 3,000 photo forced under 100 KB by quality alone becomes a blocky mess, while the same photo resized to around 700 × 900 first reaches 100 KB at a quality setting that still looks clean.
On Android, Convertlix's Image Resizer resizes by pixels, percentage or file size on the handset, so the photo never leaves the device — no upload, no server-side copy, nothing to retain. The scope, up front: Android 8.0 or later, sign-in required (there is no guest mode), 25 MB per file and batches of 5 on the free tier against a server-set monthly allowance of conversions shown in the app, and the result lands in Downloads. Everything below applies whichever tool you use.
The arithmetic: what 100 KB is in pixels
This is the number worth memorising, because it turns a frustrating guessing game into one calculation.
A JPEG photograph at a reasonable quality setting lands at roughly 0.15 to 0.35 bytes per pixel. Do the division and 100 KB — 102,400 bytes — works out to somewhere between 300,000 and 700,000 pixels. In practical dimensions:
- 600 × 800 = 480,000 px — comfortably under 100 KB at good quality
- 700 × 900 = 630,000 px — around the sweet spot for a portrait photo
- 827 × 1,063 = 879,000 px — the common "3.5 × 4.5 cm at 600 DPI" spec; tight, needs a lower quality setting
- 1,200 × 1,600 = 1.9 M px — will need aggressive quality reduction and will show it
- 4,000 × 3,000 = 12 M px — not reachable at 100 KB without visible damage
The range is wide because the bytes-per-pixel figure depends on the content, not just the size. Which leads to the tip that saves more people than any setting:
A busy background is expensive. JPEG spends bytes where there is detail, so a photo of you against a plain wall compresses far smaller than the identical photo against a bookshelf, a patterned curtain or foliage. Grain and sensor noise from a dim room cost bytes too, because noise is high-frequency detail from the encoder's point of view. If a form is rejecting your photo, reshooting against a plain light wall in daylight is often worth more than any amount of fiddling with quality.
The levers, in order of effect
| What you change | Typical saving | What you lose |
|---|---|---|
| Halve the pixel dimensions | ~75% | Detail if the form displays it large or prints it |
| Lower JPEG quality 90% → 75% | 40–60% | Almost nothing visible at normal viewing size |
| Lower JPEG quality 75% → 50% | 30–40% | Visible blocking around edges, especially on text |
| Convert PNG → JPG (photos only) | 60–90% | Transparency; and it becomes lossy |
| Crop tighter to the subject | Proportional to pixels removed | Background you may have needed for a specified margin |
| Convert to greyscale | 20–30% | Colour — usually not allowed on ID photos |
| Reshoot on a plain background | 30–60% | Ten minutes |
Order matters because resolution is multiplicative: halving both dimensions removes three quarters of the pixels in one step. Quality reduction comes second because that is where visible damage starts, and cropping is worth trying before either if there is dead space around the subject.
One thing that does not work: saving a JPEG repeatedly at ever-lower quality. Each save re-encodes the artefacts from the previous one, so the damage compounds and never comes back. Always start from the original.
Why the form may reject a photo that is under 100 KB
Byte size is usually only one of several requirements, and the others are invisible in your gallery. Before you assume the compression failed, check:
- A pixel dimension specification. Exam and visa portals very often state both, e.g. "200 × 230 pixels, 20–50 KB". When both are given, the pixel spec wins — resize to exactly those dimensions, then bring the bytes under the ceiling with quality. Some also enforce a byte floor, rejecting files that are too small, which is its own trap: a 6 KB file can fail for being under-detailed.
- The format. Some portals accept JPG only. An iPhone photo is often HEIC, which many forms simply refuse to parse — HEIC to JPG on Android (Free, Offline) covers that conversion, and it has to happen before any of this.
- Progressive JPEG encoding. A handful of older government portals reject progressive JPEGs and accept only baseline. It is rare and undocumented, and it presents as a mystifying "invalid file" error.
- Colour mode. CMYK JPEGs and greyscale files get rejected by validators expecting RGB colour.
- Aspect ratio. If the spec says 3.5 × 4.5 cm, a square crop fails even at the right pixel count.
How to get a photo under 100 KB
- Read the whole specification, not just the size. Write down the byte cap, any pixel dimensions, the accepted format and the aspect ratio. Half the failures on this task are a requirement nobody read.
- Convert the format first if you need to. If the file is HEIC or PNG and the form wants JPG, do that before resizing — the conversion changes the byte size substantially and there is no point tuning a number that is about to move.
- Crop to the required framing. Get the aspect ratio right and cut any dead space around the subject. Pixels you remove here are free savings.
- Resize the pixel dimensions. Hit the specified dimensions exactly if there are any; otherwise aim for the 600 × 800 to 800 × 1,000 range as a starting point. In Convertlix, the Image Resizer takes pixels, a percentage or a target file size.
- Then bring the bytes down with quality, and stop as soon as you're under. There is no prize for 40 KB when the cap is 100 KB, and every step down costs detail permanently.
- Check the number, then look at the face at 100%. Read the file size in Downloads, then zoom in on the eyes and any text. That is what the reviewer looks at.
When this doesn't work
- A byte cap with a high pixel floor. "1,200 × 1,600 pixels, under 50 KB" is close to arithmetically impossible for a photograph and the result will look bad whatever you do. Get the pixel spec right, get as close as you can on bytes, and submit — a portal enforcing both that hard usually has a validator that is more lenient than its instructions.
- Documents rather than photos. Text and line art under a byte cap behave completely differently: JPEG blurs letter edges, and PNG or a bilevel format wins. Compress a PDF Under 500 KB Without Blurry Text covers the same lever-order argument for documents, and Make a PNG Smaller Without Losing Quality covers screenshots and graphics.
- An already-compressed download. A photo pulled off WhatsApp or a website has been re-encoded once already, and squeezing it again looks noticeably worse than compressing the original would have. Find the original if you can.
- Anything to be printed. 100 KB is a screen-sized image. If someone will print it at any size, you need the original and a different conversation with whoever set the cap.
FAQ
What pixel size is 100 KB?
Roughly 300,000 to 700,000 pixels for a photograph, which is about 600 × 800 up to 800 × 900. The range is wide because JPEG spends bytes on detail: the same dimensions will come out much smaller against a plain wall than against a bookshelf. If you need one number to start from, 700 × 900 is a good first attempt for a portrait.
Why does my photo get rejected even though it's under 100 KB?
Almost always another requirement in the same specification. The most common causes are a pixel dimension the form also specifies, a format it won't accept (HEIC from an iPhone is the big one), a wrong aspect ratio, or — occasionally on older government portals — a progressive JPEG where only baseline is accepted. Some forms also set a minimum size and reject files that are too small.
Should I resize or lower the quality?
Resize first, then lower quality, and stop as soon as you are under the cap. Dimensions are multiplicative, so halving width and height removes three quarters of the pixels at no visible cost when the image is displayed small, whereas quality reduction is where blocking and blur start to show. Doing it the other way round is what produces the smeared, blocky results people associate with compression.
Does Convertlix upload my photo?
No. The image is opened through Android's own file picker, resized on the phone and saved back to the device — nothing is sent anywhere, and the app has no storage permission, so it cannot read anything you did not hand it. Its network calls carry identity, licence, quota, configuration and payment data, never a photograph. Sign in once, switch on airplane mode, and it still works.
Is there a free way to do this without an app?
Yes, several good ones. Squoosh is free, runs entirely in your browser and shows
the output size live as you drag the quality slider, which makes hitting an exact
cap genuinely easy — it is the best free tool for this specific job and worth using
if you're at a computer. ImageMagick does it in one command
(magick in.jpg -resize 700x900 -quality 78 out.jpg), and Windows Photos and macOS
Preview both have resize and export built in. As of September 2026 most other
browser-based resizers upload the file to their servers first, which for a passport
photo is a trade worth noticing.
If the form is rejecting your photo and you'd rather not hand your ID picture to a website to find out why, resize it on the phone and read the size in Downloads before you try again.