Turn a WebP into the still image every program on your machine will open, with the transparency intact.
Your files never leave your browser — all processing is local.
✓ EXIF, GPS and all other metadata are removed from the output.
Drop images here
or click to browse — PNG, JPEG, WebP, GIF, HEIC, AVIF, SVG — you can also paste images (Ctrl+V) anywhere on this page
Animation is the loss that surprises people. The converter probes every incoming file with the browser's ImageDecoder, and when it finds more than one frame while PNG is the target, it keeps the first frame, closes the decoder and warns that only that frame was converted. The remaining frames, the per-frame delays and the loop count have nowhere to go, because this route writes a plain single-image file rather than an APNG. If the motion is what you came for, choose GIF as the target — the animated path there preserves every frame and its timing — or keep the source format and simply re-encode it.
What does survive is more than most conversions manage. The source's 8-bit alpha channel maps directly onto the target's, so soft shadows, antialiased edges and semi-transparent pixels are carried across with no background color applied. If the input was lossless, the output holds exactly the same pixel values. If it was lossy, the output records the decoded result faithfully, artifacts and all — the smoothing and block structure the first encoder introduced are now the image, and no later step can separate them from the subject.
Metadata does not cross. A WebP may carry EXIF and ICCP chunks inside its RIFF container; the converter decodes to pixels through a canvas, so those chunks are not transferred and the result comes out untagged. Capture time, camera fields, GPS and the source color profile are therefore gone, which is convenient before sharing a picture and inconvenient if you were relying on any of them.
On 2026-09-12 the script measured a 1280 × 854 lossy WebP at quality 85, 319,834 bytes. Decoding it and writing PNG with "optimize (oxipng)" on produced 1,818,413 bytes, about 5.7 times as large. That checkbox is off by default on this page, so converting with the settings as they load usually produces a larger PNG. Part of that ratio is simply the cost of lossless storage, and part of it is that the new encoder must now store the old one's smoothing and block edges as if they were detail. A screenshot or a flat illustration grows far less, and a lossless source of a flat graphic can convert to a very similar size, since both formats are then storing the same exact pixels with related compression schemes.
Do not convert a file you are about to publish. It was already the smaller one, and this route multiplies the bytes without improving anything — if some browser cannot display the original, a JPG fallback is far cheaper than a five-times-larger PNG. Do not convert an animated sticker or reaction image and expect to keep the motion; target GIF instead. Do not convert as a way to fix a blurry picture, because the blur is in the pixels now. Converting is right when a desktop editor, an office document, a printer driver or an upload form rejects the file, when transparency has to survive that handover, or when you want a stable intermediate to edit repeatedly.
Conversion happens entirely in your browser — no upload, no queue, no watermark. Drop in as many files as you like and download them individually or as a zip.
Only the first frame is kept, and the converter says so in a warning. The delays and loop count are discarded because this route writes a single-image file, not an APNG. Choose GIF as the target if you need the whole animation to survive the conversion.
The encoding step is lossless, so nothing further is lost. Whether the picture is lossless overall depends on the input: a lossless source converts pixel for pixel, while a lossy one has its existing artifacts recorded exactly and permanently. Neither case restores anything.
One format stored an efficient lossy approximation; the other stores every decoded pixel, including the smoothing and block edges of that approximation, which compress badly. The measured 1280 × 854 sample went from 319,834 to 1,818,413 bytes, roughly 5.7 times.
No. Conversion happens inside your browser using the canvas API and a Web Worker — files never leave your device. There is no upload step, no queue and no file size limit beyond your machine's memory.
No — and that's a feature. Re-encoding through the canvas strips all metadata: GPS location, camera model, timestamps and color profiles. The output contains pixels only, which is usually what you want before sharing an image publicly.
Yes. Drop or paste any number of files; each is converted in the background with its own progress and download button, and you can grab everything at once as a .zip archive.
It depends on the target. The converter always decodes to raw pixels and re-encodes, whichever formats are involved, which is also how metadata gets stripped. For lossless targets (PNG, and GIF within its 256-color limit) the pixels stay identical to what was decoded; for JPEG, WebP and AVIF the quality slider controls the trade-off, and converting a file that is already lossy adds one more generation of loss.