SizeMint guides

Compress image to 100KB, exactly.

A 100KB limit is the most common upload constraint on the web. Here is how to hit it exactly, with quality to spare.

Worth knowing before you start

Start from the destination. A 100KB limit is a concrete constraint, so start with the constraint rather than a generic quality number. Name the target first; let the tool search for the encoding.

Dimensions are half the battle. A modern phone photo is thousands of pixels wide. If the portal displays it at a fraction of that, keeping every source pixel is wasteful — set a sensible maximum width and a higher quality setting becomes possible within the same 100KB.

Pick the format that matches the image. Photographs usually benefit from JPG or WebP; screenshots and graphics may need PNG. If the destination accepts WebP, it stretches 100KB further for photos. See our WebP vs JPG comparison.

When you need exactly 100KB

100KB is the workhorse limit: job portals, university uploads, government document sections, profile systems. It is generous enough that most photos survive with quality intact, but strict enough that an unoptimized 4MB phone photo will fail it mechanically — 101KB fails the same way 10MB does.

Hit 100KB in four steps

1. Upload your image

Open the SizeMint compressor and drop in a JPG, PNG, WebP or AVIF file. Processing happens entirely in your browser — the image is never uploaded anywhere.

2. Enter 100 as the target

Type 100 KB as the target size. The compressor searches encodings automatically to find the best quality that fits under 100KB.

3. Inspect the result honestly

Check faces, text, thin lines and high-contrast edges at the size they will be displayed. A file can meet 100KB while looking worse than necessary if the dimensions or quality were pushed too far.

4. Download and verify

Download the result and confirm the file size in your file manager before uploading it to the form. Keep your original — the 100KB file is a submission copy, not an archive.

What 100KB can and cannot do

At 100KB, most photographs look genuinely good — this is enough budget for a clean, detailed image at sensible dimensions. What 100KB cannot do is preserve a 12-megapixel original at full resolution; but no upload form asking for 100KB wants your full resolution anyway. If the result looks soft, the fix is almost always dimensions first: a 1200-pixel-wide photo at 100KB beats a 4000-pixel-wide photo at 100KB every time.

If the target cannot be reached

Unusual, but possible with extremely detailed images — dense foliage, crowds, fine fabric texture. Reduce the maximum width, try WebP output if the destination accepts it, and judge the result at its real display size. A responsible tool reports when a target cannot be reached instead of silently handing back an oversized file.

Questions, answered

Is 100KB enough for a clear photo?

Yes. At sensible display dimensions, 100KB holds a clean, detailed photograph. This is the most forgiving of the common upload limits.

JPG or WebP for 100KB?

Use whichever the destination accepts. WebP usually looks slightly better at the same size; JPG is the safer choice for older portals. Our format comparison walks through the trade-offs.

My file is 102KB — will the form accept it?

Usually not — byte counts are checked mechanically. Target slightly under, around 98–99KB, so measurement differences do not push you over.

Should I resize before compressing?

If the source is much larger than the display size, yes. Removing pixels the destination cannot show is the single biggest quality win at any fixed byte budget.

Use the compressor

Ready? Open the SizeMint compressor, enter 100KB, and download your file.