Compress PNG

Choose PNG files

Choose PNG files

Processing...

Browser PNG re-encoding may change colour-profile interpretation or metadata. Animated PNG files are rejected; output is always a static image/png file. Resizing may interpolate colour and alpha values.

Compress static PNG files without uploading them. The tool uses your browser’s image decoder and PNG encoder, shows the actual size change, and keeps the original unchanged when a full-colour re-encode would be larger.

How to compress PNG files

  1. 1

    Choose static PNG files

    Select up to 10 files, with limits of 20 MB and 24 megapixels per file and 50 MB for the batch. Animated PNG is rejected.

  2. 2

    Set colour precision and width

    Keep full RGB precision or reduce each RGB channel to 6, 5, or 4 bits. Optionally set a smaller maximum width.

  3. 3

    Review the real result

    Compare original and output bytes, dimensions, and the signed percentage change before saving anything.

  4. 4

    Download PNG output

    Every generated file is verified as image/png and given a .png filename.

What this compressor actually does

The browser decodes each static PNG into a canvas and encodes the rendered pixels as a new PNG. Full colour keeps 8-bit RGB precision. The 6-, 5-, and 4-bit settings round the red, green, and blue channels to fewer levels, which can help flat artwork compress but may introduce banding. Alpha values are not rounded by that control. If you resize, canvas interpolation can change both colour and alpha around edges.

This is not an oxipng filter search or a pngquant indexed-palette encoder. A browser-generated PNG can be larger than its source. With full colour and unchanged dimensions, the tool returns the original file whenever that file is already smaller. In that case its original metadata is also retained.

Limits and privacy

  • Up to 10 PNG files, 20 MB each and 50 MB in total
  • Up to 24 megapixels and 8192 pixels on either side
  • Generated output is limited to 50 MB per PNG and 100 MB per batch
  • Static PNG only; APNG animation is rejected rather than reduced to one frame
  • Files are processed locally and never sent through Livewire or an upload endpoint
  • In the four-step flow, files can be restored for 30 minutes. An active page removes them after expiry; if the page was closed or suspended, the next multi-step visit removes expired or malformed records

Canvas re-encoding can remove metadata and can change how an embedded colour profile is interpreted. It preserves the browser-rendered appearance, not the original encoded samples or ancillary chunks bit for bit.

Frequently Asked Questions

It retains full 8-bit RGB precision, but browser decoding and colour management mean a re-encoded file is not guaranteed to match the original encoded samples or metadata bit for bit. If the unchanged full-colour output is larger, the original file is kept instead.

The colour-precision control leaves alpha values untouched. Resizing can interpolate semi-transparent edge pixels, and browser re-encoding can change metadata or colour-profile interpretation.

PNG size depends on pixel patterns, filters, and the encoder. The browser encoder may be less efficient than the program that created the source. The comparison reports the real signed change rather than promising a fixed saving.

No. Decoding, canvas work, comparison, and downloads happen in the browser. The multi-step flow makes files restorable for 30 minutes; an active page removes expired copies, while closed or suspended sessions are cleaned on the next multi-step visit.

Related Tools