100% Free In-browser Transparency preserved

Compress PNG Images Free

Reduce PNG file size while preserving transparency. Choose PNG (lossless) or WebP (smaller). All processing happens in your browser — your images never leave your device.

Drop PNG images here or click to browse

PNG • Transparency supported • Batch compress supported

Accepts: .PNG
Output: .PNG or .WEBP
75%
px
Lower quality = smaller file size. 75% is recommended for most photos.
Never uploaded·How to use this tool
0 files

Compress PNG images in 3 steps

1

Upload your PNG

Drop your .png files onto the tool. Transparent PNGs are fully supported. Add multiple files for batch processing.

2

Choose output format

Keep as PNG for maximum compatibility, or choose WebP for even smaller file sizes while preserving transparency.

3

Download compressed

Download your compressed PNG or WebP files individually or all at once as a ZIP archive.

PNG compression that keeps transparency

Color quantization via UPNG — the same approach as pngquant. Alpha channel is preserved throughout. Palette steps from 256 to 32 colors find the right balance for every image.

100% Private
Files never uploaded
Always Free
No account needed
Instant Results
No upload wait time
No Limits
Batch process freely
Feature JustDownSize Others
Price Always free Paid plans
File uploads Never uploaded Sent to server
Daily limit Unlimited 5–20/day free
Account needed No signup Registration
Watermarks None, ever On free tier

PNG Compression That Keeps Transparency Intact

Transparency Preserved

PNG compression uses UPNG color quantization — the same approach as pngquant. Alpha channel data is preserved throughout, so transparency stays perfectly intact.

Color Quantization Engine

Rather than lossy quality reduction, PNG compression works by reducing the color palette. 256 colors at high quality, stepping down to 128, 64, or 32 at lower settings — often with no visible difference on screen.

Browser-Only Processing

No uploads. PNGs process entirely in-browser via UPNG.js. Your logos, UI assets, and screenshots never touch a server.

Batch PNG Compression

Process entire icon sets or screenshot batches in one session. Download all compressed PNGs as a ZIP when done.

Multi-Step Fallback

If quantization at your chosen level doesn't beat the original size, the tool tries progressively lower palette settings until it finds a smaller output — or returns the original unchanged.

PNG-to-PNG Output

Input is PNG, output is PNG. No forced conversion to JPEG that would strip transparency. The format stays intact.

When PNG Compression Is the Right Choice

Web UI Assets and Icons

Interface elements, logos, and icon sets are usually PNG to preserve crisp edges and transparency. Color quantization reduces a 500KB icon to under 80KB with no visible quality loss at screen resolution.

App Screenshots for the App Store and Google Play

App store listings require screenshots under specific file size limits. PNG screenshots from simulators often run 1–3MB — compression brings them into range without JPEG artifacts on text and UI elements.

Game Sprites and Texture Atlases

Sprite sheets for games are almost always PNG for alpha support. Quantizing a 2MB sprite sheet to a 64-color palette can cut it to 200KB, which matters for mobile game download size.

Documentation and Tutorial Screenshots

Technical documentation screenshots with UI elements compress better as PNG than JPEG. Color quantization preserves text readability while reducing storage footprint across large documentation sites.

Frequently asked questions

Yes. When the output format is PNG, full transparency (alpha channel) is preserved exactly. When you choose WebP as the output, transparency is also fully supported — WebP is one of the few formats that supports both lossy compression and alpha transparency simultaneously, often producing smaller files than PNG.

PNG uses lossless compression — every pixel is stored exactly. The quality slider has no effect on PNG output because lossless means no quality trade-off. WebP uses lossy compression controlled by the quality slider, which can produce files 25–50% smaller than PNG for the same perceived visual quality. Both formats support transparency. WebP is supported by all modern browsers.

No. All processing happens entirely in your browser using the HTML5 Canvas API. Your images never leave your device. This means instant results, complete privacy, and no file size restrictions from server-side limits.

