Compress JPG to 100KB

Detailed guidance

Why 100 KB keeps appearing as a limit

One hundred kilobytes is the quiet default of a hundred systems written over twenty years: application portals, form builders, CMS upload handlers, and email gateways that assume a photo should be light enough to travel fast on hotel wifi. The cap is rarely explained on the page that enforces it, which is why the most common failure looks like a silent reject button rather than an error message. Treat 100 KB as a budget rather than a punishment. You get to decide where the bytes go: fewer pixels and a gentler encoder usually beats one huge image squeezed to breaking point.

A routine that survives strict forms

Start by resizing the photo to the largest dimensions the destination accepts, because pixel count costs more than encoding quality does. A portrait for an application rarely needs more than 600-800 px on the long edge. Then run it through this page with the 100 KB target preset already filled in. Open the result at full size and look specifically at faces, small text, and the horizon line; those reveal over-compression first. If anything looks wrong, go back a step and resize a little more rather than pushing the encoder further. Keep the file named for its purpose before you upload, since some systems bounce generic names and a clear filename helps a human reviewer if the application is queried later.

Reading the result honestly

The card shows the delivered byte count, not an estimate, so you can trust it against a stated limit. If the result lands far below the ceiling — 40 KB where 100 KB was allowed — the photo had little detail to encode, which is normal for flat graphics and screenshots. If it stops above the target, the tool has run out of acceptable settings and the honest fix is fewer pixels rather than a second pass. Repeatedly re-saving a JPG compounds generation loss, so always work from the cleanest source you have instead of compressing an already-compressed export.

Privacy is the quiet advantage

Documents that pass through a web compressor often linger in temporary storage, get logged, or are cached by third-party CDNs on their way back to you. A local canvas never has those failure modes: the file is decoded in memory, redrawn, and exported as a new copy in your downloads folder. That also means no queue and no upload throttle, so thirty forms worth of photos take seconds rather than minutes, and the work still finishes on a bad connection.

When a photo refuses to fit

Some subjects fight a 100 KB ceiling harder than others: a crowded street, foliage, a shot of a television screen, or a photo that carries small text. When the search runs out of acceptable settings, do not rerun it — reduce pixels by roughly a fifth and try once more, because structure costs more bytes than smooth areas do. Two other adjustments work at this weight. Crop out dead space so the encoder spends its budget on the subject, and switch a purely graphic image to PNG when it contains large flat colours, which pack better than JPG ever does. Portraits should keep resolution and accept a softer encode; text images should keep detail and accept more plain area around them.