Runs on your device
Compress an image to 100 KB.
One of the tightest limits still in common use. Crop first, let the tool find the quality that fits — all of it inside this tab.
Quality is searched automatically. If quality alone can't get under the limit, dimensions step down too.
1 image · drop more here
or drop them here · JPG, PNG and WebP
- Original
- —
- Compressed
- —
- Saved
- —
Compression settings
What must it fit under?
Limits & output
Leave empty to keep the original dimensions. Aspect ratio is always preserved.
JPEG has no transparency — transparent areas are filled with white.
Choosing a format
- JPEG
- The safest choice for photographs, and the one most forms and older software expect. No transparency — transparent areas become white.
- WebP
- The sensible default for the web. Roughly 25–35% smaller than JPEG at matching perceived quality, and it keeps transparency.
- PNG
- Lossless. Keep it for flat graphics, screenshots with text, and anything that must stay pixel-exact. Avoid it for photographs, where it is often larger than the original camera file.
AVIF is smaller still, but it is slow to encode and not yet universal, so it is not offered here. The guide below goes into more detail.
Results
Compressing to 100 KB
What 100 KB actually buys you
100 KB is a hard squeeze. A photograph off a modern phone starts life somewhere between 2 and 6 MB, so landing under this ceiling means giving up upwards of 95% of the file. The tool spends encoder quality first and only starts removing pixels when quality alone cannot get there — at 100 KB it almost always ends up doing both.
Expect a photograph to come back around 900 to 1,200 pixels on its long edge. That is still crisp on a phone, and perfectly respectable as a profile picture or a form attachment, but it is no longer a file you would print or crop into afterwards. Keep your original somewhere.
Flat images fare much better. A screenshot, a logo, a diagram, a scanned form with large type — anything built from broad areas of one colour — frequently survives at full resolution under 100 KB, simply because there is less detail to encode in the first place.
Crop before you compress
At this ceiling, framing beats every setting. 100 KB spread across a wide scene of sky and pavement leaves very little for whatever you actually care about. The same 100 KB spent on a tightly cropped face, or on the text of a document, is a visibly better picture. Crop first, compress second — it is the largest single lever available to you here.
Format is the second lever, and at this size it is close to decisive. WebP typically lands 25 to 35% smaller than JPEG at matching perceived quality, which at 100 KB is the margin between a clean image and a visibly blocky one. Choose JPEG only when the system you are uploading to insists on it.
Limits this tight usually come from somewhere old: government portals written a long time ago, forum avatars, upload widgets whose cap was chosen when broadband was new. They rarely explain themselves, so the practical approach is to hit the number and move on.
Other limits, same tool: 200 KB, 500 KB, 1 MB. Or read the full guide to formats, quality and file size.
Frequently asked questions
Can a photo really look acceptable under 100 KB?
Yes, with one caveat: it has to be the right photo. A tightly framed portrait or a document holds up well, because the detail that matters occupies most of the frame. A wide landscape full of foliage does not — fine, high-contrast texture is exactly what a lossy encoder has to throw away first. Crop to the subject and 100 KB goes a long way further.
What resolution am I left with at 100 KB?
Usually 900 to 1,200 pixels on the long edge for a photograph, though it depends entirely on the picture. Flat graphics and screenshots often keep their original dimensions. Every result reports the dimensions and the quality it settled on, so you never have to guess what was traded away.
JPEG or WebP for a 100 KB limit?
WebP, unless something forces your hand. The 25 to 35% it saves over JPEG is worth more at 100 KB than at any larger size, because it is spent entirely on detail you would otherwise lose. Keep JPEG when the destination explicitly asks for .jpg, which older portals often do.
The upload still says my file is too big. Why?
Almost always a units mismatch. This tool treats 100 KB as 102,400 bytes, the binary convention your operating system also uses. Some upload forms mean exactly 100,000 bytes instead. If yours is rejecting a file that looks like it fits, set the target to 95 KB and try again — the couple of kilobytes cost you nothing visible.
My screenshot is already under 100 KB. Should I still run it through?
No. There is nothing to gain and a little to lose, since re-encoding an image that already fits only discards detail. Compression is worth doing once, from the original file. If it already fits, upload it as it is.