PNG compression — Delivery workflow

Worked example

To deliver PNG files, keep a master, produce the sizes each destination needs, and decide whether a lighter WebP version should travel with the PNG.

A designer sending a logo for an email footer, a website header and a social profile might prepare 1024 × 1024 as the master, 512 × 512 for the site and 256 × 256 for the footer. Resize each from the master and then compress, rather than repeatedly shrinking one copy. Downloads end in compress.png, so add the size yourself, for example logo-512.png.

Think about where transparency is needed. Email clients and slide decks accept PNG widely, so it is a safe choice for a transparent logo. A website can often use WebP for the same image at lower weight, but keep the PNG as a fallback and check that the destination accepts the file before you rely on it.

For a set of icons, load them together and process them one at a time. The queue holds up to 12 images and 48 MB of input, and finished results can be saved as a ZIP with numbered names such as 01-icon-compress.png. Completed outputs are retained up to 64 MB, so split very large screenshot batches.

The mistake to avoid is delivering only the optimised copy. Hand over a small folder with the master PNG, the sized versions and a note on pixel dimensions and whether each has transparency. Keep that master safe, because it is the only file you can reuse without quality questions.

PNG logo with alpha

PNG; transparency retained when supported

Compression runs in your browser, so the files are not uploaded; closing the tab discards unsaved results.