You've got a strict 100KB upload limit — a form field, a marketplace listing, a CMS asset rule, a game asset budget — and your PNG is sitting at 400KB with no obvious way down. Dragging a quality slider doesn't even exist for PNG the way it does for JPEG, so the usual advice doesn't apply, and converting to JPEG wrecks your transparency or introduces fuzzy edges around text and icons.
PNG is a lossless format, which means it can't be "compressed" the same way a photo can. But that doesn't mean 100KB is out of reach. There's a specific, repeatable process for shrinking a PNG hard while keeping it sharp and fully transparent — and a much faster way to hit an exact number without any trial and error.
To get a PNG under 100KB, reduce the color palette to 256 colors or fewer, strip metadata, and run lossless PNG optimization first — this alone can cut 60–80% off flat-color images like logos and screenshots. If it's still too large, resize the pixel dimensions rather than switching formats. For a guaranteed result with no guesswork, an exact file size resizer will hit 100KB automatically.
What does "compressing" a PNG actually mean?
PNG is a lossless format — unlike JPEG, it never throws away pixel data to save space, which is exactly why it's the standard for logos, screenshots, icons, and anything with transparency or sharp edges. That also means there's no quality slider to turn down. Real PNG size reduction comes from three different levers, none of which touch image quality the way JPEG compression does:
- Color palette reduction. A standard PNG stores 24-bit color (16.7 million possible colors) plus an alpha channel. Many images — logos, illustrations, UI screenshots — only actually use a few hundred distinct colors. Converting to an 8-bit indexed palette (256 colors or fewer) can shrink the file dramatically with no visible change.
- Metadata and chunk stripping. PNGs often carry embedded color profiles, text chunks, and editor metadata that add nothing to how the image looks. Stripping this is pure savings with zero visual cost.
- Better lossless encoding. The PNG format allows different internal compression strategies (filter methods, deflate settings). Re-encoding with a more efficient optimizer — without changing a single pixel — routinely saves 20–50% over a default export.
If those three levers still don't get you under your target, the remaining option is to reduce pixel dimensions. This is the one genuinely "lossy" step in the process, but it's honest: a smaller image at full quality almost always looks better than the same large image forced into a tiny file size through aggressive re-encoding.
Why hitting 100KB matters
A 100KB limit is rarely arbitrary — it usually reflects a real constraint somewhere in the system that will reject, resize, or badly re-compress your file if you ignore it:
- Hard upload limits. Job application portals, marketplace listings, government forms, and some CMS platforms enforce a strict per-file cap and will simply reject anything over it — no partial credit for being close.
- Automatic re-compression. Some platforms don't reject oversized files; they silently re-compress them with their own algorithm, which often looks worse than if you'd controlled the compression yourself.
- Page and app performance. Every icon, logo, and UI graphic under 100KB adds up across a page or app bundle. Bloated PNGs are a common, avoidable source of slow load times.
- Email and messaging limits. Many chat and email clients compress or block attachments over certain sizes, and a controlled 100KB export avoids that lottery entirely.
Step-by-step: getting your PNG under 100KB
- Check what the image actually needs to look like. Does it need full 24-bit color and transparency, or is it mostly flat colors and text? This determines how aggressively you can reduce the palette before anything changes visually.
- Reduce the color palette first. Convert to an 8-bit indexed PNG (256 colors) if the image allows it — logos, icons, and simple illustrations usually tolerate this with zero visible difference. Photographic PNGs may need to stay closer to full color.
- Strip unnecessary metadata. Remove embedded color profiles, text chunks, and editor-added metadata. This is free savings that never affects how the image looks.
- Run a lossless PNG optimizer. A dedicated optimizer re-encodes the file with better internal compression settings without touching a single pixel — this step alone often saves 20–50%.
- Check the file size against your 100KB target. If you're under, you're done. If you're still over, move to resizing rather than degrading the palette further.
- Resize the pixel dimensions if needed. Scale down to the actual display size the image will be used at — a 2000px image compressed to fit 100KB looks worse than the same image resized to 800px first, since resizing removes data that was never going to be visible anyway.
- Use a tool that targets an exact file size. Rather than repeating steps 2–6 by trial and error, an exact file size resizer takes your 100KB target directly and iterates automatically until the output matches it.
Common mistakes that keep files too big
1. Converting to JPEG to force the size down
JPEG has no transparency support and introduces soft, blurry edges around text and sharp boundaries — exactly the content PNG is usually chosen for. Converting formats to hit a size target almost always looks worse than properly optimizing the PNG itself.
2. Resizing dimensions before reducing the palette
Shrinking pixel dimensions first throws away resolution you might not have needed to lose. Palette reduction and metadata stripping are genuinely free wins — they cost nothing visually — so they should always happen before you touch the image's actual dimensions.
3. Assuming all PNGs compress the same way
A flat-color logo and a detailed screenshot with gradients behave very differently under palette reduction. The logo might drop to 256 colors invisibly; the screenshot might show banding. Judge the result visually per image, not by a rule of thumb.
4. Re-exporting from an already-compressed PNG repeatedly
Because PNG is lossless, this specific risk is smaller than with JPEG — but repeatedly re-indexing a palette-reduced image or resizing an already-resized file can still degrade results. Keep a full-quality master and re-export from that each time you need a new target size.
Real-world size reduction examples
These are representative results from optimizing typical PNG files using palette reduction, metadata stripping, and lossless re-encoding:
The pattern holds across most graphics: flat-color images like logos and icons compress the most dramatically, while detailed illustrations and gradient-heavy screenshots may need a small dimension reduction alongside palette optimization to comfortably clear a 100KB target.
Compression method by image type
Different PNG content responds very differently to each compression lever — here's which method to reach for first based on what you're compressing.
| Image type | Best first method | Typical savings | Quality risk | Notes |
|---|---|---|---|---|
| Logos / icons | Palette reduction (256 colors) | 70–85% | Very low | Flat colors survive indexing with no visible change |
| UI screenshots | Palette reduction + metadata strip | 60–80% | Low | Text stays sharp since PNG never blurs edges |
| Transparent icons / stickers | Palette reduction (alpha-safe) | 65–85% | Very low | Alpha channel preserved through indexing |
| Illustrations with gradients | Lossless re-encode, light palette reduction | 40–60% | Low-medium | Watch for banding if palette drops too far |
| Detailed / photographic PNGs | Resize dimensions + re-encode | 30–55% | Medium | Consider whether JPEG or WebP fits better here |
| Need an exact size (e.g. 100KB) | Exact file size resizer | Target-guaranteed | Low | Automatically balances palette + dimensions for you |
Get your PNG under 100KB right now — free
The Rebrixe PNG Compressor runs entirely in your browser, reducing palette size and stripping metadata without ever uploading your file to a server. If you need to land on an exact number — like a strict 100KB cap — the Exact File Size Resizer takes your target directly and iterates automatically until the output matches it.