No upload
Your images stay on your device and are converted by the current browser.
WEBP to PNG batch converter
Convert up to 10 WEBP images to PNG per batch. Your browser processes them one at a time, and the files stay on your device.
Browser-local processing
Before choosing files: up to 10 images, 50 MiB per image. Images above 45 MP are rejected after decoding. ZIP output files are capped at 100 MiB combined; download larger results individually. Available device memory can impose lower practical limits. MiB = 1,048,576 bytes; MP = million pixels.
Up to 10 files per batch. Images are converted one at a time on your device.
Your images stay on your device and are converted by the current browser.
Conversion keeps each image's original width and height without intentional resizing.
Convert up to 10 images per batch. Download results individually or save successful results together as a ZIP.
Drop images or choose up to 10 files from your device.
The conversion runs locally inside your current browser.
Download each finished image individually, or choose Download All (.zip) once the batch finishes.
| Feature | WebP | PNG | JPG |
|---|---|---|---|
| Encoding | Lossy or lossless | Lossless encoding of decoded output pixels | Lossy photo encoding |
| File size | Often compact; depends on encoding | Can be larger, especially for photos | Depends on the photo and quality setting |
| Transparency | Supports alpha | Supports alpha | No alpha; this tool uses white |
| Useful for | Web delivery when accepted | Graphics, editing or PNG-required workflows | Photo workflows that request JPEG |
Conversion keeps the decoded pixel dimensions, not every feature of the source file. It does not remove backgrounds, restore lost detail or guarantee preservation of EXIF, ICC profiles or other metadata. Keep your original WebP.
Animated WebP is exported as a static image (the browser's default image or first frame), not an animated PNG or JPG.
WebP to PNG is useful when you need a widely supported lossless image format or want to keep decoded transparency for editing and graphics workflows.
PNG preserves decoded WebP transparency, but the file can be larger than the WebP source. If your main goal is photo compatibility, try WebP to JPG.
Compare WebP and PNG: transparency, size and compatibility →
If you also need a smaller file after conversion, use the image compressor.
No. Image decoding and conversion happen locally in your browser. Your files are not sent to FileOnTap servers.
Yes. Convert up to 10 files per batch. Your browser processes them one at a time. Download finished results individually, or save successful results together as a ZIP after processing finishes.
No. The converter keeps each image's original width and height and only changes the image file format.
Not guaranteed. Browser re-encoding generally does not preserve all original EXIF metadata, so keep the source file when metadata matters.
Yes. When converting to PNG, decoded transparent pixels are preserved.
No. Renaming changes the filename, not the WebP encoding. Decode the source and create a real PNG or JPG for a destination that requires that format.
No. PNG can retain existing decoded alpha transparency, but it does not remove an opaque background. Neither PNG nor JPG can restore detail already discarded by lossy WebP encoding.
No. PNG can be much larger than a compact WebP, especially for photos. JPG size also depends on the source and encoding. Compare actual bytes and appearance. The image compressor may help, but cannot guarantee a smaller file or an exact target.
No. This browser converter produces one static PNG or JPG using the animation's default image or first frame. It does not export the animation sequence. Keep the source if animation matters.