Privacy check: the WebP converter reads, decodes, and creates the result in your browser. It has no image upload or remote conversion endpoint.
Before you begin
Have a WebP file available in your device's file picker. The converter checks the actual RIFF and WebP content instead of trusting the filename. It accepts static WebP images up to 20 MB each, up to 40 megapixels after decoding, and up to 8 files in a 64 MB batch; at most 2 conversions run at once.
Follow these steps
Open the WebP converter in a current browser. Choose Browse your device or drop a file onto the upload area.
Select one WebP image or a small batch. The queue shows each name, input size, dimensions, and ready or error status before conversion starts.
Select JPG when the destination expects a common photo format. Select PNG when transparent pixels or crisp graphics matter. The canvas re-encodes decoded pixels, so source-byte and metadata preservation are not promised. JPG quality is shown only for JPG.
Press Convert all. At most 2 files are converted at once. Each file is decoded locally and processed independently, so one failed item does not stop the others.
Review the preview and output size. Download one result or use the ZIP button for successful results. Duplicate names in a ZIP receive a numeric suffix.
JPG or PNG for a WebP image?
JPG is usually the practical choice for a photograph, an upload form, or a message that rejects WebP. The quality control changes the browser's JPG encoding tradeoff. JPG has no transparency channel, so Kivoza places a white background under transparent pixels.
PNG is useful for an image with transparent regions, crisp graphic edges, or a workflow that can accept a larger file. Kivoza sends decoded pixels to a PNG canvas, so transparent pixels remain transparent when the browser provides them. This is a re-encode and does not promise source-byte, metadata, or color-profile preservation.
Static WebP is the supported scope
The first version supports one static image per file. Animated WebP is detected from the container's animation flag or animation chunks and is reported as unsupported. The converter does not silently export one frame and label it as a complete animation conversion.
If a file will not convert
- An empty file is rejected before decoding.
- A JPG, PNG, or other file renamed to
.webpis rejected because its bytes do not contain a WebP container. - An animated WebP receives a specific unsupported message. Use a static export if you need one image.
- A file over 20 MB, over 40 megapixels, or in a batch over 64 MB is rejected with a visible limit.
- If the browser cannot decode the file or runs short of memory, use Retry after closing heavy tabs or try one file.
What to check in the result
The queue preview should match the source. A JPG download has a .jpg name, JPEG MIME type, and JPEG signature. A PNG download has a .png name, PNG MIME type, and PNG signature. Review the result before deleting the original. The tool does not promise metadata retention, animation conversion, or lossless JPG output.
Example workflow
For a real public sample named gallery-1.webp (30,320 bytes, 550 × 368), add it, choose JPG, leave quality at 88, and press Convert all. In a Chromium 148 check it produced gallery-1.jpg at 56,195 bytes; quality 60 produced 27,170 bytes and quality 100 produced 200,896 bytes. If a source contains transparent areas and the white background is unwanted, repeat with PNG.
Sources and verification
These instructions describe the current Kivoza WebP converter and its tested browser-native path. WebP decoding support and output size can vary by browser and image content. Always inspect the downloaded file in the application where you plan to use it.