Compress image to 100 KB

Set the budget, and the encoder is searched for the best quality that fits under 100 KB. On your device — the image is never uploaded.

  • 0 uploads
  • No limits
  • No signup
  • Works offline

Where a 100 KB limit comes from

Nobody chooses 100 KB for fun. If you are here, a form told you to, and the form probably did not explain how. These are the places this particular number turns up:

  • Document scans attached to online forms
  • Product images on marketplace listings with a size cap
  • Photo fields on tax and licensing portals

At 100 KB a 1200-pixel-wide photograph holds up well on screen. Scanned text stays sharp enough to read comfortably.

What 100 KB actually buys you

One hundred kilobytes is where the exercise stops being about faces and starts being about documents. It is the common cap for a scanned page attached to a form, and a scan behaves differently from a photograph: it is mostly white, with high-contrast text that JPEG handles badly at exactly the settings that flatter skin tones.

If your 100 KB file is a scan and the text looks fuzzy, the fix is usually greyscale rather than harder compression. Dropping two colour channels removes a large share of the bytes at no cost to legibility, which leaves the quality setting free to stay high enough that the letterforms hold their edges.

Rarely a compromise. Most images survive this intact. The search here spends the budget on dimensions before quality — a larger image at quality 55 beats a smaller one at 95, because the eye forgives artefacts more readily than missing resolution.

Getting a better result

Three things reliably help when the budget is tight:

  • Crop before compressing. Every pixel you keep costs bytes. A tightly framed portrait at 100 KB looks far better than a full-body shot squeezed into the same space. The cropper hands its result straight to this tool.
  • Start from the highest-quality original you have. Compressing an image that has already been through WhatsApp compounds the damage. Go back to the file straight off the camera.
  • Prefer WebP if the form allows it. At the same file size WebP holds noticeably more detail than JPEG. Most official forms still want JPG, but it costs nothing to check.

Other common targets

10 KB · 20 KB · 30 KB · 50 KB · 150 KB · 200 KB · 300 KB · 500 KB

How it works

  1. 01Add your imageDrop it on the page, click to browse, or paste from the clipboard.
  2. 02The 100 KB target is already setYou landed on this page, so the budget is filled in. Change it if you need something different.
  3. 03The search runsThe encoder is run repeatedly, binary-searching quality for the best result that still fits under 100 KB.
  4. 04Compare, then downloadDrag the before/after slider to see what the compression cost before you commit.

Questions people actually ask

My scanned document looks blurry at 100 KB but my photo looks fine. Why?
Photographs are texture, which lossy compression is built for. Text is hard edges at small scale, which is the case it handles worst — the artefacts land exactly on the letterforms. Convert the scan to greyscale before compressing, keep the resolution above about 200 dpi, and the same budget goes much further.
Will my photo still look acceptable at 100 KB?
At 100 KB a 1200-pixel-wide photograph holds up well on screen. Scanned text stays sharp enough to read comfortably. Rarely a compromise. Most images survive this intact.
Is the result exactly 100 KB?
It lands within about 5% below 100 KB, and never above it. Going over would defeat the point — a form that says "maximum 100 KB" rejects a file of 101 KB without explanation.
Is my image uploaded to reach 100 KB?
No. Every encode in the search runs on your own device, in a background thread, using WebAssembly builds of MozJPEG and libwebp.