Skip to content

image guide

How to Convert PNG to WebP — Reduce File Size Without Visible Quality Loss

WebP gives you the same visual quality as PNG at 26-80% smaller file size — depending on whether you choose lossless or lossy mode. For websites, this directly translates to faster loads and better Core Web Vitals scores. This guide explains exactly how to convert and which settings give the best result.

Updated September 22, 2026 · 21 questions answered

Key takeaways

  • Lossless WebP beats PNG on size with identical pixels: typically 20-30% smaller.
  • Lossy WebP at quality 80 cuts photographic PNGs by 60-85% with no visible difference.
  • Transparency requires lossless mode — lossy WebP has no alpha channel at all.
  • Rule of thumb: text, UI and logos go lossless; photographs go lossy at quality 80.
  • Serve WebP inside a <picture> element with a PNG fallback and even old browsers never break.

Why Convert PNG to WebP?

PNG's lossless compression is excellent for graphics with flat colours but terrible for photographic content. A 12-megapixel camera photo saved as PNG is typically 15-25 MB — absurd for a web image. The same image as lossy WebP at quality 80 is 400-800 KB and visually identical.

Even for graphics: PNG → lossless WebP gives you identical pixel-perfect output at 20-30% smaller. If you host 500 images on a product page, switching from PNG to WebP saves roughly 30% of total bandwidth with zero visual change.

For SEO: Google's Core Web Vitals use Largest Contentful Paint (LCP). Your hero image is usually the LCP element. Converting it from 3 MB PNG to 600 KB WebP cuts LCP by over a second on average connections.

Lossy vs Lossless PNG → WebP Conversion

Lossless mode: every pixel in the WebP matches the PNG exactly. Alpha channel is preserved. Reduction: 20-30% on any image type. Zero quality loss. Use for: logos, icons, screenshots, graphics with text.

Lossy mode: perceptually identical but mathematically different pixels. Alpha is not supported in lossy mode. Reduction: 60-85% on photographic content. Use quality 80-85 for near-invisible loss. Use for: photographs, hero images, product shots.

Decision rule: if the image has sharp text edges or transparency → lossless. If it is photographic → lossy at quality 80.

Best Converters Compared

Collabs Tool (browser-based, free, batch 20 files): quality slider, side-by-side preview, preserves transparency, no upload. Best for privacy-conscious users and medium batches.

