Local target-size compression

Reduce Image Size in KB

Enter a custom KB or MB goal. PicRecast searches real output Blobs locally and never treats an estimate or an above-target file as success.

1

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.

2

Set target and compression behavior

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

Exact file-size target

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

Compression behavior
Output format
JPG transparency background
3

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 reduce image size to a custom target

  1. 1Choose one supported image and enter a KB or MB target.
  2. 2Select Strict target or Keep dimensions, then keep or explicitly change the format.
  3. 3Run the bounded local search and verify the exact output bytes 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 target you control

Use the upload limit you actually need. Decimal units mean 1 KB is 1,000 bytes and 1 MB is 1,000,000 bytes.

Strict versus Keep dimensions

Strict may reduce dimensions after quality reaches its safe minimum. Keep dimensions never resizes and labels an above-target result honestly.

Keep format or change it explicitly

The source format is the default. JPG and WebP use real quality searches; PNG uses lossless OxiPNG and optional dimension reduction in Strict mode.

Valid custom targets

Enter 100 to 25,000,000 bytes with no more than three decimal places. Invalid, too-small, or out-of-range values keep processing disabled.

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.

Custom target compression FAQ

How are KB and MB calculated?

PicRecast uses decimal units: 1 KB = 1,000 bytes and 1 MB = 1,000,000 bytes, rounded to the nearest whole byte.

Will Strict mode crop my image?

No. It may reduce pixel dimensions while preserving aspect ratio, but never crops or stretches.

Will PicRecast change formats automatically?

No. A format change happens only after you explicitly choose JPG, PNG, or WebP.

Is the image uploaded?

No. Validation, candidate encoding, selection, verification, preview, and download stay in the browser.