Local target-size compression

Compress Image to 200KB

Target 200KB while keeping more dimensions or quality, with real Blob verification and lossless PNG optimization.

Runs in your browser
No image upload
Review before download

Choose an image

Add one supported image. A replacement is accepted only after it passes local validation.

Static JPG/JPEG, PNG, and WebP. Animated WebP is rejected. Processing stays in this browser.

Set target and compression behavior

Choose exact decimal KB or MB, whether dimensions may change, and the output format.

Exact file-size target

Target valueUnit

Exact target: 200,000 bytes (1 KB = 1,000 bytes; 1 MB = 1,000,000 bytes).

Compression behavior

Strict target — may reduce dimensionsQuality is tested first. If needed, pixel dimensions are reduced without cropping or stretching.Keep dimensions — find the closest resultOriginal pixel dimensions stay fixed. A result above the target is labeled clearly, not reported as achieved.

Output formatOutput format

JPG transparency backgroundFill transparent pixels with

Review the actual result

PicRecast tests real encoded files and reports the selected file's exact bytes before download.

Choose an image to begin.

Three-step workflow

How to target 200KB

1Choose a supported static image.
2Keep 200,000 bytes or edit the target and choose Strict or Keep dimensions.
3Run the local search and review the exact verified result.

Choose the tradeoff that fits this target

Target bytes, image detail, pixel dimensions, and output format interact. Review the verified result instead of relying on an estimate.

More room for larger previews

200KB is less aggressive and can retain more resolution or quality for larger previews and web images. An original already below target is kept unchanged.

Preserve dimensions when practical

Keep dimensions reports the closest same-size output. Strict resizes only after the original dimensions cannot meet the target.

Lossless PNG remains lossless

PNG candidates use OxiPNG at every tested dimension, preserve RGBA and Alpha, and never use hidden palette quantization.

Honest no-improvement handling

If an already-efficient source is smaller than the selected result, PicRecast warns instead of calling the larger output compressed.

File size is not pixel size

Width and height describe pixels; KB and MB describe encoded bytes. Reducing either quality or dimensions can change file size.

JPG, PNG, and WebP differ

JPG and WebP support quality search. PNG uses lossless OxiPNG, so a very small target may require proportional resizing.

Metadata may be removed

Newly encoded files may not retain EXIF metadata or color profiles. Keep the original and inspect the download.

Why a result can miss the target

Format overhead, safe quality limits, minimum dimensions, and bounded attempts can leave a verified result above the target.

Local processing boundary

Validation, candidate encoding, comparison, preview, and download stay in this browser. Images are not sent to a processing API.

200KB compression FAQ

What happens if the original is already below 200KB?

The original is kept without unnecessary re-encoding and the result is labeled already under target.

Can Strict still fail?

Yes. A target can remain unreachable at minimum quality, dimensions, or the attempt limit; the real smallest result is shown.

Does PNG use a quality slider?

No. PNG uses lossless OxiPNG and proportional dimension search only in Strict mode.

Is OxiPNG fetched from a third party?

No. The locked codec asset is self-hosted and loaded only when PNG processing needs it.