Kivoza image tools · WebP

Convert WebP to JPG or PNG.

Convert static WebP images in this browser tab. Your originals stay on your device, and no account is needed.

Local processing No upload JPG + PNG

Drop a few in

Choose your output.

Static WebP only. Animation is detected and reported before decoding.

Drop WebP files here

or browse your device. We check the content before decoding.

Up to 8 files · 20 MB each · 40 megapixels each · 64 MB per batch · 2 conversions at once

Output format

JPG cannot contain transparency, so transparent pixels use a white background. PNG keeps alpha when the browser decodes it. Both outputs are canvas re-encodes; metadata, color profiles, and original losslessness are not promised.

Conversion queue 0

Add a file to begin.

A short path

Choose, convert, download.

01

Choose

Select WebP images or drop them onto the queue. The page checks the RIFF container and rejects empty, damaged, or animated files.

02

Convert

Your browser's native WebP decoder draws the static image to a local canvas. JPG quality is applied only to JPG output.

03

Download

Preview each result, download one file, or package the successful results into a ZIP created in this tab.

Know the edges

Built for everyday images.

The limits keep browser decoding predictable on laptops and phones. The converter runs at most 2 files at once. Available device memory still affects unusual or demanding files.

20 MBmaximum input size per file
40 MPmaximum decoded pixel count per file
8 filesmaximum queue size per batch

JPG or PNG?

JPG is widely accepted and usually smaller for photographs. PNG is useful for transparent pixels or crisp graphics. JPG output always uses a white background.

What is supported?

This first version converts one static WebP image per file. It does not promise metadata, color-profile retention, animation, or source-byte losslessness.

When does it fail?

Empty files, damaged RIFF containers, renamed non-WebP files, animated WebP, unsupported browser decoding, and size limits are reported per file.

A real workflow

From a site asset to a shareable image.

Input / public sample

gallery-1.webp

Google's WebP gallery sample is 30,320 bytes at 550 × 368. The queue reports the name, input size, dimensions, and ready status before conversion.

Output / Chromium 148 check

gallery-1.jpg

At JPG quality 88, the same 550 × 368 sample produced a 56,195-byte JPEG. Quality 60 produced 27,170 bytes and quality 100 produced 200,896 bytes; browser and content affect the result.

Frequently asked questions

Are my images uploaded?

No. Validation, native decoding, canvas conversion, previews, and ZIP creation happen in this browser tab. The app has no image upload or remote conversion endpoint.

Does this convert animated WebP?

No. The page checks WebP animation flags and animation chunks before decoding, then reports that animated WebP is not supported. It does not silently export one frame as a complete conversion.

Why is a JPG background white?

JPG has no alpha channel. Before encoding JPG, the converter places a white background under transparent pixels. Choose PNG when you need transparency.

Why did one file fail?

The file may be empty, damaged, animated, over a limit, a renamed non-WebP file, or unsupported by the browser's native decoder. Other queue items can finish, and the failed item has Retry.