Compress an Image to an Exact File Size

Set a target, drop in an image, and the tool hunts for the highest quality that still fits under it. It does not apply a fixed quality setting. It encodes at quality 100 first, and if that already fits, the image comes back untouched — a file that was small to begin with loses nothing. When quality 100 is too large, a binary search runs through up to nine encodes, halving the search range each time, until it finds the best setting that stays at or under your number. The result card reports the original size, the compressed size, and the quality actually used.

1. 1Drop or select a JPG, PNG, or WebP file. The limit is 50 MB.
2. 2Pick a target: 20, 50, 100, 200 or 500 KB, or type any number you need.
3. 3Choose JPG or WebP output.
4. 4Download the result. Your original file is never modified.

The right number comes from wherever the image is going, not from guesswork. The ranges below cover the limits that actually show up in upload forms and platform documentation.

• 20 KB: forum and community avatars, which usually render at 200 to 400px, and strict government or school portals that reject anything larger.
• 50 KB: email attachments at corporate gateways, and job or visa application forms with a per-file cap.
• 100 KB: blog and article images, where it sits comfortably inside most CMS budgets.
• 200 KB: marketplace listings and product galleries, where images are re-sampled anyway once uploaded.
• 500 KB: full-width hero images and portfolio pieces that still need to look sharp on a large screen.

For a small target, WebP is usually the better pick. It compresses more efficiently than JPG at the same quality, which matters most when every kilobyte counts, and it keeps transparency — a logo can become a 20 KB WebP without losing its clear background. Choose JPG when the receiving system is old or refuses WebP. JPG fills transparent areas with white, which is fine for a photo of a document but changes how a logo looks.

• WebP: smaller at the same quality, keeps transparency, works in every current browser.
• JPG: the safest choice for old upload forms, but transparent areas turn white.
• Both are lossy, so the quality trade-off applies to whichever you pick.

Some images will not make it. A noisy photo full of fine texture — foliage, a crowd, a gravel path — can still sit above a small target even at quality 1, because there is simply too much detail left to encode. A 2000px shot of leaves might bottom out at 34 KB against a 20 KB goal. When that happens the tool returns the smallest encode it can produce and labels it "Smallest possible" rather than pretending the target was met. Resizing to a smaller width is the fix: fewer pixels means the encoder has less to work through.

Yes, whenever the source is large and the target is aggressive. Resizing discards pixels, which is a far bigger lever than quality alone. A 3000px camera photo that stalls at 90 KB under compression will usually slide under 20 KB once it is 400px wide, because there are far fewer pixels to encode. Run the resizer first, then bring the smaller file here. The same applies in reverse: if a target is easy to hit, skip the resize and keep the extra resolution.