PNG is already a losslessly compressed format. The browser's PNG encoder may not achieve the same compression ratios as dedicated tools like pngcrush or oxipng, which use more aggressive lossless algorithms. For much smaller file sizes, try switching the output to WebP — this will apply lossy compression and often reduces PNG files by 50–70%.

Yes. Select multiple PNG files at once or drag and drop a batch. All files are compressed with the same settings. When all files are done, a Download All (ZIP) button appears so you can grab everything in one click.

Compress PNG File Size Online — Why the Quality Slider Works Differently

PNG is a lossless format. That single fact changes everything about how compression works compared to JPEG. There's no quality factor in the JPEG sense — no way to say "discard 30% of the detail and make the file smaller." What you can do is reduce the number of colors stored in the file. That's what the quality slider actually controls here, and it's the same technique that makes pngquant and TinyPNG effective.

Color quantization: what's actually happening

PNG files can store up to 16 million colors (24-bit RGB) or over 4 billion with an alpha channel (32-bit RGBA). Most real-world PNG images don't actually use anywhere near that many distinct colors, but they're encoded as if they might. Color quantization analyzes the actual colors in your image and reduces the palette to a smaller set — 256, 128, 64, or 32 colors — by replacing each pixel's exact color with the closest available color in the reduced palette.

The quality slider maps to palette size: 95%+ keeps the full lossless encoding (no quantization, just better deflate compression), 80%+ uses 256 colors, 60%+ drops to 128, 40%+ uses 64, and anything below 40% uses a 32-color palette. A photographic PNG at 128 colors will show subtle banding in smooth gradients if you look closely. A logo or icon with flat colors looks nearly identical at 32 colors as it does at full color — which is why quantization works so well for that type of content.

The tool uses UPNG.js for this process, which runs entirely client-side in your browser. UPNG.js implements the same quantization algorithm that pngquant uses — median-cut color space partitioning — so results are comparable to what you'd get from command-line pngquant without installing anything. Transparency is preserved fully through the quantization process: the alpha channel is part of the RGBA data that gets quantized, so semi-transparent edges stay semi-transparent.

When PNG compression isn't enough and you should switch to WebP

Quantization has a ceiling. A complex photograph stored as PNG at 256 colors will still be much larger than the same photo stored as a WebP at 80% quality, because WebP uses lossy VP8 encoding that achieves compression ratios PNG fundamentally can't match. If you're compressing a PNG and the output is still above 500KB, switching the output format to WebP will typically cut that in half or better. The WebP option on this tool preserves transparency, so you can convert a transparent PNG logo to WebP without losing the alpha channel.

The tradeoff is compatibility. WebP is supported by all modern browsers — Chrome, Firefox, Safari 14+, Edge — but older desktop applications, some email clients, and certain CMS platforms may not handle it. For anything going on a modern website, WebP is the better choice. For anything going into a Word document, Slack, or legacy software, stay with PNG.

The size-check fallback and when files don't get smaller

After quantization, the tool checks whether the output is actually smaller than your input. If it isn't — which can happen with small PNGs, already-optimized files, or images with very few colors — it steps down through smaller palette sizes (64, 32, 16 colors) until it finds one that beats the original. As a last resort it runs a lossless UPNG deflate pass and then falls back to the browser's native PNG encoder. If none of these produce a smaller file, it returns your original. You won't download a PNG that got bigger.

Files are processed entirely in-browser. Nothing is uploaded. For converting PNG to other formats, see Convert to PNG or the general image compressor for multi-format batch jobs. The background remover is useful if you need a transparent PNG before compressing.

What to look for when reviewing compressed PNG output

Check gradients first — any area where color transitions smoothly from one shade to another is where quantization artifacts appear most. A blue-to-purple gradient in a background might develop visible banding at 32 or 64 colors. Flat-color areas are fine at any palette size. If you're compressing a PNG icon or logo, you can often go as low as 32 colors without a visible difference. If you're compressing a photograph stored as PNG, 256 colors is the minimum worth considering — and for photos specifically, converting to WebP or JPEG will usually give you a better file size at equivalent visual quality than any quantization setting can achieve. The preview updates in real time, so compare input and output sizes and zoom in before committing to a download.