Compress an image to 100 KB
The 100 KB target is preset: the page keeps the highest JPG quality that fits, prints the real byte count on the card, and never uploads the photo.
Your images
Settings
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
The application form took your resume without complaint and then bounced the headshot: "Image must be 100 KB or smaller." That exact ceiling guards the profile-photo field in most applicant tracking systems, the avatar upload on older forums and intranets, and the photo slot on state benefit, DMV and school-district portals. A phone photo weighs 3 to 5 MB, so it is 30 to 50 times over the line, and the error never says by how much.
This is the 100 KB rung of the compressor: the target of 102,400 bytes is already set and the output is JPG, the one format none of those forms reject. Instead of asking you to guess a quality number, the page encodes the photo up to twelve times, measures the real size after each pass, and keeps the highest quality that still lands under the limit. A headshot or a scanned ID stays readable instead of being crushed to the minimum just to be safe.
Every result card prints the original size, the new size, the percentage saved, the pixel dimensions and a target met tag, so you know the file will pass before you leave the page. If you want the picture to look good rather than merely fit, crop to the face or the document first: fewer pixels sharing the same 100 KB means each one keeps more detail.
How it works
Three steps between a 4 MB camera-roll photo and a file the form will take.
Add the photo or photos
Drag them onto the page, choose them from your camera roll or desktop, or paste with Ctrl+V. JPG, PNG, WebP, iPhone HEIC, GIF, BMP and SVG all open right in the browser, and the files stay on your device.
Leave JPG selected
The settings panel opens with the 100 KB target applied and JPG on the format bar; the quality slider is ignored here because the search picks the number. Switch to WebP only if you need transparency. The width field is not on this page: if the form also caps pixels, run the photo through Resize image before you come here.
Generate, check the card, download
Press Generate images. The card under each photo reports the before and after sizes, the percentage saved, the output width × height and a target met tag; if 100 KB was out of reach it says smallest possible instead. Open Compare to check the face or the small print, then download the file or the whole batch as a .zip.
Where the 100 KB cap shows up
The limit is about storage, not photography: 100 KB stops raw phone photos while leaving room for a sharp 600–1,000 px headshot or a legible scan. It rarely travels alone, though.
- Applicant tracking and HR profile photos: 100–200 KB, JPG or PNG, often a 400 × 400 px minimum.
- Forum, wiki and intranet avatars: 100 KB plus a pixel ceiling, typically 200 × 200 or 500 × 500.
- Benefits, DMV, visa and school portals: 100 KB, JPG only, sometimes an exact frame such as 600 × 600.
- Older internal systems: a limit set years ago and an error that says only "file too large".
Typical results at the 100 KB target
Two stages. First, a binary search on JPG quality from 5 to 96: up to twelve encodes, each measured against 102,400 bytes, keeping the highest quality that fits with the pixels untouched. Only if quality 5 is still over does the image shrink, 15% per step at quality 72, up to ten steps, until one passes.
Results land a few KB under the line, at 94, 97 or 99 KB, never on it; a 100.6 KB file would be refused.
| Source | What happens | Result |
|---|---|---|
| 12 MP phone photo, 4000 × 3000 JPG, 4.2 MB | Shrunk to about 1,000 px wide, quality 72 | ~96 KB |
| iPhone HEIC, 12 MP, 2.1 MB | Decoded on the device, same ladder, saved as JPG | ~97 KB |
| Headshot, 600 × 800 JPG, 180 KB | Pixels untouched, highest quality that fits (often 75–85) | ~90 KB |
| Photographed letter-size page, 3000 × 4000, 2.6 MB | Shrunk to roughly 1,000 px; crop the margins first | ~90 KB |
Under 100 KB and the upload still fails
Bytes are one of four checks, and the error rarely names the one you tripped:
- Pixel dimensions. A maximum, a minimum or an exact frame. Check the width × height tag on the card; if it is wrong, crop on Crop image and set the width on Resize image, then come back.
- Format. iPhone photos arrive as HEIC and most portals list only JPG and PNG. The JPG output here settles HEIC, WebP and BMP alike.
- Decimal versus binary kilobytes. This page targets 102,400 bytes; a few systems count 100 KB as 100,000, so a card reading 99.5 KB (about 101,900 bytes) can still be over their limit.
- Too small after downscaling. If quality alone could not reach 100 KB, the image was shrunk, and a 400 × 400 minimum may refuse it. Crop to the subject first so the surviving pixels are the ones that count.
Crop first if it should look good, not just fit
A hundred kilobytes is a budget, and the bookshelf behind you spends it. Crop a full-body shot to head and shoulders and the quality search finishes near 80 instead of dropping into the downscale ladder; trim the white margin off a scan and the text stays crisp at 1,000 px.
Frequently asked questions
Why did the file come out at 96 KB and not 100 KB?
Because the page controls quality, not bytes: each quality step moves the file by several KB, and it keeps the highest step that lands at or under 102,400 bytes. Landing a few KB short is exactly what keeps the portal from rejecting it.
Does compressing to 100 KB change the pixel size?
Only if quality alone cannot get there. Then the width is cut in 15% steps, at most ten times, until the file fits, and the card shows the final width × height. A 600 × 800 headshot keeps its pixels; a 4000 px phone photo ends up near 1,000 px wide.
The form needs at least 400 × 400 px and under 100 KB. Can I get both?
Yes, as long as the page never has to shrink the image. Crop to a square on Crop image, resize to about 600 × 600 on Resize image, then compress here: a face at that size fits in 100 KB around quality 80, with pixels to spare above the minimum.
The site says 100 KB but refused a file this page marked target met. What happened?
That system counts 100 KB as 100,000 bytes, while this page targets 102,400. Take the file to the general compressor, lower the quality a few points and watch the card; stop as soon as it reads 97 KB or less. Or shave 10% off the width on Resize image and run it here again.
Can I drop in HEIC photos straight from an iPhone?
Yes. On the first HEIC the page fetches a decoder of roughly 1 MB, once, and the photo itself never leaves the phone. It is decoded, run through the same 100 KB search and saved as JPG, which is what the form wanted in the first place.
Can a logo with a transparent background stay transparent under 100 KB?
Not as JPG, which fills transparency with white. Pick WebP on the format bar: it keeps the alpha channel and gets the full quality search. PNG also keeps transparency, but it has no quality setting, so the page can only shrink its dimensions to reach the target.
I'm sending a passport photo and a scanned ID to a government portal. Does this page see them?
No. The decoding and the JPG encoding happen in your browser's canvas; nothing is transmitted and there is no server copy to delete later. The EXIF block, including the GPS position a phone camera writes, is stripped from the output, which is what you want on a file headed to a portal.
Is 100 KB enough for a resume headshot?
Easily. A 600 × 800 head-and-shoulders photo lands under 100 KB at the highest quality that fits, often 80 or above, with no loss you can see on a screen. It only looks rough when a full-body 4,000 px photo is squeezed into the same budget, which is why cropping first pays off.