The form is filled in, the documents are ready, and then the portal rejects your photo: "file size must not exceed 100KB". Your phone saved it at 2.4MB — roughly twenty-five times too big. The fix takes about a minute with the free Image Compressor: open it, set a quality level, and read the resulting file size until it lands under the cap.

This guide walks through the exact method — which quality to start at, how far to step down, and what to do when quality alone is not enough. Every step runs in your browser on the Image Compressor page, so the photo is never uploaded anywhere.

Why online forms reject your photo

Admission portals, job applications, exam registrations and visa systems all cap upload sizes because they store millions of files. A typical set of limits looks like this: signatures capped at 20KB (20,480 bytes), passport photos at 50KB (51,200 bytes), general uploads at 100KB (102,400 bytes), and supporting documents at 200KB (204,800 bytes). The numbers differ by portal, but the pattern is the same — the cap is always far below what a modern phone camera produces.

A phone photo at 2.4MB is 2,516,582 bytes. To fit a 100KB cap of 102,400 bytes, it must shrink to about 4% of its original size — a 24.58-fold reduction. That sounds drastic, but JPEG compression is designed for exactly this: it discards fine detail your eye barely notices, and at document-photo sizes the result still looks perfectly acceptable on screen and in print.

Note that portals measure in binary kilobytes, where 1KB is 1,024 bytes — not 1,000. A file your computer calls "100KB" might read as 102,400 bytes, and a portal checking strictly against 102,400 bytes will reject anything even slightly over. Always aim a little under the cap, not exactly at it.

Phone cameras are the reason this mismatch exists. A 12-megapixel sensor captures twelve million pixels, and even efficient JPEG encoding needs a few megabytes to store that much detail at high quality. Portals, meanwhile, were designed when a scanned document at 200KB was generous. Neither side is wrong; they simply optimise for different things — your phone for quality, the portal for storage. Compression is the bridge between them, and because JPEG was built for photographs, the bridge is a short one.

The method: start at 80% and step down

Open the compressor and choose your photo. The quality slider starts at 80% by default, which is the right starting point for almost every form: it visibly preserves quality while cutting most phone photos to a fraction of their size. Run the compression once and read the resulting file size, which the tool shows next to the download button.

If the result is still over your cap, move the slider down one or two notches — the slider moves in 5% steps, from 100% down to 10% — and run it again. Each run re-encodes from your original photo, not from the previous compressed version, so stepping down never stacks quality loss on quality loss. Repeat until the size reads under your portal's limit, then download.

Two practical notes. First, the tool accepts images up to 25MB (26,214,400 bytes), which covers any phone photo; anything larger needs resizing first. Second, do not chase the smallest possible file — stop at the first setting that gets you under the cap, because every step down trades away a little sharpness you cannot get back.

When you download the result, give the file a clear name before uploading. Some portals reject files with unusual characters or very long names — a different error from the size limit, and an easy one to confuse with it. Keep the name short, in plain Latin letters, and keep whatever extension the tool gives you.

Worked example: a 2.4MB phone photo under 100KB

Take a typical phone photo: 2,516,582 bytes (2.4MB), and a portal cap of 100KB (102,400 bytes). The walkthrough below shows the quality-step descent. The starting size and the cap are exact; the intermediate sizes are illustrative estimates, because the real numbers depend on how detailed the photo is — a plain sky compresses far better than a crowded street.

At 80% quality, a photo like this typically lands around 380KB — still well over the cap, but already an 85% reduction. Drop to 65%: roughly 150KB, closer but not there. Drop to 50%: roughly 90KB, under the 102,400-byte cap with a small safety margin. Three runs, each under ten seconds, and the file is ready to upload. If your photo is busier than average you might need 45%; if it is simpler, 65% could be enough — the size readout after each run tells you exactly where you stand.

Aim to land 5–10% under the cap rather than right at it. A result of 95KB against a 100KB limit leaves room for the portal's own byte-counting quirks.

When quality alone isn't enough: shrink it first

Some photos resist compression: screenshots, graphics with sharp edges, and very high-resolution images can stay stubbornly large even at 40% quality. When the slider stops helping, shrink the image dimensions before compressing. Halving the width and height quarters the pixel count, which usually does more for file size than any quality setting.

