Lossless PNG compression strips metadata and optimizes color tables to reduce file size 15–40% — without changing a single pixel. Transparency, sharp edges, and text stay pixel-perfect.
Lossless re-encoding strips metadata and optimizes color tables. Transparency stays intact.
PNG was designed as a lossless format, which means it stores every pixel exactly as it appears with no quality shortcuts. That's a feature — it's why PNG is the right choice for logos, screenshots, UI elements, and images with text. But it also means PNG files carry a lot of data that isn't strictly necessary for display.
Most of the compressible waste in PNG files comes from three sources. First, metadata and EXIF data: PNG files frequently contain creation software information, color profiles, creation timestamps, and sometimes full copies of ICC color profile data. These can add 50–200 KB. Second, sub-optimal color tables: a PNG saved by Photoshop often embeds an oversized palette with duplicate entries or unused colors. Third, inflated chunk sizes: the PNG format divides image data into "chunks," and image editors often write these chunks less efficiently than a dedicated optimizer would.
What lossless compression does is re-encode the PNG more efficiently — stripping unnecessary metadata, optimizing palette entries, and rewriting chunks tightly. The pixel values are identical. The file is just smaller because all the padding and waste has been removed.
The number after PNG refers to bits per pixel, which determines color capacity and file size. Understanding which subtype you're working with helps set realistic expectations for compression results:
| PNG Type | Color Depth | Transparency | Typical File Size | Best For |
|---|---|---|---|---|
| PNG-8 | 256 colors max | Binary (on/off) | Very small (5–200 KB) | Simple icons, web graphics with flat colors, simple illustrations |
| PNG-24 | 16.7 million colors | None | Medium (100 KB–2 MB) | Photos and graphics where you need full color but not transparency |
| PNG-32 | 16.7 million colors | Full alpha (256 levels) | Large (200 KB–5 MB) | Logos, product cutouts, UI elements needing smooth transparency |
If you have a PNG-32 logo with full transparency that displays well on any background color, don't convert it to JPEG — you'd lose the transparency entirely. The right path is lossless compression to reduce the file, then optionally convert to WebP (which also supports full alpha transparency) for web delivery.
The choice between lossless PNG compression and WebP conversion depends on where the image is going:
PNG works everywhere. Email clients, Word, Google Docs, InDesign, and printers all handle PNG without issues. WebP doesn't have universal support in non-browser contexts. Losslessly compress and share as PNG.
Keep original PNGs as lossless masters. Compress them losslessly for storage efficiency. Only convert to WebP for the web-delivery copy — keep the PNG original intact.
WebP achieves 25–35% smaller files than PNG at the same visual quality, and supports full transparency. If you're publishing to a website, WebP is the better delivery format. 97%+ browser support as of 2025.
For logos and transparent product cutouts on websites, WebP-with-transparency delivers the same visual result as PNG-32 at 25–35% smaller file size. Use a <picture> element with PNG fallback for the rare non-WebP browser.
| Asset Type | Compression Approach | Expected Reduction | Notes |
|---|---|---|---|
| Logo (transparent) | Lossless PNG → optionally WebP | 20–40% | Never JPEG — sharp edges need lossless. WebP for web delivery. |
| Screenshot / UI | Lossless PNG compression | 15–30% | Text and interface elements need lossless — JPEG introduces ringing |
| Illustration (flat colors) | PNG-8 if ≤256 colors, else lossless PNG or WebP | 30–60% | Flat color illustrations often work well as PNG-8 |
| Photo saved as PNG | Convert to JPEG or WebP instead | Won't help much | Compressing a photo PNG is the wrong fix — change the format |
| Product cutout (transparent) | Lossless PNG or WebP lossless | 20–35% | Shopify and e-commerce sites benefit from smaller product PNGs |
| Icon set | Lossless PNG or SVG | 15–25% | For icons with fewer than 256 colors, PNG-8 or SVG is most efficient |
The most common PNG optimization mistake is using PNG for the wrong content type. Understanding when PNG is and isn't appropriate prevents you from fighting against the format's design.
A 4000×3000 photo saved as PNG is typically 15–25 MB. The same photo as JPEG at quality 85 is 1–3 MB. PNG adds zero visual benefit for photographic content — it just bloats the file. Use JPEG or WebP for photos.
JPEG introduces ringing artifacts around every sharp edge. A screenshot with menus, text, or UI elements at JPEG quality 80 will show visible degradation around every letter and line. Use lossless PNG or WebP lossless for screenshots.
Photos → JPEG or lossy WebP. Screenshots, logos, text-containing images → PNG or lossless WebP. Animated images → WebP (animated) or MP4. The format choice matters more than compression level for PNG content.
The optimal web delivery workflow: losslessly compress the PNG (for the archive copy), then convert to WebP for web delivery. You get the smaller WebP size on the web while preserving the lossless PNG original.