Squoosh (Google's open-source browser tool): single file, shows before/after with slider, lets you choose WebP vs AVIF vs JPEG. Excellent for comparing options on one file.

CloudConvert (server-based, supports 200+ formats): good for formats beyond WebP. Requires upload — a privacy consideration. Free tier: 25 operations per day.

ImageMagick (desktop, command-line): unlimited batch, scriptable, best for developers and large migrations. magick input.png -quality 80 output.webp.

Keeping Transparency

If your PNG has an alpha channel, converting to lossless WebP preserves it perfectly. The resulting WebP looks identical on any background.

If you convert a transparent PNG to lossy WebP, the alpha is destroyed: the transparent area becomes a solid-colour background (usually white, sometimes black, depending on the converter). Most tools warn you — some silently flatten.

For the smallest transparent WebP: lossless mode with a good encoder (the libwebp default) already beats PNG-32 by 20-30%.

Settings Cheat Sheet

Photographic image → WebP lossy, quality 80, no alpha. Expect 70-80% size reduction.

Logo/icon with transparency → WebP lossless. Expect 20-30% reduction, alpha preserved.

Screenshot (text + UI) → WebP lossless. Expect 25-35% reduction.

Large hero image for website → WebP lossy, quality 75. Accept slight softening for maximum speed.

Archival (no quality loss, but smaller than PNG) → WebP lossless. Always safe.

Frequently asked questions

The questions people ask most about png to webp: reduce file size by 30-80% (free converter), answered directly.

How do I convert PNG to WebP?

Drag and drop your PNG onto a browser-based converter like Collabs Tool, choose quality (80 for photos, lossless for graphics), and download the WebP result. Takes one second per file, no upload needed.

Does PNG to WebP reduce quality?

Lossless mode: no — identical pixels, just smaller file. Lossy mode at quality 80+: imperceptible visual difference. Lossy at quality below 65: visible artefacts. The reduction in file size is what you trade for the tiny lossy-mode quality difference.

How much smaller is WebP than PNG?

Lossless WebP is typically 26% smaller than PNG for any image. Lossy WebP at quality 80 is 60-80% smaller than PNG for photographic content. The exact reduction depends on image complexity.

Can I convert PNG to WebP without losing transparency?

Yes — use lossless WebP mode. It preserves the alpha channel perfectly. Lossy WebP mode does NOT support transparency, so always choose lossless for images with alpha.

Is WebP better than PNG for websites?

Yes for file size. A well-optimised WebP loads faster than the equivalent PNG, directly improving Core Web Vitals and user experience. However, PNG remains better for email, universal compatibility, and design-workflow round-tripping.

Can I convert multiple PNGs to WebP at once?

Yes. Collabs Tool accepts up to 20 files in batch mode: set quality once, convert all, download individually. For hundreds of files, ImageMagick handles batch in a single command.

What quality should I use for PNG to WebP?

For photographic images: quality 80 (lossy) — near-identical visual quality at 70% smaller. For graphics/screenshots: lossless — identical quality at 25% smaller. Below quality 70, visible artefacts appear.

Does Google support WebP?

Fully. Chrome, Google Search indexing, Google Images, Gmail (browser), YouTube thumbnails, and Google Ads all use WebP extensively. Google created the format.

Can I use WebP in email?

Not reliably. Outlook desktop (Windows) does not render WebP. Gmail web does. For email-embedded images, stick with PNG or JPEG. WebP is for web pages, not email bodies.

How do I convert PNG to WebP in Photoshop?

File → Export As → choose WebP format → set quality → Export. Photoshop 2020+ supports WebP export natively. For batch: use Actions with a WebP export step.

Should I use WebP or AVIF?

WebP: universal browser support (98%+), fast encoding, good compression. AVIF: 20% smaller but slower encoding and 82% browser support. Use AVIF with WebP fallback for best results.

Does WebP support animation?

Yes. Animated WebP is 60-70% smaller than equivalent GIF with better colour depth. However, it is less universally supported than GIF and less common than APNG or video formats.

How do I serve WebP on a website with a fallback?

Use the HTML <picture> element: a <source type="image/webp"> pointing at the WebP plus an <img> fallback carrying the original PNG. Browsers that understand WebP take the source, older ones load the img — the file-size win with zero compatibility risk, and the pattern Google recommends.

Does WordPress support WebP?

Yes — the media library accepts WebP uploads since version 5.5 (2020). Most optimisation plugins (Smush, ShortPixel, EWWW) additionally generate and serve WebP versions of existing PNGs and JPGs automatically, with the fallback handled for you.

Do WebP images help SEO?

Indirectly but measurably: smaller files download faster, which improves Largest Contentful Paint — a Core Web Vitals ranking input — and reduces bounce behaviour. The gain comes from the speed, not the file extension. Google, which created WebP, has confirmed images should be compressed; WebP is simply how to compress them further.

Does Safari support WebP?

Yes — Safari 14 (late 2020) onward renders WebP on both macOS and iOS. Global coverage sits above 95% of browser usage. Older Safari versions and some embedded webviews are the reason the <picture> fallback still matters for maximum reach.

Should I convert screenshots to WebP?

Yes, in lossless mode. Screenshots are flat colours, sharp text edges and UI chrome — precisely what lossless WebP compresses 25-35% better than PNG while keeping byte-identical pixels. Never use lossy mode for screenshots: it smudges text anti-aliasing.

Is lossless WebP truly identical to the PNG?

Yes. It re-encodes the same pixels with a different algorithm (spatial prediction plus entropy coding instead of PNG filtering plus DEFLATE). Decoding returns exactly the original RGB and alpha values. Verify it yourself: convert, convert back, pixel-diff — a perfect match.

How much page-speed improvement can WebP give?

Roughly 30% fewer image bytes is a realistic average across a mixed page. On a 3 MB PNG hero image, lossy WebP at quality 80 typically lands near 600 KB — often a second or more off first paint on mobile connections, which is exactly the measurement Core Web Vitals is grading.

Can I convert a transparent PNG to WebP safely?

Yes — choose lossless mode and the alpha channel carries over untouched. The trap is lossy mode: lossy WebP has no alpha at all, so the converter flattens your transparent background onto a solid colour, usually white, and the transparency is gone for good.

Does converting to WebP improve image quality?

No — conversion cannot add detail the PNG never contained. Well-configured WebP keeps the same visual information in fewer bytes. Anyone reporting a quality 'improvement' is seeing the removal of PNG bloat or a re-save, not better pixels.