How to Compress an Image to Under 200 KB (JPG, PNG, WebP)

Images · Published 2026-11-10 · YYSI Editorial · 中文版

The short answer

Open the image compressor, set Mode to Target size (KB), keep the target at 200, pick an output format (see the table below), add your files and press Compress. A photo at 2400×1600 came out at 202,028 bytes in our test — under the target. Whether 200 KB is enough for your image depends on its type: photos compress easily, screenshots compress well as WebP, and a transparent PNG kept as lossless PNG may not shrink at all.

What "200 KB" means here: KB vs KiB

Upload forms rarely say which "KB" they mean. This tool counts in binary units: the target value is multiplied by 1024, so a target of 200 means 204,800 bytes (200 KiB), and the sizes shown in results use the same 1024-step convention with rounding (the row "197 KB" was 202,028 actual bytes in our test). Some systems check against 200,000 bytes (decimal KB). If your form does that, play safe: enter a target of 195 (199,680 bytes) and, for anything strict, download the file and check its real byte size yourself — the displayed value is rounded, the file on disk is the truth.

Steps in the tool

1. Open. Go to the image compressor. Files are processed in your browser; nothing is uploaded. Limits: 20 files per batch, 20 MB and 25 megapixels each.
2. Set the mode. Under Mode, choose Target size (KB). The Target size per image (KB) box appears with a default of 200 — keep it or type your own.
3. Pick the output format. Output format: *Same as input* keeps the file type; *JPG*, *PNG* or *WebP* converts every file. Rule of thumb from our tests: JPG or WebP for photos, WebP for images that must stay transparent, and expect little change if you keep a screenshot as PNG.
4. Add files and compress. Drag the files in (or click the drop area) and press Compress. Each row shows the size change and the quality used, for example 1.61 MB → 197 KB (-88%) · Q22.
5. Download and verify. Download each file (or all as a ZIP). If the receiving system is strict, check the downloaded file's byte size — that is the number that counts.
6. Read honest failures. A row saying already well compressed — original kept means the tool could not shrink that file without changing its format or losing the condition you asked for (for example lossless PNG), so it kept your original instead of pretending.

Our test results (2026-11-10, desktop Edge)

We drew three original synthetic samples — a photo-like scene, a transparent logo and a text screenshot — and ran them through the tool at target 200. All numbers below are actual file bytes read back from the downloaded output, not the rounded display:

As a comparison, the quality-level mode at the default Q80 turned the same photo into 1,244,344 bytes (1.19 MB) — smaller, but nowhere near 200 KB. That is the difference between the two modes: quality mode compresses by a fixed level; target mode searches for the largest quality that still fits your number.

Why the transparent PNG refused the target

PNG is a lossless format: re-encoding rewrites the file but must reproduce every pixel exactly, so size barely moves. Our logo stayed at 325,503 bytes and the tool said so instead of handing back a fake result. To actually get that logo under 200 KB you must give something up:

• Switch to WebP — came out at 204,422 bytes (Q76) and kept the transparency (we verified the corner pixels are still transparent). Usually the best trade for logos and UI graphics.
• Switch to JPG — came out at 194,432 bytes (Q94), but JPG has no alpha channel: the tool flattens transparency onto a white background (verified in our output). Fine for printing or embedding on white; wrong for layering.
• Resize smaller first — fewer pixels means a smaller lossless PNG. Use the image resizer if the destination allows smaller dimensions.
• Re-export from the source — a flat-color logo re-exported from its design file is often a fraction of the PNG-from-photo size.

Lossy vs lossless, and what changes what

Choose by scenario

• Portal/exam/job upload demanding “JPG under 200 KB” — target mode, output JPG, target 200; if the form checks decimal bytes, target 195. Photos work directly; documents that started as PNG scans convert cleanly but text edges soften a little at strong compression.
• Logo/graphic that must stay transparent and small — target mode, output WebP (transparency kept). If the destination refuses WebP, JPG-on-white or a resized PNG are the fallbacks.
• Screenshot to send by mail/chat — target mode, output WebP; our 531 KB screenshot became 202,956 bytes at Q76 and text stays readable. Keep PNG only when every pixel must stay identical (design handoff), and then compress differently.
• File already under the target — leave it alone. The tool detects this and keeps your original instead of re-encoding for nothing.

Known limits and failure handling

• Inputs: JPG, PNG, WebP only; up to 20 files, 20 MB and 25 megapixels each. Anything else needs the image converter first (GIF/BMP/AVIF/SVG inputs are supported there).
• No password/EXIF stripping guarantee: re-encoding through the browser canvas drops most original metadata, but do not rely on this for privacy — remove sensitive data explicitly before sharing.
• Quality numbers (Q values) come from the browser's own encoders and differ between browsers; the byte size is what matters, not the Q value.
• If a row reports the closest honest result but still misses the target, no quality setting will fit at the current pixel size — resize smaller or convert format.
• Everything runs locally in the browser tab; processing time depends on your device.

Try it with our samples

The sample files below are the exact inputs from our test runs (YYSI-made synthetic drawings, no third-party material). Download them, run the tool with target 200, and compare your byte counts with the table above.

• photo-2400x1600.jpg — photo-like sample, 1,683,390 bytes — Download sample · 1683390 bytes
  SHA-256: 79cdefc198131faa8f1fc9a5a5363afbb32d9ccad637958a07d669d754c7a21b
• transparent-logo-2000x1400.png — transparent logo, 325,503 bytes — Download sample · 325503 bytes
  SHA-256: 680fdeb3055503c6c2d6ca360dbe0430dd33b54bb38705ad117b808d2e2863d1
• text-screenshot-2200x1400.png — text screenshot, 543,857 bytes — Download sample · 543857 bytes
  SHA-256: f7291c7e3a4124dbad10c2b6e144884b193cccf0b1d70aa2dd11b94e33abaa5a
• photo-2400x1600.webp — already-small WebP, 27,020 bytes — Download sample · 27020 bytes
  SHA-256: a17820613bd249881668c202506ae6e73b593079c4d690a30d4833bb027a2452

SHA-256 checksums are shown next to each download link so you can confirm the file you received is the file we tested.