TryImager

Reduce Image to 100KB

100 KB is the single most requested upload limit on the internet. Job boards, visa and exam portals, older content management systems and performance budgets all converge on it. The good news is that it is a comfortable target: most photographs reach it at full resolution with a quality drop you have to look for, which is why this page starts you on quality rather than dimensions.

Processed in your browser

Drop your image here

or choose an image from your device

Accepts JPG, PNG or WEBP · No fixed size limit — we adapt to what your device can handle. Very large files may take longer or show a warning.

Need a different file size?

Reduce Image to 50KBStay under 50 KB, quality and size tuned automaticallyReduce Image to 200KBStay under 200 KB, quality and size tuned automaticallyReduce Image to 500KBStay under 500 KB, quality and size tuned automatically

When you need this

  • A job application or exam portal capped at 100 KB
  • Keeping blog and product photographs light enough not to delay a page
  • Sending several images in one message without tripping an attachment limit
  • Application portals that ask for a photo under 100 KB at a stated pixel size
  • Preparing images for a page that has to stay quick on mobile data
  • Bringing a run of camera photos down before uploading them one at a time

Why 100 KB is easier than it sounds

A typical phone photo is between 2 MB and 6 MB. Reaching 100 KB therefore means shedding 95–98% of the file — a number that sounds impossible and is routine. Most of that weight is not picture information; it is the high-quality JPEG setting your camera app uses to avoid ever being blamed for a bad shot, plus embedded thumbnails and metadata that re-encoding discards entirely.

In practice a 4032×3024 photo usually lands under 100 KB somewhere around quality 0.45–0.6, with visible softening only in fine texture. Portraits, documents and product shots on plain backgrounds do better than landscapes, because grass, gravel and foliage are the hardest things in photography to compress.

Format matters more here than at any other target

At 100 KB the choice of output format changes how much detail survives.

  • JPG: universally accepted. If a form names a format, it names this one. Use it and do not experiment.
  • WEBP: for anything published to the web, WEBP typically reaches the same perceived quality in a noticeably smaller file, so you get more detail inside the same 100 KB.
  • PNG: cannot hit a target size in any honest way. There is no quality dial in a lossless format, so this page writes a lossy output instead when you feed it a PNG.

When to resize instead

If the result looks smeared rather than merely soft, the image has more pixels than 100 KB can describe. Displaying at 1200 px wide but compressing a 4032 px original wastes the entire budget on detail nobody will see. Resize to the width you actually need first, then compress — the quality difference at the same file size is obvious side by side.

The same budget, two very different pictures

Take one 4032×3024 photo and produce two 100 KB files from it. The first keeps the full dimensions and runs the quality down to about 0.5. The second is resized to 1600×1200 first and then compressed, which typically needs only about 0.8 quality to fit. Both files are the same size on disk. Viewed at the width a web page or a form will actually display, the second is clearly cleaner, because its compression is doing far less work.

The only reason to prefer the first is when the destination genuinely uses the full resolution — a print, or a viewer that lets people zoom in.

Choosing a width

If the destination does not tell you, pick the width from how the image will be seen.

  • Full-width on a phone: 800–1000 px is enough, even on a high-density screen.
  • Full-width on a desktop page: 1400–1600 px covers almost every layout.
  • Inside a form or profile field: use the number the form gives, exactly.

Reading the result before you commit

The panel reports the output dimensions alongside the measured byte count, so you can confirm both constraints in one glance. If the size passes but the dimensions came out different from what you typed, the crop mode is the reason — Fit inside preserves the aspect ratio and will leave one side shorter than requested.

How to use it

  1. 1Drop your JPG, PNG or WEBP into the upload area, or tap it to pick a file.
  2. 2Leave the target at 100 KB, or type the exact figure your form specifies.
  3. 3Run it — the encoder steps quality down and stops at the first pass measuring 100,000 bytes or less.
  4. 4Compare Original, Result and Saved, then download the file the panel measured.

Frequently asked questions

Should I choose JPG or WEBP for a 100 KB target?

If a form dictates the format, follow it — that is almost always JPG. If you are publishing to a website and the destination accepts WEBP, choose WEBP: at the same 100 KB it carries more detail, so the picture simply looks better.

Will my photo lose visible quality at 100 KB?

On a portrait, a product shot or a document, rarely at normal viewing size. On a detailed landscape with foliage or water, yes — those are the hardest subjects to compress. Zoom to 100% in the preview before downloading if the detail matters.

Can I compress the same file twice to get smaller?

You can, but do not. Every lossy re-encode discards detail permanently and the second pass gives back far less than the first. Change the target number and run once from the original instead.

Does the tool keep my image's dimensions?

Yes. Compressing here changes encoding quality only; width and height stay exactly as they were. Use the Resize Image tool first if you also need specific pixel dimensions.

Is my image uploaded to a server?

No. The file is decoded and re-encoded by your own browser using the Canvas API. It never leaves the device, there is no account, and closing the tab discards everything.

Do I have to resize, or is compressing enough for 100 KB?

Compressing alone is usually enough to reach 100 KB. Resizing first is about how the result looks rather than whether it fits: the same 100 KB spread over fewer pixels shows far less compression damage.

What width should I choose for a web page?

Around 1400–1600 px covers full-width desktop layouts, and 800–1000 px is plenty for an image only ever seen on a phone. Matching the display width is the single biggest saving available.

Why is my output shorter than the height I typed?

Fit inside preserves the aspect ratio, so the image is scaled until it fits your box and one dimension ends up smaller. Choose Crop to fill if you need the exact width and height and can accept trimming.

Can I do a whole folder at once?

No — the tool handles one image at a time. Because everything runs locally, each file is processed with your device's own memory and there is no queue, so repeating the same settings on several files is quick even though it is manual.

Related guides

Related tools