How much smaller is WebP than PNG?

It depends entirely on content. Our photographic PNG dropped from 1382.4 KB to 110.4 KB (−92%). A big UI screenshot went from 2683.7 KB to 83.8 KB. The famous "26% smaller" figure describes lossless WebP on graphics. Photos save far more via lossy.

Does PNG to WebP keep transparency?

Yes, fully. WebP carries the same alpha channel PNG does, in both lossy and lossless modes. Your logos and cutouts convert with soft shadows and anti-aliased edges intact. Verify any edge against the checkerboard in the compare view. Fringing means a tool flattened the alpha. Ours doesn't.

Should I use lossy or lossless WebP?

Use lossy for photographs and screenshots: huge savings, invisible cost at Auto quality. Use lossless for flat art where every pixel is deliberate. Our Auto setting reads the image and errs on the safe side. The compare slider exists so you can overrule it with evidence.

Does converting PNG to WebP lose quality?

Lossy WebP trades exactness for bytes, tuned to be invisible at normal viewing. The source PNG's pixels are the baseline, so nothing compounds from earlier compression. Check text edges and gradients at 100% in the slider. Those show loss first if any is visible.

Do all browsers support WebP in 2026?

About 97% do. Safari has supported it since 14 (2020), Chrome and Firefox for a decade, Edge likewise. WordPress has served it natively since 5.8, and Shopify's CDN handles it automatically. WebP is no longer the risky choice. It is the default the web already runs on.

Will converting improve my PageSpeed and LCP?

If heavy PNGs sit in your critical path, dramatically. A hero that was a 1382.4 KB PNG loads as a 110.4 KB WebP. On 4G, that is the difference between a visible wait and an instant paint. Convert the LCP image first, then measure with PageSpeed before and after.

How do I bulk convert PNGs for a site migration?

Drop up to 50 PNGs and download one ZIP. Filenames are preserved so references keep matching, and each row shows the measured saving so you can prove the migration's value. Repeat per folder within the 300-image daily allowance. Ongoing automation is what the API and CMS plugins are for.

Can I keep the WebP under a size limit?

Yes. Set Max file size and the engine guarantees the output lands under it, quality-searched and never overshot. "PNG to WebP under 100 KB" is a real workflow for marketplace and CMS upload limits. No other converter in this SERP can promise the number.

What about animated PNGs (APNG)?

We decline animated inputs with a clear message rather than silently flattening them to one frame. For animation, animated WebP encoded from the original frames is excellent. But converting a flattened still and calling it done would be lying about what survived.

WebP or AVIF for my PNGs?

AVIF is smaller still. The same photographic PNG measured 110.4 KB as WebP and 69.8 KB as AVIF. Serve AVIF, then WebP, in a picture element for the best of both. Convert to WebP alone when a platform hasn't caught up to AVIF yet.

What happens to my files?

We keep nothing. We process your files and wipe them automatically, never archive them, never use them for anything else. We strip metadata by default. There is no account required, no watermark, and a 300-image daily allowance.

blinkimg

Convert PNG to WebP

Convert PNG images to WebP in your browser. WebP keeps your transparency and is usually smaller than the original PNG, whether it's a logo, screenshot, or photo.

– / –

Drop images or browse

JPEG · PNG · WEBP · AVIF · HEIC · max 30 MB

HEIC

PNG

JPEG

AVIF

WEBP

Advanced settings1 on

QualityAuto

SmallerAutoBetter

Auto tunes each image.

Max file size

A hard cap for “under 50 KB” portals.

Max resolution

Empty side keeps the ratio. Never enlarges.

Keep EXIF metadataOff by default. We strip camera and GPS data.

One real file, before and after

PNG, 1.3 MB — A real result from this exact operation: 1.3 MB in, 108 KB out. Drop your own file and the meter reports yours. The left half is a preview render; the byte counts are the real files’.

WebP, 108 KB — A real result from this exact operation: 1.3 MB in, 108 KB out. Drop your own file and the meter reports yours. The left half is a preview render; the byte counts are the real files’.

Measured by content type, because PNGs differ wildly

Source	PNG	WebP	Saved	AVIF (next rung)
Photograph	1382.4 KB	110.4 KB	−92%	69.8 KB
UI screenshot	2683.7 KB	83.8 KB	−97%	n/a
Flat-colour graphic	7.4 KB	1.3 KB	−82%	0.8 KB

Auto quality. The photograph is the headline case. Screenshots are the everyday one. Flat art starts small and still halves.

How these numbers are measured: every byte count on this page is the size of the actual encoded file our engine produced from the named source image. Those are the same bytes you would download, not an estimate or a best case. Rerun any of them yourself: drop your own file into the tool above and the meter reports your real result.

Transparency survives: here's the proof protocol

