WebP Converter

How to convert images to or from WebP

1. Add images. Drop one file or a whole batch onto the box above — up to 200 images (100 MB) per batch. JPG, PNG and WebP are all read by their actual bytes, never by their file name.
2. Choose the output format. One conversion target per batch: WebP to save space, JPG for maximum compatibility, or lossless PNG for pixel-perfect results.
3. Set quality and transparency. The WebP/JPG quality slider (default 85%) controls lossy output. Transparent images going to WebP or PNG keep their transparency; going to JPG, they are flattened onto white or any colour you pick, with a live preview before you commit.
4. Compare and save. Every card shows before/after sizes with the exact difference, the comparison view shows both versions, and you can download individually or take the whole batch as a ZIP.

Why WebP (and when not)

• Photos: WebP is typically 20–40% smaller than an equivalent JPG at the same visual quality.
• Transparency + small size: WebP supports alpha at much smaller sizes than PNG — good for logos and UI graphics.
• Already-optimized files: converting a small WebP back to JPG or PNG may grow it — the tool tells you when the output is larger.
• Old software: JPG is still the safest target when a destination app predates WebP support.

Limitations, stated plainly

• Format support depends on your browser. The WebP option only appears when the browser really encodes WebP (verified by producing a test file and checking its MIME type), and WebP inputs are refused if the browser cannot decode them.
• It is refused, not guessed: converting a file into the format it already has produces a clear per-file message instead of a wasteful copy.
• Batch size is capped (200 files, 50 MB each, 100 MB total) and sources beyond 24 megapixels / 8192 px per side are refused, so very large images fail early with a clear message instead of freezing your device.
• Metadata is not copied. EXIF, XMP and colour profiles beyond what the browser reads are not preserved.