Sukat · PNG · 100 KB

Compress a PNG to an exact 100 KB

PNG is a lossless format — there’s no quality dial to drop, so the only real way to make a PNG smaller is to reduce the number of pixels. Sukat handles that automatically: set the target, pick PNG output, and the algorithm downscales until the encoded result fits under 100 KB.

Compress PNG to 100 KB now →
Last reviewed: May 2026

PNG is the right output for transparency, logos, screenshots, and crisp line art. For photographs, switch the output to JPEG or WebP — the visible quality difference at 100 KB is dramatic.

A 4 MB image reduced to fit under a 100 KB limit Animation: you set a 100 KB limit; the file size counts down through a binary search from 4 MB and lands at 98 KB, under the limit. YOUR LIMIT 100 KB ← the ceiling Sukat must stay under CURRENT FILE SIZE 4.0 MB 1.18 MB 412 KB 156 KB 98 KB binary search · ~7 re-encodes, highest quality that fits DONE98 KB — under your limit
How to

Compress a PNG to 100 KB

Three steps. The algorithm downscales until the encoded PNG fits.

Upload your PNG

Drop the file onto Sukat. Transparency is preserved through the conversion when output is PNG.

Set 100 KB and PNG output

Type 100 in Maximum File Size, select KB, and pick PNG. Optionally lower Target Width if the destination only needs a smaller pixel dimension.

Convert and download

Sukat downscales until the encoded PNG fits under 100 KB. The live preview shows the actual output dimensions first.

The trade-off

PNG vs JPEG at 100 KB

JPEG (and WebP) compresses by throwing away visual detail you can’t see. PNG doesn’t — it stores every pixel exactly. Same target file size, very different output:

JPEG / WEBP AT 100 KB

1500 px · quality ~80

A 1500-pixel photo stays 1500 px and looks visually clean.

PNG AT 100 KB

~500–700 px · lossless

The same photo is downscaled, but every remaining pixel is pixel-perfect.

So pick PNG when the format requirement is real — transparency, screenshots, logos, line art, app UI captures, charts. Pick JPEG or WebP when the input is a photo and the destination just wants something under 100 KB. Sukat handles all three formats; switch the output dropdown.

Use cases

When PNG at 100 KB is the right choice

Where lossless and transparency matter more than the highest pixel count at the cap.

  • Logos with transparency. For embedding on multi-coloured backgrounds without a halo.
  • App UI screenshots. For documentation, blog posts, and product tours.
  • Line art & illustrations. Where every edge needs to stay crisp.
  • Charts & data visualisations. With thin lines and small labels that must stay legible.
  • Game sprites & pixel art. Where pixel-perfect rendering is the design.
  • QR codes & barcodes. Where decoder accuracy depends on edge sharpness.
  • Small favicons. Though for actual favicons, use Sukat’s ICO output instead.
  • Editor-friendly intermediates. Round-tripping through PNG keeps quality intact between edits.
Why Sukat

Why Sukat for PNG-to-100-KB

The honest path through a constraint that doesn’t bend.

Honest about the trade-off

Most tools either silently re-encode as JPEG (losing transparency) or fail when the photo can’t fit. Sukat keeps the format you asked for and downscales to fit — and previews the actual output dimensions first.

Transparency preserved

Cropping, painting, and Remove Background all preserve PNG’s alpha channel through the workflow.

One-click switch to JPEG / WebP

If the input turns out to be a photo and PNG isn’t required, change the output dropdown — Sukat re-runs the same target-size search with a format that compresses photos efficiently.

Privacy

Compression runs in your browser via the Canvas API. Your PNGs never reach a server.

Questions

FAQ

Why is PNG compression different from JPG compression?

PNG is a lossless format with no quality dial — the encoder can’t trade visible quality for file size the way JPEG can. The only way to make a PNG smaller is to reduce the number of pixels, so Sukat compresses PNG by downscaling dimensions until the encoded result fits your target.

Should I really use PNG at 100 KB?

For photos, no — JPEG or WebP at 100 KB will look dramatically sharper at the same file size. Use PNG at 100 KB only when you specifically need transparency, lossless rendering, or crisp edges (logos, icons, screenshots, line art).

Does Sukat preserve PNG transparency?

Yes. When the input PNG has transparent regions and the output format is PNG, Sukat preserves the alpha channel through the conversion. Crop and Remove Background also preserve transparency.

What if my PNG is a screenshot or has flat colours?

PNG handles screenshots and flat-colour graphics very efficiently — much better than photos. A 1080p screenshot with a solid background often fits under 100 KB at full dimensions. Line art, app UI captures, and chart screenshots are PNG’s strong suit.

Can I convert my PNG photo to JPG instead?

Yes — and for photo content, this is usually the better choice. Set the output format to JPEG, set 100 KB, and Sukat encodes a JPG instead. The result will be far sharper than a 100 KB PNG of the same photo.

Are my PNGs uploaded to a server?

No. Compression runs entirely in your browser via the Canvas API. Your PNGs never reach a server. Verify by switching to airplane mode after the page loads.
Related tools

Keep going

Compress Image to 100KB — the general 100 KB target page (JPG/WebP friendly) Compress JPG to 100KB — same target, JPG-format-specific HEIC to PNG — convert iPhone HEIC to PNG with transparency Reduce Image Size in KB — pick any custom KB target Image Size Guide — full breakdown by platform and use case

Hit exactly 100 KB — transparency intact.

Free, browser-based, no upload, no watermark. Keeps PNG’s alpha channel; switch to JPEG or WebP in one click for photos.

Compress PNG to 100 KB now →