Questions, answered
Short answers specific to this page. The tool above settles most of them in a second.
- Does compressing a PNG damage transparency?
- No. The alpha channel survives palette quantization intact, including semi-transparent pixels like drop shadows and anti-aliased edges. You can check every result against a checkerboard in the compare view, so you verify the transparency instead of trusting a promise.
- Is PNG compression lossless or lossy?
- The PNG format is lossless, but the big savings tool is subtly lossy. That tool is palette quantization, the TinyPNG technique we also use. It reduces the palette to 256 or fewer expertly-chosen colours. On screenshots and graphics the difference is usually invisible. The slider lets you check.
- Why is my PNG file so large?
- Usually because it holds a photograph. PNG stores pixels faithfully, and photographs have millions of subtly-different colours. Our reference photo weighs 1382.4 KB as PNG and 74.2 KB as an equivalent JPEG. PNG earns its bytes on graphics, screenshots and transparency. Photos belong in JPEG, WebP or AVIF.
- How much can a PNG realistically be reduced?
- Measured, not promised: our photographic reference dropped −86% on Auto (1382.4 → 189.8 KB). A big UI screenshot dropped −85% (2683.7 → 394.8 KB). Flat-colour art compresses hardest. Photos vary most.
- What is the difference between PNG-8, PNG-24 and PNG-32?
- Bit depth. PNG-8 stores up to 256 palette colours (small), PNG-24 stores full truecolour (big), and PNG-32 is truecolour plus an alpha channel. Quantization converts 24/32-bit images toward 8-bit territory. That conversion is where the savings live.
- Does converting to 8-bit keep the alpha channel?
- Yes. Unlike GIF, PNG-8 supports full alpha per palette entry, so quantized output keeps real transparency, including soft edges. This misconception keeps people on heavyweight PNG-32 exports. The compare view will show you the alpha survived.
- How do I get a PNG under 50 KB or 100 KB?
- Set Max file size in Advanced settings. The cap is hard: we meet it by tightening quantization and, if needed, dimensions, and we never overshoot. For photographic content a cap that tight usually means the honest answer is switching format. The tool will tell you rather than deliver mush.
- Can I compress the same PNG twice?
- You can, but a second pass through quantization compounds palette reduction. It usually saves little and can band gradients. Better: keep your original and compress once per destination. If a re-run would grow the file, our never-larger guard returns your original untouched.
- Why did my PNG get BIGGER after optimising elsewhere?
- Common causes: a tool that re-encoded truecolour with heavier filtering, added metadata, or "optimised" an already-quantized file back to 24-bit. With us, same-format compression that would grow the file returns your original bytes untouched and says so.
- Should this image even be a PNG?
- Screenshots, UI, logos, anything transparent: yes. Photographs: almost never. The same photo measured 189.8 KB as optimised PNG but 69.8 KB as AVIF. If your PNG is a photo, converting beats compressing by an order of magnitude.
- Can I compress many PNGs at once?
- Yes, up to 50 per batch at 30 MB each. You get one ZIP with filenames preserved, free, with no signup and a 300-image daily allowance. Each row shows its measured before/after size, so a screenshot-heavy docs folder shows exactly where the bytes went.
- What happens to my files?
- We keep nothing. We process your files, then wipe them automatically. We never archive them or use them for anything else. We strip metadata from outputs by default, and you need no account.