Compress Image to 200KB, 100KB or 50KB: Free, No Upload

How to compress an image to 200 KB in your browser

Compressing an image to 200 KB takes about thirty seconds: drop the file on the tool above, leave the quality slider at 80%, and read the before-and-after size printed on each row. There's no signup and no upload: the file is decoded and re-encoded inside this tab.

Photos don't compress the same way twice, so run the same order every time: pixels first, quality second, verify.

• Resize first. Type a width into Max width: 1600 px for web and email, or the exact pixels a form specifies. Dimensions remove most of the weight; the slider finishes the job.
• Compress second. 80% is the default for a reason: at normal viewing size the photo looks unchanged, while the file gets dramatically smaller.
• Re-run if you're over. Still above 200 KB? Drop the slider five points and press Re-compress with current settings: every run restarts from your original file.

Reduce image size in KB without losing quality

'Without losing quality' means without losing anything you can see at the size you actually display the image. JPEG and WebP are lossy formats: they quietly drop texture detail your eye rarely notices, and that discarded detail is where the savings come from.

Typical results for a 4000×3000 camera photo re-encoded as JPEG (ranges rather than promises, since a crowded tree line costs more bytes than an empty sky):

Between 70% and 85% photographs stay visually identical while the file shrinks hard; below 50% you're trading detail you can see for kilobytes you may not need. If the portal accepts WebP, switch format: the same photo usually lands smaller as WebP than as JPEG.

Compress an image for an email attachment (Gmail's 25 MB cap)

Gmail refuses a message once the attachments and the message text together pass 25 MB. A single modern phone photo can weigh 3–6 MB, so three or four originals from a weekend already push you over the line before anyone replies and quotes every image back to you.

• Cap the width at 1600 px. Attachments are viewed on a screen, and 1600 px fills a phone or laptop display comfortably.
• Compress at 80%. At that setting and width a photo typically lands in the hundreds of kilobytes, so a dozen fit in one message with room to spare.
• Leave headroom for replies. Corporate and school mail servers often allow far less than Gmail, and every reply carries the attachments forward again.
• Batch the whole folder. Drop everything at once, press Download all, then attach the compressed copies instead of the originals in your gallery.

Sending a scan instead? Same recipe: 1000–1600 px wide at 75–85% brings a text page down to the low hundreds of kilobytes while staying sharp enough to print.

What we actually tested: encoding, DevTools and real numbers

We wrote this tool, so this is what we checked first-hand:

• The encode path. Each file is decoded in the browser, drawn onto a canvas at the target width, then written out by the canvas encoder at your quality setting: no server step in that chain.
• DevTools → Network proves it. Open DevTools, filter the Network tab and compress a photo: the only requests listed are this page's own HTML, CSS and JavaScript. No POST, no multipart upload, no image bytes.
• Typical 80% results. A 4000×3000 photo at 80% quality usually lands around 600 KB to 1.3 MB; with the 1600 px width cap it drops to a few hundred KB.
• It never inflates a file. With 'Same as input' selected, a re-encode that comes back the same size or larger is discarded and your original is delivered instead.
• PNG ignores the quality slider. It's lossless, so savings there come from changing the width or switching output format.
• EXIF is stripped on every re-encode: GPS coordinates, camera model and timestamps aren't carried over. If the tool kept your original instead, its metadata is still intact, so run sensitive shots through our guide to removing location data from photos first.