Local target-size compression

Compress Image to 100KB

Use a 100KB target with real quality search, optional Strict resizing, and transparent Alpha-preserving output behavior.

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: 100,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 100KB

1Choose JPG, PNG, or static WebP.
2Review the target, search mode, output format, and JPG background if relevant.
3Inspect exact bytes, final quality, scale, and dimensions before downloading.

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.

A balanced general-purpose target

100KB can work for photos, product images, and document previews, but the visual result still depends on complexity and is not promised to look lossless.

Strict and same-dimension choices

Strict may resize proportionally only when quality is insufficient. Keep dimensions prioritizes unchanged pixels and honest status.

Transparency-aware output

WebP and PNG preserve Alpha. Explicit JPG output composites transparent pixels over the chosen background.

Actual candidate sizes

Non-monotonic encoder results are handled by boundary refinement and real-candidate ranking within a hard attempt limit.

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.

100KB compression FAQ

Is 100KB exactly 100,000 bytes?

Yes. The target uses decimal KB and success requires an output no larger than 100,000 bytes.

What gets prioritized in Strict mode?

It first seeks a target-meeting result, then favors more pixels, higher quality, and closeness to the target.

Can I explicitly convert formats?

Yes. Format conversion is opt-in and is disclosed in the result.

Does the Worker use a server?

No. A Web Worker is a browser thread; the controlled fallback also remains local.