9314JIUsi
Image compression · 200KB scene

Compress to 200KB: forum attachments and upload limits

Forum attachments, legacy portals, the classic 200KB ceiling. Target preset, drop and compress.

Old forum software, corporate intranet forms, school homework portals - 200KB is the most classic limit still in service. Phone photos run 3-8MB, 15-40× over. At 200KB the quality loss is invisible to the eye for everyday shots.

SCALE BENCH binary-search quality ×8 rounds · auto-downscale ×6 steps
📎

Click to choose / drag & drop / Ctrl+V paste, multi-select supported

JPG / PNG / WebP / GIF (resize only), up to 50MB each, up to 20 files

KB or less

Adjustable 10-2000KB; preset fits attachments

WebP saves more on screenshots; pick JPG when compatibility rules.

Your images are compressed inside this device's browser - nothing is uploaded and it works offline. Target size and format live only in this browser's localStorage; switching devices or clearing site data loses them. "Clear my data" in the footer wipes them.

Queue is empty - drop attachment-bound images in, each one gets its own pass/fail badge.

Three steps

  1. Feed drag signatures or scans onto the bench (multi-select fine); each file's size shows up in the queue instantly.
  2. Set target is preset to 20KB, adjustable; JPG recommended, switch to PNG only for transparent icons.
  3. Take results arrive per file: green ✓ badge plus the real size in the file name; files already under target are left as-is.

Facts & limits

InputJPG / PNG / WebP / GIF; up to 50MB each; animated GIFs get resize-only (no frame compression); transparent PNGs are flattened to white when output as JPG
OutputJPG / WebP / PNG / Smart (PNG→WebP, others keep their format); file names carry target and actual size, e.g. photo-20kb-19KB.jpg
Key parametersTarget preset to 200KB (range 10-2000KB); binary-search quality 0.30-0.96, up to 8 rounds; auto proportional downscale to 85% when it does not fit, up to 6 steps
ProcessingBrowser-local Canvas encode/decode, no upload, no account; settings live in this device's localStorage (nothing written on first load), images never touch disk
LimitsUp to 20 files per run, 50MB each; queued one by one, a single failure never blocks the batch
Known limitsAlmost nothing misses 200KB (full-frame high-ISO and mega-tall screenshots excepted, red badge honest); PNG needs downscaling to fit; HEIC unsupported - iPhone users convert to JPG first

FAQ

Is 200KB compression visually lossy?

Practically not. 200KB buys JPG quality 75-90 at 1200-1600px on the long edge - a range even working photographers struggle to identify blind. Only large gradient skies or high-ISO noise fields may show faint banding. Daily photos, screenshots and chat-archive images are effectively indistinguishable at 200KB.

Why do so many systems still cap at 200KB?

History: forum engines of the 2000s (Discuz, stock phpBB configs) set 200KB attachment limits to match then-storage costs, and plenty of intranets and school portals never changed them. Storage is cheap now, but changing a system config takes a approval chain - so in 2026 you still squeeze 8MB photos under 200KB by hand.

Do long chat screenshots survive 200KB?

Yes - chat captures are compression-friendly: flat color blocks plus regular text. One caveat: some portals reject ultra-tall images (over 8000px high) outright, so split those first; this tool only scales proportionally, never crops content. Judge legibility at 100% zoom: if the small captions next to stickers read clearly, you are set.

Do images already under 200KB get recompressed?

No point, and the tool does not bother: files already below target get an instant green badge and keep essentially their original bytes (no compress-then-grow nonsense). Batches mixing small and large files are common; per-file badges exist exactly for this.

What kind of image fails to fit 200KB?

Rarely anything: after 8 binary-search rounds plus 6 downscale steps, the survivors are full-frame high-ISO RAW exports and thousand-line screenshots. If you see the red badge, crop or split the image - and if even that fails, what you have is probably a job for a file archiver, not an image compressor.

Are my images uploaded anywhere?

No. The page reads local files with browser Canvas and exports Blobs - no upload endpoint, works offline. Only the target size and format preference sit in localStorage on this device; they do not follow you elsewhere, and "Clear my data" in the footer removes them.

Related tools