How to compress an image to 100 KB
100 KB is a comfortable size for most images: enough for a clear photo on any screen, small enough for strict upload forms and quick-loading listings. This guide covers how to get there, how JPG and WebP compare at this size, and how photos, screenshots and scans behave.
- Add your images by dropping them on the page, pressing Choose files, or pasting from the clipboard. A whole set of listing or report photos can go in at once.
- Confirm the target reads 100 KB. You can type a different number at any time, in KB or MB.
- Pick the format. JPG is the safe choice for forms. WebP usually looks better at the same size and keeps transparency, if the destination accepts it. PNG suits screenshots and graphics with flat colour.
- Use Edit on any file that needs cropping, rotating or flipping before it is compressed.
- Press Compress. Each file card shows the new size, how much smaller it is, and the quality and scale used.
- Compare before and after, then download single files or press Download ZIP for the batch.
Worked example: one photo, two formats
Start with a 4.2 MB phone photo of 4032 × 3024 pixels. These results are typical rather than guaranteed; a detailed landscape needs more bytes than a close-up on a plain background.
As a JPG, the photo is too large for 100 KB even at the lowest quality the compressor allows at full size, so it is scaled down. A usual outcome is around 1,300 × 975 pixels at a quality near 50 percent, saved as a file of about 98 KB. That is wider than most web layouts display an image, so on screen it looks sharp.
As a WebP, the same 100 KB generally buys a little more: either a higher quality at a similar size, or more pixels at a similar quality. The compressor makes that choice for you by searching both quality and dimensions. If the site accepts WebP, try both and compare them with the slider.
A 1920 × 1080 screenshot behaves differently. It has fewer pixels and large flat areas, so it often fits 100 KB at its full size and only quality is reduced. Small text may show faint halos at that quality; PNG avoids them if the screenshot is mostly flat colour.
What happens at 100 KB, by starting image
| Starting image | Usual result | Notes |
|---|---|---|
| 12 MP phone photo, 4032 × 3024 | Scaled to about 1,250–1,400 px wide | Quality around half; looks clean at normal viewing size. |
| 2 MP photo, 1920 × 1080 | Full size or close to it | Quality is lowered first; dimensions change only if needed. |
| Product shot on white, 1200 × 1200 | Full size at high quality | Plain backgrounds use very few bytes. |
| App or web screenshot, 1920 × 1080 | Usually full size | Text edges soften slightly; PNG may be cleaner. |
| A4 page scanned at 300 dpi, 2480 × 3508 | Scaled to about 1,100–1,300 px wide | Body text usually stays readable; tiny print may not. |
The pattern is simple: the compressor protects quality until it would drop below about 45 percent, and only then gives up pixels. A file that starts small keeps its size; a file that starts at 12 megapixels gives up most of its pixels, because no screen or form needs them at 100 KB.
When a form allows more than 100 KB
Some limits are wider than 100 KB. In our specification list, UPSC accepts 20–300 KB and NEET and JEE Main accept 10–200 KB. A 100 KB file sits safely inside those windows, well clear of both the minimum and the maximum, which is useful if you are unsure how a portal counts kilobytes.
If the image has a lot of fine detail, though, there is no need to stop at 100 KB when the form allows more. Type the larger limit, or a few KB under it, and the compressor will use the extra room to keep more pixels.
Fixing common problems
- The file is soft when zoomed in. That is expected for a 12 MP photo at 100 KB; it has been scaled down. Crop to the subject first so fewer pixels are thrown away.
- A scanned page is hard to read. Crop off margins and anything the recipient does not need. For a black and white page, compare JPG with PNG; on some scans PNG keeps letters crisper.
- Transparency was lost. JPG fills transparent pixels with the background colour, white by default. WebP and PNG keep the alpha channel.
- The photo came from an iPhone as HEIC. It is decoded in your browser and saved in the format you picked. Large batches of HEIC take longer to decode than JPGs.
- The result is the same as the original. A file already under 100 KB in the chosen format is passed through untouched apart from metadata removal. Change the format or the target to re-encode it.
- The compressor reports it could not reach the target. This is rare at 100 KB and usually means a very large PNG output. Switch to JPG or WebP.
- WebP fails in your browser. Some older browsers cannot encode WebP; use JPG or update the browser.
Local compression versus upload sites
Compressing a set of 40 listing photos on an upload-based service means sending perhaps 150 MB to a server first and downloading the results afterwards. Done here, the same photos are processed by your own device, so the time depends on its speed rather than on your upload bandwidth, and none of the files leave it.
Upload services have one real advantage: a slow device does not slow them down. If you are on an old phone, a big batch will take longer here. The free plan takes up to 50 files of up to 200 MB each per batch. Pro raises that to 500 files and 1 GB, and the installed app works offline.