Resize Image to 50KB, 100KB or 200KB

50KB vs 100KB vs 200KB — which target do you actually need?

The size you pick should come from the portal, not from habit. 50KB is the bureaucratic floor; 100KB is the web tier; 200KB is comfortable for anything that isn't strict. Compressing harder than required just throws away sharpness, so read the limit and pick the loosest target that clears it.

When a portal states a range (e.g. '20KB–50KB' or 'up to 200KB'), aim for the top — validators often reject suspiciously tiny files as likely-corrupt.

Why portals reject your photo — and what the KB number really means

A modern phone camera saves photos at 3–8MB. A 50KB limit is roughly 1% of that, so "compress a little harder" was never going to work — the file has to shrink in dimensions, not just quality. File size is driven by three things: pixel count (width × height), format, and compression quality. Halving both dimensions cuts the pixel count by 75%, which does far more for file size than dropping JPEG quality from 90 to 60 — and it looks far better too, because upload forms display photos small anyway.

That's the approach this tool takes at every target: it works out the largest dimensions that can fit inside your chosen budget at a quality that still looks clean, resizes with proper resampling, then fine-tunes JPEG quality to land under the cap. You don't pick numbers; you pick the target. A 200KB budget simply keeps more pixels than a 50KB one.

What actually fits at each size

Approximate JPEG sizes for photographic content. Use this to sanity-check what dimensions to expect — and why a 4000px image can't stay 4000px at any of these targets:

Sizes vary with image detail — a busy background compresses worse than a plain one. Figures are for JPEG; PNG photos are 5–10× larger and rarely fit small targets.

Typical upload limits on application portals

The tight caps exist because government and exam portals were built for slow connections and tiny storage budgets — and their specs rarely change. Common patterns, spanning all three targets:

Always check your portal's current specification — limits and required dimensions vary by agency and change between application cycles.

WebP: the same budget, visibly better

At an identical file size, WebP holds roughly 25–35% more detail than JPEG for photos — a 100KB WebP looks like a 130KB JPEG. If your destination accepts it (your own website, modern CMSs, most chat apps), switch the output format and keep the extra quality for free, especially at the tighter 50KB and 100KB targets where every kilobyte counts. If the destination is conservative — government portals, older job boards, several of which explicitly reject WebP — stay with JPG. The format decision guide explains when each one wins.

Hit your target without ending up blurry

• Crop dead space first. If the form wants a headshot, crop to the face before compressing — wasted background pixels cost kilobytes that should be spent on the subject, and this matters most at 50KB.
• Match the portal's required dimensions exactly (e.g. 413×531). Bigger isn't better: the portal shrinks it anyway, and you'll have spent your budget on pixels nobody sees.
• Photos belong in JPEG (or WebP). PNG only wins for line art and signatures with few colours — see the image format guide, or convert PNG to JPG first.
• Compress from the original, not from a screenshot of it — each extra JPEG generation adds loss. Going original → 50KB once looks visibly better than original → 200KB → 50KB.
• If the result looks soft at 50KB, step up to 100KB if the portal allows it before you blame the encoder — often the target was simply too tight for the detail in the shot.

Signatures and documents play by different rules

A signature is dark ink on white paper — very few colours, lots of flat area. Scanned at 300×100 to 600×200 pixels it compresses to well under the typical 10–20KB signature cap without any visible damage. Shoot it in even lighting, crop tight to the ink, and let the tool do the rest.

If your portal wants a document under a size cap rather than a photo, you're usually better served by the PDF path: compress the PDF to 100KB, 200KB or 500KB directly instead of squeezing a photographed page through an image compressor.

ID photos shouldn't pass through someone else's server

The photos people resize to these sizes are passport photos, ID scans, and KYC documents — exactly the material you don't want sitting in a stranger's upload bucket. This tool runs entirely in your browser: the image is read locally, resized locally, and saved locally. Disconnect from the internet after the page loads and it keeps working. Re-encoding also drops the photo's EXIF block (including GPS coordinates); to verify or strip metadata explicitly, run it through the EXIF remover.