Skip to content

Compress an image to 200 KB

Bring a photo under a 200 KB limit while keeping it sharp — a comfortable budget for full-width web images and most application forms.

  • Runs in your browser
  • Files are never uploaded
  • Free, no account
Drop the images that need to come in under 200 KBAdd as many as you like — every encode runs on your own CPU, so the retry loop costs nothing.JPG, JPEG, PNG, WEBP, AVIF, GIF, BMP · up to 200 MB each
Target size
We aim 2% under the limit, because upload forms compare against a hard byte ceiling.

1 KB = 1024 bytes, the same arithmetic your operating system uses.

Only kicks in when quality 5 still overshoots.

200 KB is the web-performance sweet spot

Most page-speed guidance lands in the same place: keep individual images under about 200 KB and the whole page under a megabyte or two. At 200 KB a full-width hero photo still looks excellent, and on a mid-range mobile connection it arrives in well under a second. Above that you start paying for detail nobody looks at — and Largest Contentful Paint, the Core Web Vital that most often fails, is usually exactly this image.

Resize before you compress

This is the biggest win available and it is routinely skipped. A 4000 px photo displayed in an 800 px column carries twenty-five times more pixels than the layout can show. Cap the width first — the field is right there in the options — and the quality search then has far less work to do, so the same 200 KB buys a much sharper image. As a starting point:

PlacementSensible max widthTypical size at quality 80
Full-width hero1920 px180–300 KB
Content column image1200 px90–160 KB
Card or listing thumbnail600 px25–50 KB
Avatar200 px6–12 KB
Email newsletter image1200 px100–180 KB

Metadata is a bigger share than you think

A camera JPEG carries an EXIF block, often an embedded colour profile, and a full JPEG thumbnail of itself. Together those routinely add 20–80 KB — up to 40% of a 200 KB budget spent on data no browser displays. Because this tool re-encodes from raw pixels, all of it is dropped automatically. If you want to inspect what was in there first, use the metadata viewer; if you only want the metadata gone without touching the pixels, use Remove EXIF Data.

JPEG, WebP or AVIF for the web?

  • WebP — supported by every current browser, typically 25–35% smaller than JPEG at matching quality. The default choice for a modern site.
  • JPEG — universal, including in email clients and older CMS previews. Pick it when you do not control the consumer.
  • PNG — only for screenshots, logos, charts and flat colour. A photo saved as PNG is often ten times larger than it needs to be.

Batch a whole gallery

Drop in the entire folder. Each image is searched separately to the 200 KB target, with its own progress row, and “Download all as .zip” bundles the results in one go. There is no ten-file cap and no daily quota: the encoding runs on your CPU, so batching costs us nothing to allow. For a large gallery, set the width cap as well — it makes the whole run several times faster because every attempt encodes fewer pixels.

Checking your work

The result card gives you the achieved byte count, the dimensions and the exact quality the search chose. If the quality it settled on is 90 or above, your target is generous and you could go lower; if it is under 55, the image is fighting the budget and you should crop or resize rather than accept the artefacts. That feedback loop — which server-based tools cannot give you without another upload — is the point of doing this locally.

Other targets

100 KB · 500 KB · 1 MB · any target you type.

Questions

Is 200 KB enough for a good-looking web image?

Comfortably. A 1600 px-wide hero photo at quality 75–82 usually lands between 120 and 200 KB, which is well inside the budget most performance audits ask for.

Should I resize as well?

Almost always. A 4000 px photo shown in an 800 px column carries 25 times more pixels than it needs. Cap the width first and the quality search then has far less work to do, so the same 200 KB buys a much sharper picture.

Does it strip metadata?

Yes, as a side effect of re-encoding from raw pixels. EXIF blocks, colour profiles and camera thumbnails can add 20–80 KB on their own, which is a large share of a 200 KB budget.

Can I compress a batch to the same limit?

Yes. Every image gets its own independent search to the same target, and “Download all as .zip” bundles the results.