A compatibility conversion for WebP files, with animation and alpha called out before JPEG discards either one.
What changes when WebP becomes JPEG
WebP can be lossy or lossless, can contain transparency and can animate. JPEG has one lossy still-image representation. The queue detects the container from its RIFF signature and reports animation instead of silently pretending the two formats have equal capabilities.
If alpha exists, the matte control becomes part of the visual result. A white matte suits document and marketplace uploads; a sampled edge can avoid a pale fringe around a cut-out; a custom colour is safest when the destination background is known.
A short, inspectable workflow
- Drop one WebP file or a whole selection. The queue reads the signature inside each file instead of trusting its extension.
- Inspect the detected type, dimensions and any format notice on each row before conversion.
- Choose JPEG quality and, where transparency exists, the colour that must replace it.
- Choose whether ordinary EXIF data survives and whether GPS coordinates are removed.
- Convert the queue. More than three finished files download as one ZIP so the browser does not open a stack of save prompts, and Download as ZIP bundles any two or more.
What the conversion cannot preserve
Animation, alpha and WebP-specific container structure do not survive. Converting one lossy format into another also means a second quantisation pass, so use the highest JPG quality the destination permits and avoid cycling the result through this conversion again.
A converted file is a new JPEG, not the original format with a different filename. Keep the source whenever animation, layers, high bit depth, transparency or repeated future edits might matter.
Questions about this input
What happens to animated WebP?
Can a WebP-to-JPG conversion improve quality?
Does transparent WebP work?
Photos stay on your device.