PNG to WebP Converter

PNG to WebP, smaller and sharper. Nothing ever uploads.

Drop PNG files below — get WebP images back, usually much smaller than the PNG, with transparency kept. Converted entirely on your device.

  • Your file data never leaves the device
  • Lossless or lossy — your choice
  • Batch up to 20 files
  • Works offline after load

Convert PNG to WebP

Add your PNG files

Drag & drop PNG files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Loading the WebP encoder…

    No files yet. Everything stays on this device. Downloads start instantly.

    Privacy you can verify, not just trust

    Most online PNG converters upload your images to their servers first — and some keep a download link live for 30 days. This one can't: your browser decodes PNG natively and the WebP encoder (libwebp, compiled to WebAssembly) runs entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. The encoder file is served from this site, not fetched from anywhere else, and there is no file fetched after load for the conversion itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Convert any PNG above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — conversion still works.

    How to convert PNG to WebP without uploading it

    Every "free" online PNG converter you've used uploads your images to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for days. For personal screenshots, logos, and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

    This tool does exactly that. When you drop a PNG here, your browser:

    1. Decodes the PNG natively — every browser includes a PNG decoder, so there is no decoder file to download and no waiting for a library to load.
    2. Reads the image's orientation data and stores the output upright, so a portrait image doesn't come back sideways.
    3. Resizes it to the width you picked (800 px by default), keeping the aspect ratio and the alpha channel — transparency is never flattened onto a background.
    4. Encodes it as WebP with libwebp, the reference WebP encoder, running as WebAssembly in your browser — lossy at the quality you pick, or truly lossless with the Lossless toggle on. Your original file is never modified.

    Lossy or lossless — which should you pick?

    Pick lossy (the default, quality 85) when the image is going on a website, into a blog post, or onto Discord or a forum: it is the small file that loads fast, and at quality 85 it looks identical to the original for almost every image. Pick lossless when every pixel has to survive exactly — a logo master, a screenshot you will edit further, or an icon with razor-sharp edges. Lossless files are bigger, sometimes bigger than the PNG for photos, because lossless cannot throw detail away. Either way, keep the PNG as your master copy and publish the WebP.

    Why is WebP smaller than PNG?

    PNG compresses losslessly: it has to be able to rebuild every pixel exactly, so photos — millions of slightly different shades — compress poorly. WebP's lossy mode is allowed to discard detail your eye cannot see, and it predicts neighbouring pixels far better than PNG does, so the same photo typically comes out noticeably smaller at quality 85 with no visible difference. That is why Google, WordPress and most image CDNs serve WebP by default, and why switching a site's PNGs to WebP is one of the cheapest PageSpeed wins there is. The saving is real but not magic: flat graphics with few colours were already tiny as PNG, and lossless WebP cannot beat PNG by much.

    Why won't my PNG load fast enough on my site?

    PNG is the web's default for screenshots and logos, but a PNG photo can weigh several megabytes, and every kilobyte is time your visitor waits — especially on a phone. WebP keeps the picture looking the same while cutting the weight, which is what Core Web Vitals and PageSpeed measure. If the destination has a size limit, pick a destination preset and the converter will aim for it: website heroes aim for under 300 KB, blog images under 150 KB, Discord or forum uploads under 256 KB.

    Honest limitations

    Lossy by default

    Unless Lossless is on, the output discards some detail. Quality 85 is visually identical to the original for most images, but quality 100 is near-lossless, not pixel-perfect. Keep the PNG as your master copy.

    Lossless can be larger than the PNG

    Lossless WebP cannot throw detail away, so for photos it can come out bigger than the PNG it came from. If the file comes out bigger, the card says so — use lossy mode for publishing instead.

    Animated PNG is first frame only

    Browsers decode only the first frame of an APNG for web pages. This tool converts that frame and says so plainly on the file card. WebP itself can animate, but this tool converts still images only.

    Not every app accepts WebP yet

    Every modern browser displays WebP, and Discord, Slack and most forums accept it — but a few older upload forms and apps still only take JPG or PNG. Check the destination first, or convert to JPG instead.

    Metadata is stripped

    Camera metadata (EXIF, including location) is dropped on re-encode, and 16-bit PNGs are tone-mapped down to 8-bit. Orientation is preserved — the output is stored upright.

    Very large images depend on your device

    The encoder runs entirely on your device, so a 50-megapixel PNG needs hundreds of megabytes of memory while it converts. A desktop handles that; a low-memory phone may not. Files over 25 MB are refused outright.

    Frequently asked questions

    Is WebP really smaller than PNG?

    Usually, yes. WebP's lossy compression is far more efficient than PNG's, so photos and screenshots typically come out noticeably smaller at quality 85 — and this tool shows the before and after size honestly for every file, so you can see the saving instead of taking our word for it. Flat graphics with very few colours can occasionally stay about the same size, and a lossless WebP can be larger than the PNG for photos, because lossless cannot throw detail away. If a file comes out bigger, the card says so and you can keep the PNG.

    Is the WebP output lossless?

    Only when the Lossless toggle is on. With it on, the encoder is libwebp's true lossless mode, which stores every pixel exactly — a lossless WebP decodes back to the identical image. With it off (the default), the output is lossy WebP at the quality you pick: quality 85 looks identical to the original for most images, and quality 100 is visually near-lossless but not pixel-perfect. Keep your PNG as the master copy and use WebP as the published version.

    Will my PNG's transparency survive as WebP?

    Yes. WebP stores a real alpha channel, so transparent and semi-transparent pixels survive the conversion — smooth edges stay smooth, unlike GIF, which only allows fully opaque or fully gone. The preview shows transparency as a checkerboard so you can see it. Transparency is preserved in both lossy and lossless mode, though lossy mode can soften very fine semi-transparent detail at low quality.

    Will the animation in my PNG survive as a WebP?

    No. An animated PNG (APNG) carries several frames, but browsers only expose its first frame to a web page, so this tool converts that first frame and says so on the file card instead of silently dropping the motion. WebP itself can animate, but this tool converts still images only. If you need an animated WebP, convert each frame separately and combine them with an animation tool.

    What happens to transparency and metadata?

    Transparency is preserved — WebP has a full alpha channel, so see-through areas stay see-through. EXIF metadata, including location, is dropped on re-encode. 16-bit PNGs are tone-mapped down to 8-bit, because the browser canvas that feeds the encoder stores 8 bits per channel. Orientation is preserved — the output is stored upright.

    Why convert PNG to WebP instead of keeping the PNG?

    PNG keeps a picture looking its best, but it is a poor compressor for photos: a PNG screenshot or photo can be several times larger than the same image as WebP, and that weight slows the page down. WebP was built for the web — smaller files, faster loads, better Core Web Vitals and PageSpeed scores — and every modern browser displays it. Keep the PNG as your master copy for editing, and publish the WebP. If the destination does not accept WebP, use our PNG to JPG converter instead.

    Can I share the WebP on Discord, a forum or by email?

    Usually, yes. Discord, most forums, Slack, WhatsApp and every modern browser display WebP inline, and email clients are catching up — though a few older upload forms and apps still only accept JPG or PNG, so check the destination first. Use the destination presets if the app has an upload size limit: website heroes aim for under 300 KB, blog images under 150 KB, and Discord or forum uploads under 256 KB. The presets aim for the target, they do not guarantee it — the tool reports the size it actually reached.

    Is there a file size or daily limit?

    There is no daily limit and no account. A 25 MB safety cap applies per file and 20 files per batch, because decoding large images in the browser is memory-heavy. Most PNGs saved from the web are well under 5 MB, far below the cap. Very large images also depend on your device's memory — the encoder runs entirely on your device, so a low-memory phone will struggle with a 50-megapixel PNG where a desktop will not.