UtilityKit

500+ fast, free tools. Most run in your browser only; Image & PDF tools upload files to the backend when you run them.

PNG to WebP

Convert PNG images to WebP with full alpha preserved — typically 30-50% smaller. Browser-only, batch ZIP supported.

About PNG to WebP

PNG is the king of lossless image formats and the only universal way to ship images with transparency — but the file size cost is steep, especially for photo-heavy PNGs. WebP achieves 30-50% smaller files than PNG at visually identical quality, and crucially supports alpha transparency the same way PNG does. That makes WebP the modern replacement for PNG in every place that supports it (every modern browser since 2020). This converter re-encodes your PNGs to WebP using your browser's Canvas encoder, preserving the full alpha channel for transparent logos, icons, and screenshots with cutouts. Files never leave your device. Default quality 90 produces output indistinguishable from the source. Drop a single icon, a logo set, or hundreds of UI screenshots — output is bundled as a ZIP for batch downloads. No upload, no signup, no watermark.

Why use PNG to WebP

  • 30-50% smaller files than PNG at visually identical quality — the savings are even bigger than JPG-to-WebP because PNG is uncompressed for photographic content.
  • Full alpha transparency preserved — WebP supports the same per-pixel alpha channel as PNG, so transparent logos, icons, and cutout screenshots convert without losing the transparent regions.
  • 100% browser-local — your PNGs never leave your device during conversion. Confidential UI mockups, unreleased branding assets, and personal screenshots all stay private throughout.
  • Batch any number of PNGs at once — drop a folder of icons, screenshots, or logo variants and receive a ZIP of WebPs in a single operation, no per-file clicks needed.
  • Quality slider 20-100 with smart default of 90 — for icons and pixel art consider higher quality, for screenshots with text 85 is enough, for general web 90 strikes the right balance.
  • Modern browser support is universal — Chrome, Firefox, Safari 14+, Edge, and every mobile browser render WebP with alpha natively, no fallback needed for 96% of users.

How to use PNG to WebP

  1. Drop one or more .png files onto the upload zone, or click to browse — multiple files at once are supported.
  2. Set the WebP quality with the slider; 90 is the default for PNGs because they often contain detailed graphics with sharp edges.
  3. Click Convert to WebP — your browser re-encodes each file via the Canvas API with the alpha channel preserved.
  4. Compare the file-size reduction (30-50% typical) and preview the WebP output, with a checkerboard background showing transparency.
  5. Download a single WebP file, or click Download all (ZIP) to receive every converted file in a single bundle.
  6. Use the converted WebPs anywhere a modern browser will render them — the alpha channel works exactly like the original PNG.

When to use PNG to WebP

  • Optimising a website's logo, icons, or UI graphics where PNG was used for transparency but file size is now hurting page-load performance.
  • Converting a design system's PNG icon library to WebP as part of a performance optimisation pass without changing any visual fidelity.
  • Reducing the weight of an Android app's transparent assets — WebP with alpha is the recommended format and saves a measurable percentage of APK size.
  • Migrating a Progressive Web App's image library from PNG to WebP to improve First Contentful Paint and Largest Contentful Paint scores.
  • Compressing UI screenshots for documentation or Slack messages where the file size of raw PNG is excessive but you need transparent backgrounds.
  • Preparing transparent product photos or cutout PNGs for an ecommerce site where every kilobyte saved across thousands of images compounds into faster page loads.

Examples

Transparent logo

Input: logo.png: 512×512 with alpha, 78 KB

Output: logo.webp: 512×512 with alpha, 28 KB at quality 90 (64% smaller)

UI screenshot batch

Input: 10 PNG screenshots, ~280 KB each (2.8 MB total)

Output: ZIP of 10 WebPs, ~165 KB each (1.65 MB total) at quality 88

Icon set

Input: 50 icons.png, ~12 KB each (600 KB total)