Use the Image Resizer to bring a 4000-pixel-wide photo down to 1200–1600 pixels wide — plenty for any online form — then run the smaller file through the compressor. You will find the quality slider suddenly effective again, often landing under the cap at 70–80% quality with visibly better results than a full-size image crushed to 30%. The image tools category keeps the resizer, compressor and related utilities together.

JPG vs PNG vs WebP at small sizes

Format matters as much as quality. The compressor keeps PNG files as PNG and converts everything else to JPEG — and that distinction decides whether your file can ever get small. PNG is lossless: it preserves every pixel perfectly, which makes it the wrong choice for shrinking photos. A photographic PNG will fight you all the way down the quality slider and may never reach 100KB.

For photos, JPEG is the right format at small sizes: its lossy compression is tuned for exactly this job, and virtually every portal accepts it. WebP produces even smaller files than JPEG at the same visual quality, but many government and exam portals still accept only JPG or PNG uploads, so check the portal's accepted formats before converting. If your source is a PNG photo, convert it to JPEG first — then compress.

If a portal accepts only PNG — rare, but it happens with older systems — the quality slider will barely move the needle, because PNG has no quality setting to lower in the same way. Your lever then is dimensions: resize the image down aggressively with the resizer first. A 1200-pixel-wide PNG photo is dramatically smaller than a 4000-pixel one, and for an on-screen form nobody can tell the difference.

Mistakes that make it worse

  • Re-compressing an already-compressed file over and over. Each pass throws away more detail; always work from the original photo, which is what the tool does on every run.
  • Saving a photographic image as PNG and expecting it to shrink. PNG is lossless — for photos it stays large no matter the quality setting.
  • Cropping out required content to hit the size cap. Portals reject photos missing the required head size, margins or background; shrink dimensions instead of cutting content.
  • Screenshotting a photo instead of using the original file. Screenshots add their own compression artefacts before you even start, giving you a worse result at every size.

Your photo never leaves your device

Compression here happens entirely in your browser: the tool draws your photo onto a canvas element and re-encodes it locally, then hands you the result as a download. Nothing is uploaded to any server at any point — there is no queue, no processing delay, and no copy of your ID photo sitting on someone else's machine. That is the same property explained in Which Online Tools Upload Your Files — and Which Never Do: if a tool never sends your file anywhere, there is nothing to leak, sell or breach.

This matters most for the exact documents forms ask for — ID photos, signatures, certificates. An upload-based compressor would hold a copy of your identity documents on its servers; an on-device one cannot, because the file never leaves the tab you opened.

Photo rejected again? Open the Image Compressor, start at 80%, and step the slider down until the size reads under your cap. Most forms are sorted in under a minute.

Frequently asked questions

What quality setting gets a 2.4MB photo under a 100KB cap?

Start at the default 80% and step down in 5% increments, checking the size readout after each run. A 2,516,582-byte photo typically lands under the exact 102,400-byte cap somewhere between 65% and 45% quality, depending on image detail.

My form says "maximum 50KB" — how small is that, exactly?

50KB is 51,200 bytes. Use the same method: start at 80% quality and step down until the result reads under 51,200 bytes. Leave a small margin rather than aiming for exactly the cap.

Why won't my PNG photo compress below 100KB?

The tool keeps PNG input as PNG, and PNG is a lossless format — it preserves every pixel, so photographic images stay large almost regardless of the quality setting. Convert the photo to JPEG first, then compress; JPEG's lossy encoding is designed for this job.

Can I just keep re-compressing the output to make it smaller?

That is the worst way to do it: every re-compression of an already-compressed file discards more detail and adds artefacts. Each run of the tool re-encodes from your original photo instead, so step the quality slider down on the original rather than compressing the output again.

Is it safe to compress an ID or passport photo in a browser tool?

With this tool, yes: compression runs on a canvas element inside your own browser tab and the file is never uploaded anywhere, so no copy of your identity document reaches any server. Avoid upload-based compressors for identity documents, where your file would sit on someone else's machine.