ENPublished: 2026-05-07Updated: 2026-05-07

Compress PNG online: lossy and lossless trade-offs

TL;DR: PNG is a lossless format, which makes it useful for screenshots, graphics, transparency, and exact edges. Compressing PNG can mean lossless optimization, lossy palette reduction, resizing, or conversion to WebP or AVIF. Each choice has a trade-off. Frisbly can help you compress PNG images in the browser by exporting web-focused copies while keeping your original file on your device.

What makes PNG different

PNG is built for lossless image storage. The W3C PNG specification describes PNG image types including indexed-color, grayscale, and truecolor images, with alpha support. That makes PNG useful for UI screenshots, simple diagrams, icons, and graphics where sharp edges or transparency matter.

The same strengths can make PNG larger than needed for photographic delivery. A large full-color PNG photo may carry more bytes than a lossy web format would need. For a screenshot with text, PNG may be appropriate. For a hero photo, WebP or AVIF may be worth testing. The right answer depends on the image content and destination support.

Do not judge by extension alone. A PNG logo, a PNG chart, and a PNG exported from a photo editor are different cases. Start by asking what must stay exact: transparency, text clarity, brand colors, pixel edges, or broad compatibility. Then choose compression settings around that requirement.

Lossless PNG compression

Lossless PNG compression tries to reduce bytes while preserving decoded pixels. It can help when the file has inefficient compression settings or unnecessary chunks, but it may do little when the PNG is already optimized. That is normal. Some files do not have much redundant information left.

PNG compression relies on filtering and DEFLATE-style compression. The libpng manual is a useful technical reference for how PNG files are read and written, while the W3C spec is the formal source for the format. For most web teams, the practical rule is simple: lossless PNG optimization is low risk but may produce modest savings.

If the output must remain PNG, inspect file size and visual output after export. The visual check should pass because lossless work should preserve pixels, but you still need to confirm transparency and display behavior in the destination. Some publishing systems modify uploads after receiving them.

Lossy PNG techniques

Lossy PNG workflows reduce bytes by changing the image. Palette reduction and color quantization can turn a full-color image into a smaller indexed-color file. That may work for flat illustrations or simple UI captures, but it can create banding, color shifts, or jagged edges in detailed graphics.

This is where wording matters. A PNG file can be the container for an image that has already been simplified. The PNG format itself is lossless, but the preparation step before saving PNG can be lossy. If a tool reduces colors before writing PNG, the final PNG preserves the reduced image, not the original image.

Use lossy PNG methods only after visual review. Compare gradients, shadows, antialiasing, and text. If a screenshot becomes harder to read, the byte savings are not worth it. If an icon or chart looks unchanged at the intended size, palette reduction can be acceptable.

When to convert PNG to WebP or AVIF

For web delivery, conversion can be more useful than trying to shrink PNG further. Google's WebP documentation reports WebP lossless images 26% smaller than PNGs in its study, and WebP supports alpha transparency. That makes WebP a reasonable test for transparent graphics and screenshots when the destination supports it.

AVIF can also be tested for some images, especially when file size matters and browser support is acceptable. It may take longer to encode, so batch workflows should start with a small sample. If the destination is a CMS, app store listing, documentation system, or email tool, confirm support before replacing PNG.

Keep PNG when exact pixels, tooling compatibility, or delivery requirements demand it. Convert when the destination accepts the new format and the output passes visual review. A careful workflow can keep both: original PNG for editing and WebP or AVIF for web delivery.

Practical browser-side workflow

Open the PNG in Frisbly, keep the original unchanged, and export a smaller copy for the destination. If the image is larger than the display slot, resize first. Then test WebP and AVIF if both are acceptable. For screenshots, check small text. For transparent graphics, check edges over multiple backgrounds. For charts, check labels and lines.

Use batch processing after you validate settings. Screenshots from the same app may work with similar settings, but photos, diagrams, and logos should be tested separately. Store output files in a new folder and keep a short note about the settings used.

Because Frisbly runs in the browser, your source PNG stays on your device during compression and export. You still control rights, review, and publication. Do not process files you are not allowed to use.

FAQ

Is PNG compression lossless? Native PNG storage is lossless, but some workflows reduce colors or resize before saving PNG. That preparation can be lossy even if the final PNG stores the reduced image losslessly.

Why did my PNG not shrink much? The source may already be optimized, or the image may not have enough redundancy for lossless compression to reduce much. Try resizing or WebP conversion if the destination allows it.

Should screenshots stay PNG? Often, PNG is a strong option for screenshots because text and edges matter. WebP can still be tested, but inspect small labels and UI boundaries carefully.

Does transparency work in WebP? Yes. Google WebP documentation describes alpha support. Test the exported file in the destination, especially around transparent edges.

Try it yourself

Use Frisbly to compress PNG images in the browser, export WebP or AVIF samples, and compare them with the original PNG before publishing.

References

Related tools

Image compressionSVG cleanupFavicon generator