Compress an image to 200KB

200KB is set as the target by default because it's the size most forums, CMS avatar fields and email attachment limits are built around - loose enough to keep real detail, tight enough to clear the ceiling. Drop a photo in and the tool searches for the highest quality that fits under 200KB, entirely on your own device.

No upload No file size limit No sign-up Free

Drop images here

or click to choose — JPG, PNG, WebP, GIF, BMP — multiple files supported

Target file size

Custom target (KB)

Output format

Minimum width (px)

If quality reduction alone cannot reach the target, the image is scaled down — but never below the minimum width you set here.

Where the 200KB ceiling comes from

200KB sits in a different spot than the stricter government-form limits. It's closer to what forum software, CMS avatar fields, marketplace listings and mail providers were built around — loose enough to keep real detail in a photo, tight enough to keep page load times and inbox storage in check. If you've landed here from a bounced email or a "file too large" error on a listing site, 200KB is very likely the number behind it.

What 200KB actually buys you over 100KB

Width	At 100KB	At 200KB
~800px	Clean	Clean, more quality headroom
~1200px	Usually needs scaling down	Comfortable, minimal artefacts
~1600px	Visible quality loss	Good quality at normal viewing size

In practice, the jump from 100KB to 200KB is the difference between an image that clearly went through a compressor and one where you'd have to zoom in to tell. It's the target this tool defaults to for exactly that reason.

Email attachments: watch the encoding overhead

If you're compressing specifically to fit under an email provider's attachment limit, be aware that the number they enforce isn't measured against your raw file size. Email attachments are base64-encoded for transport, which inflates the effective size by roughly a third. A 200KB image can arrive looking closer to 270KB to the mail server doing the counting. If you're right at the edge of a stated limit, aim comfortably under it rather than exactly at it — the 100 KB target is the safer choice if the provider's limit itself is small.

Format choice matters more at this size

WebP is worth using here if you control the destination — your own website, an app, storage you manage. It reaches the same visual quality as JPEG at roughly 25–35% smaller file sizes, which at a 200KB ceiling translates into a genuinely sharper result rather than just a smaller file.

JPEG is still the right call for anything going to a third-party form, a forum upload, or an email attachment — support is universal, and you don't want to discover a WebP rejection after you've already composed the email.

If quality alone won't reach 200KB

This tool searches for the best quality setting at your image's current dimensions first, and only scales the image down if that search can't reach the target. The minimum width field controls how far it's allowed to go — raise your target, or lower that field, if a result keeps coming back smaller than you wanted.

Nothing is uploaded to do this

Decoding, quality search and re-encoding all happen inside your browser via the Canvas API. The photo is never sent to a server, so there's no queue, no daily limit and no third party handling the file in between. As a side effect, re-encoding through a canvas also strips EXIF metadata — GPS coordinates, camera model, timestamps — from the result automatically.

Frequently asked questions

Why 200KB specifically, rather than 100KB or 500KB?

It's the size most forum software, CMS avatar uploaders and mail providers were built around - loose enough that a decent-resolution photo still looks sharp, but small enough to keep page load times and inbox storage under control. If your target is stricter, the 100KB page runs the same tool with that ceiling instead.

Will a 200KB photo look noticeably compressed?

At a typical 1200-1600px width, no - 200KB is usually enough headroom that quality loss isn't visible at normal viewing size. You'll see it if you zoom in close or print large, but for a profile photo, forum avatar or email attachment it holds up fine.

My email keeps bouncing even under 200KB - why?

Some providers count the full email (headers, encoding overhead, any signature images) against the attachment limit, not just the raw file size - base64-encoding an attachment for email transport adds roughly 33% to its size. If you're right at the edge, aim comfortably under the stated limit rather than exactly at it.

JPEG or WebP for a 200KB target?

WebP if you control the destination - your own site, an app, storage you manage - since it reaches the same quality at a meaningfully smaller size, leaving more visual headroom under 200KB. Stick to JPEG for anything going to a third-party form or an email attachment, since support there isn't guaranteed.

Is this different from the general compress-to-target-size tool?

No - same engine, same accuracy, this page just starts already set to 200KB. The full tool with every preset (50KB through 2MB) is at compress-image-to-target-size.

Are my photos uploaded anywhere to do this?

No. The compression runs in your browser using the Canvas API. Open your network tab, or disconnect from the internet after the page loads - the tool keeps working, because the photo never leaves your device.