WebP speaks PNG's alpha language in both its lossy and lossless modes. Your transparency converts intact: hard edges, feathered anti-aliasing, semi-transparent drop shadows. Don't take that as a slogan. The compare view renders your image over a checkerboard precisely so you can drag the wipe across a logo edge and look for fringing or halos. Finding none is the point. (If a downstream tool later shows white corners, that tool flattened the alpha. The file we produced still carries it.)

The Core Web Vitals case, with real numbers

Google's LCP threshold is 2.5 seconds. On a throttled 4G connection, every 100 KB of hero image costs roughly a quarter second. A 1382.4 KB photographic PNG in your critical path is an LCP bug wearing a file extension. The 110.4 KB WebP version of the same image is not. Migrate in the order that pays: the LCP element first, above-the-fold imagery second, gallery grids third. Thumbnails usually never, because their absolute savings are noise. The per-row measured savings in the tool are your triage list.

Screenshots: the everyday win nobody calculates

Docs sites, help centres and READMEs are screenshot warehouses, and screenshots are PNG's home turf. Then they meet WebP. Our 2683.7 KB reference screenshot became 83.8 KB, with UI text still knife-sharp. Verify at 100%: text is where lossy shows first. A docs folder of fifty screenshots is one batch here, one ZIP back, and a support site that loads like it should.

When to keep the PNG

Design masters and archival sources? PNG's lossless guarantee is the point there. Convert the shipping copies, keep the source.
Pixel-art and 1px-line UI specs? Where individual pixels are data, verify lossy WebP at 100% first, or stay lossless.
A platform that rejects WebP? A shrinking list, but real. Compress the PNG instead: palette quantization still shrinks it dramatically.

Staying in PNG? Use Compress PNG. Going further? Try PNG to AVIF.

Questions, answered

Short answers specific to this page. The tool above settles most of them in a second.

How much smaller is WebP than PNG?: It depends entirely on content. Our photographic PNG dropped from 1382.4 KB to 110.4 KB (−92%). A big UI screenshot went from 2683.7 KB to 83.8 KB. The famous "26% smaller" figure describes lossless WebP on graphics. Photos save far more via lossy.
Does PNG to WebP keep transparency?: Yes, fully. WebP carries the same alpha channel PNG does, in both lossy and lossless modes. Your logos and cutouts convert with soft shadows and anti-aliased edges intact. Verify any edge against the checkerboard in the compare view. Fringing means a tool flattened the alpha. Ours doesn't.
Should I use lossy or lossless WebP?: Use lossy for photographs and screenshots: huge savings, invisible cost at Auto quality. Use lossless for flat art where every pixel is deliberate. Our Auto setting reads the image and errs on the safe side. The compare slider exists so you can overrule it with evidence.
Does converting PNG to WebP lose quality?: Lossy WebP trades exactness for bytes, tuned to be invisible at normal viewing. The source PNG's pixels are the baseline, so nothing compounds from earlier compression. Check text edges and gradients at 100% in the slider. Those show loss first if any is visible.
Do all browsers support WebP in 2026?: About 97% do. Safari has supported it since 14 (2020), Chrome and Firefox for a decade, Edge likewise. WordPress has served it natively since 5.8, and Shopify's CDN handles it automatically. WebP is no longer the risky choice. It is the default the web already runs on.
Will converting improve my PageSpeed and LCP?: If heavy PNGs sit in your critical path, dramatically. A hero that was a 1382.4 KB PNG loads as a 110.4 KB WebP. On 4G, that is the difference between a visible wait and an instant paint. Convert the LCP image first, then measure with PageSpeed before and after.
How do I bulk convert PNGs for a site migration?: Drop up to 50 PNGs and download one ZIP. Filenames are preserved so references keep matching, and each row shows the measured saving so you can prove the migration's value. Repeat per folder within the 300-image daily allowance. Ongoing automation is what the API and CMS plugins are for.
Can I keep the WebP under a size limit?: Yes. Set Max file size and the engine guarantees the output lands under it, quality-searched and never overshot. "PNG to WebP under 100 KB" is a real workflow for marketplace and CMS upload limits. No other converter in this SERP can promise the number.
What about animated PNGs (APNG)?: We decline animated inputs with a clear message rather than silently flattening them to one frame. For animation, animated WebP encoded from the original frames is excellent. But converting a flattened still and calling it done would be lying about what survived.
WebP or AVIF for my PNGs?: AVIF is smaller still. The same photographic PNG measured 110.4 KB as WebP and 69.8 KB as AVIF. Serve AVIF, then WebP, in a picture element for the best of both. Convert to WebP alone when a platform hasn't caught up to AVIF yet.
What happens to my files?: We keep nothing. We process your files and wipe them automatically, never archive them, never use them for anything else. We strip metadata by default. There is no account required, no watermark, and a 300-image daily allowance.

Related conversions

Every route in and out runs on the same engine and the same rules. Each card is its own page.

Ready when your file is

Drop it in above. The meter reports the exact saving before you download anything.

Compress now