ZumaTools

Compress image to 200 KB

Room for a genuinely detailed photo: 200 KB keeps product and listing images sharp at full width.

Updated · Published by Novpix LLC

Drop images here

or click to browse · JPG, PNG, WebP · multiple files supported

Images are processed on your device and never uploaded.

Options

Runs entirely in your browser — nothing is uploaded

How it works

  1. 1Drop your photos into the box above — a whole set of listing images at once works fine.
  2. 2Each file is re-encoded to the best quality that fits under 200 KB, so detail is kept where the budget allows.
  3. 3Download the compressed copies and upload them to your listing, forum or document.

Frequently asked questions

Is 200 KB enough for product photography?
Comfortably. Two hundred kilobytes supports a photograph around 1500 pixels wide at a quality level where compression is invisible — larger than most marketplaces display, and larger than the zoom view on many of them. The constraint that bites in e-commerce is usually the number of photos per listing, not the quality of each one.
Which platforms use a 200 KB limit?
It is common on marketplace and classifieds listings, forum attachments, school and university learning systems, and internal document workflows — places that accept many images per item and cap each one to keep pages loading quickly on slow connections.
Should I resize before compressing, or let the tool do it?
For 200 KB, let the tool work at the original dimensions first; the target is generous enough that quality reduction alone usually reaches it. Resize first only when you know the display size — a listing thumbnail never needs 4000 pixels, and starting from the right dimensions leaves the whole budget for detail.
Will white backgrounds compress better?
Substantially. Compression pays for variation, so a product shot on a clean white sweep costs a fraction of the same object photographed on a patterned rug. If you control the shoot, a plain background improves both the look of the listing and the quality you can keep within any size limit.
Does this strip the metadata from my photos?
Yes — re-encoding produces a fresh file without the original EXIF block, so camera model, timestamps and any GPS coordinates recorded at the shoot do not travel with the image. For listings and public uploads that is usually welcome. If you need the metadata, keep the original, which is never modified.

About this tool

Two hundred kilobytes is the size limit you meet where images come in sets: marketplace listings with a dozen photographs, forum threads full of attachments, course material, internal documentation. The cap exists because the page has to stay usable when every one of those images loads at once, which is a different problem from a single profile photo.

It is also a generous budget. A photograph around 1500 pixels wide fits inside 200 KB at a quality level where the compression is not visible, which is more than most platforms display and enough for their zoom view. That means the honest answer for this target is usually reassuring: you can meet the limit without any visible sacrifice, provided you start from a good original.

What decides the outcome is the content of the frame. Compression spends bytes on variation, so a product on a plain white background reaches the target at high quality while the same object on a patterned surface needs noticeably more compression. Photographs of foliage, fabric texture and crowds are the expensive cases. If the images are yours to shoot, a clean background is worth more than any setting in this tool.

Because everything runs locally, a batch of twenty listing photographs is processed as quickly as your device can encode them, with no upload, no queue and no per-day limit. Re-encoding also drops the EXIF metadata — camera details, timestamps, GPS coordinates — which is generally what you want before publishing images publicly. Your originals stay untouched on disk.

Related tools