ZumaTools

Compress image to 100 KB

The web's default upload cap. 100 KB is enough for a detailed photo if you start from the original.

Updated · Published by Novpix LLC

Drop images here

or click to browse · JPG, PNG, WebP · multiple files supported

Images are processed on your device and never uploaded.

Options

Runs entirely in your browser — nothing is uploaded

How it works

  1. 1Drop one or more images into the box above — batches are fine, each file is handled on its own.
  2. 2Each image is re-encoded at progressively adjusted quality until it fits under 100 KB, with dimensions reduced only as a last resort.
  3. 3Download the results. Every one is measured before it is offered, so all of them are at or under the limit.

Frequently asked questions

Why is 100 KB such a common limit?
It is the round number that sits just above what a decent web photograph actually needs, which is why so many systems settled on it independently — visa portals, university admissions, job boards, membership databases. A hundred kilobytes per record keeps a database of a million applicants under a hundred gigabytes, which is the kind of arithmetic that produces a limit.
How much detail fits in 100 KB?
Roughly a 1000 × 1000 pixel photograph at a quality level where compression is not visible at normal viewing distance, or a wider image if the subject is smooth — a portrait against a plain wall costs far less than a crowd scene or a leafy landscape, because compression pays for detail, not for pixels alone.
Can I compress several images to 100 KB at once?
Yes. Drop as many files as you like and each is compressed and measured independently against the target — there are no batch limits or daily quotas, because the work runs on your own device rather than a shared server.
The result is 98 KB, not exactly 100 KB. Is that a problem?
No, and it is deliberate. Encoders cannot be told to produce an exact byte count; the tool searches for the highest quality that still lands under your limit, and stopping a little short is what guarantees the file is never over. Forms enforce a maximum, not a target.
Do you keep a copy of what I compress?
There is nothing to keep. The image is read from your disk into the browser tab, processed there, and written back out as a download. No request carrying your image is ever made, which you can confirm in your browser's network inspector while the tool runs.

About this tool

A hundred kilobytes has become the default ceiling for image uploads on the web, and it is a genuinely sensible one: it is roughly what a good-looking photograph needs at the size a browser actually displays it. Visa applications, university admissions systems, job boards and membership registries converge on the same number because the storage arithmetic behind it is the same everywhere.

Hitting a specific number by hand means exporting, checking the file size, adjusting the quality slider and exporting again — several rounds of it, because the relationship between the quality setting and the resulting size is different for every image. This tool automates exactly that loop. It re-encodes, measures the real encoded size, predicts the adjustment needed, and converges in a handful of passes on the highest quality that still fits.

Two things about the source file decide how good the result looks. Detail is expensive: a portrait against a plain background reaches 100 KB at high quality, while a photograph of foliage or a busy street spends its budget on texture and needs more compression to fit. And prior compression is expensive twice over — artefacts from an earlier save have to be encoded as if they were real detail, so a fresh original always beats a re-saved copy.

Everything runs in your browser, which has practical consequences beyond privacy: there is no upload wait, no file size ceiling imposed by a server, and no daily quota. Drop a batch of application photographs, let each one be measured against the limit, and download them one by one. Your originals are never touched.

Related tools