Output: ZIP of 50 WebPs, ~6 KB each (300 KB total) at quality 90

Tips

  • WebP with alpha is supported in every modern browser since Safari 14 (September 2020). For broader fallback, use a <picture> element with a PNG source as the secondary option.
  • Default quality 90 keeps icons and graphics sharp; drop to 80 for screenshots where text rendering is robust, or push to 95 for assets where every detail matters.
  • If your PNG is a flat-colour graphic (logo, simple icon), the file-size win can be 60-70% rather than the typical 30-50% — these compress especially well in WebP.
  • Don't convert a PNG that was already converted from a lossy source — every re-encode adds artefacts. Always start from the highest-quality master available.
  • For 1-bit or 8-bit indexed PNGs (very small palettes), you may find that the original PNG is actually smaller than the WebP equivalent. Test before committing in batch.

Frequently Asked Questions

Does my image leave my browser?
No. The conversion uses the browser's built-in Canvas WebP encoder — your PNGs are decoded and re-encoded entirely in JavaScript inside your browser tab. Nothing is uploaded to any server, including UtilityKit's.
What's the size limit?
The dropzone label says 50 MB per file but the actual limit is your browser's available memory. Most browsers handle PNGs up to 100 MP (10000×10000) comfortably. Very large batches may slow the encode loop.
Is the WebP transparency preserved?
Yes. The browser Canvas WebP encoder writes a full alpha channel to the output, identical to the source PNG. Transparent logos, icons with cutouts, and screenshots with transparent backgrounds all preserve their transparency.
What quality should I pick for a PNG?
Default 90 is graphics-friendly — sharp text and crisp edges stay clean. Drop to 80-85 for general-purpose use where size matters more, push to 95 for high-value assets like brand logos. Avoid going below 75 on PNG sources with text.
Why is my WebP much smaller than the PNG?
PNG is lossless — it must store every pixel exactly. Lossy WebP uses psychovisual compression to discard imperceptible detail. For photographic PNGs, this can mean 50%+ size reduction with no visible quality difference.
Will WebP with alpha work in Safari and email?
Safari 14+ (September 2020) and every modern browser renders WebP with alpha natively. Some older email clients still don't support WebP, so use PNG fallback via <picture> for transactional email image attachments.
Can I do lossless WebP?
The browser canvas API only outputs lossy WebP — there is no built-in lossless option. For lossless WebP (which can still be 20-25% smaller than PNG), use a build tool like cwebp -lossless, sharp, or squoosh-cli.
Does the converter strip metadata?
Yes. The Canvas API does not preserve EXIF, ICC profiles, or other PNG metadata chunks during re-encode. The output WebP carries no metadata. This is usually a privacy benefit but be aware if your workflow relies on embedded colour profiles.

Explore the category

Glossary

WebP
Google's modern image format from 2010, supporting lossy and lossless compression, alpha transparency, and animation. WebP files are typically 25-50% smaller than equivalent PNG or JPG at the same visual quality.
PNG
Portable Network Graphics — a lossless raster format introduced in 1996 to replace the patent-encumbered GIF. PNG supports per-pixel alpha transparency and is universally rendered in every browser, OS, and image viewer.
Alpha channel
An extra data layer that stores per-pixel transparency information from 0 (fully transparent) to 255 (fully opaque). Both PNG and WebP support alpha; JPG does not.
Lossy WebP
The default WebP encoding mode used by browser canvas APIs. It applies psychovisual compression to discard some pixel detail in exchange for much smaller file sizes — visually indistinguishable at quality 85+.
Lossless PNG
PNG always uses lossless compression — every pixel of the original is preserved exactly. The trade-off is much larger file sizes than lossy formats like JPG or lossy WebP.
Re-encode
The process of decoding an image into pixels and then encoding the pixels into a different format. Each re-encode of a lossy format introduces minor quality loss; PNG-to-lossy-WebP is one such transition.