Reduce PNG size with a real palette control, watch the savings on a live readout, and check the result on a before/after slider. Queue up to 50 files, keep the alpha channel intact, and grab one ZIP. Free, no signup.
Drop PNGs to make them lighter
PNG only · up to 50 files · 100 MB each
Drag the divider across the photo. Both sides are the same 1:1 crop: one from the original file, one from the file this tool made from it.
Drag files onto the box or tap to browse. The dropzone takes .png only, so a stray JPEG can't slip into the batch and come out re-encoded by mistake.
Start with no reduction for a clean lossless pass. If you need more, lower the palette and watch the projected size and the compare view update together until the trade looks fair.
A single PNG downloads on its own; a queue arrives zipped. Your source files never change on disk — the tool writes fresh copies alongside them.
Set the target color count and the stats bar reports the new size and percent saved before you download. Leave it at no reduction for a pure lossless pass, or dial the palette down when a graphic can spare the colors.
The alpha channel survives every step, including semi-transparent pixels and feathered edges. A logo or icon comes out with the same clean cutout it went in with — no white box, no hard matte.
Load up to 50 files at 100 MB each, apply a single palette setting across the batch, and collect the whole optimized set as one download. Per-item progress shows exactly where the queue stands.
A brand mark placed on sites and slide decks has to keep its cutout on any background. Trim the palette of a flat logo and the file drops sharply while the transparent edge stays clean.
Icons and sprite sheets bundled into an app build add up fast across a set. Quantizing each one keeps the interface crisp and shaves real weight off what ships to the device.
Product and documentation screenshots saved as PNG bloat a knowledge base and slow its pages. A lossless re-encode plus a metadata strip lightens them without softening the text.
Sprite sheets and stickers live or die on clean alpha edges. Reducing colors on flat cel art holds those edges while cutting the download that players and chat apps have to pull.
A transparent hero PNG sitting at the top of a page is often the single heaviest asset on it. Compressing the graphic pulls it off the critical render path and lets the fold paint sooner.
Design tools export PNGs at generous bit depth by default. Running those exports through a palette pass before handoff keeps the visual and hands developers a far smaller file.
A PNG stores every pixel exactly, with no detail thrown away, which is what people mean when they call the format lossless. That fidelity is also why the files run large: a full-color PNG-24 reserves 24 bits of color for every pixel whether the artwork needs that range or not, and a PNG-32 adds an 8-bit alpha channel on top for transparency. Screenshots, exported renders, and anything with soft gradients pile on the bytes fastest. The format never discards data on its own, so a heavy PNG stays heavy until you change what it has to describe.
There are two honest ways to make one smaller. The first is a tighter lossless re-encode — the compressor runs a maximum zlib pass and strips embedded metadata, giving back a few kilobytes with zero visible change. The second, and the bigger lever, is reducing the color count: quantizing a PNG-24 down to a limited palette can cut the size dramatically, and the alpha channel is carried through the whole operation, semi-transparent edges included. That step is opt-in and one-way, so you decide when a graphic can spare the colors.
This tool puts that choice in front of you instead of hiding it behind one button. A Colors control sets the target palette, a stats bar reports the new size and percent saved as you adjust, and the compare slider sweeps between the original and the compressed copy on the same graphic. When a PNG is really a photograph in disguise, palette reduction will band the gradients — so the copy points you toward WebP or JPG for those, rather than pretending a flat palette suits every image.
Reach for the color count first — it is the biggest lever by far. A flat graphic that looks identical at 64 colors can weigh a fraction of its 24-bit original, while a lossless-only pass barely moves the needle on the same file.
Know what you started with. A PNG-8 is already palettized, so there is little left to squeeze; a PNG-24 or PNG-32 is where color reduction actually pays. The stats bar shows the honest delta either way.
Match the format to the content. Flat graphics, line art, and text stay razor-sharp as PNG; a photograph or a rich gradient will band under a small palette and belongs in WebP or JPG instead.
Keep a master copy before you quantize. Dropping colors is a one-way trip — you cannot rebuild the discarded shades later, so archive the full-depth original and reduce a duplicate.
Turn on the metadata strip for a few free kilobytes. Color profiles, capture timestamps, and editing history ride along invisibly in many PNGs and add nothing to how the image looks.
The file itself, yes — the zlib pass and metadata strip discard nothing, so the image is bit-for-bit identical, only smaller. Color reduction is a separate step and it is lossy by nature, because quantizing to fewer colors permanently drops the shades in between. It is entirely optional and stays off until you choose it.
Run it through the lossless pass alone: strip the metadata and re-encode at maximum compression, leaving the color count untouched. Every pixel and the full alpha channel survive intact. If that is not enough, lowering the palette is the next lever, at the cost of some color range you control.
No. The alpha channel is preserved end to end, and that includes partial transparency — feathered shadows, anti-aliased edges, and glass-like fades all come through as they were. Even when you reduce the color count, the transparency plane is quantized alongside the colors, not flattened onto a background.
PNG-8 uses an indexed palette of up to 256 colors, which keeps flat graphics and icons tiny. PNG-24 stores full 24-bit color — millions of shades — which is why photographs and gradients look right but weigh far more, and a PNG-32 is a PNG-24 with an added alpha channel for transparency. Reducing colors is essentially converting a heavy PNG-24 toward a lean PNG-8.
Usually because they hold full 24-bit color for content that does not need it, or because a photograph was saved as PNG. The format keeps every pixel exactly, so a busy or high-resolution image has nowhere to hide its bytes. Trimming the palette, or moving photographic content to a lossy format, is what brings the size down.
For flat graphics, logos, and screenshots, an optimized PNG is compact and universally supported, so stay put. For photographs and rich gradients, WebP is typically much smaller at the same visual quality and keeps transparency too — convert those with AnyResizer's PNG to WebP tool.
This page works the other way around: you set the palette and it reports the resulting size. When a form or upload field demands a hard ceiling like 200 KB, use AnyResizer's Resize image to KB tool, which tunes the settings automatically until the output lands under the number you name.
No. Everything runs in your own browser through ImageMagick compiled to WebAssembly, so once the page has loaded the compression works even with the network turned off. Your files are never sent, stored, or logged anywhere.
The all-format hub — JPEG, WebP, AVIF, GIF, and BMP alongside PNG.
Convert photographic PNGs to WebP for a bigger cut, transparency kept.
Move between PNG, JPG, WebP, and AVIF in a single editor.
Name a hard size ceiling and let it auto-tune to land under it.
Quality-slider compression built for photos and JPG exports.
Drop up to fifty, set a palette, and keep every transparent pixel on the way to a lighter file.
