RunToolRunWebP to JPG
Convert WebP files to JPG format.
How to Convert WebP to JPG
Select your WebP files
Click the upload area or drop one or more .webp images — batch conversion is supported.
Instant in-browser conversion
Each WebP is decoded and re-encoded as a high-quality JPG (92%) on your device. Transparent areas are flattened to white.
Download the JPGs
Save each converted image — accepted by every upload form, app and device.
A lossy file becoming a different lossy file
Both formats discard information to save space, and they discard it in different ways. Converting means decoding the WebP back to pixels — artefacts included — and re-encoding those pixels as JPEG, which then applies its own compression on top. This is a second generation of loss, and it is unavoidable.
At a high quality setting the added damage is not visible on a normal photograph, which is why this conversion is perfectly reasonable in practice. But it is a one-way step, and converting back to WebP afterwards adds a third generation rather than restoring anything.
The file will usually get bigger
WebP's whole purpose is being smaller than JPEG at equivalent quality, typically by a quarter to a third. Converting therefore moves in the expensive direction: the same picture, in a larger file, with slightly less detail. That is the price of compatibility, and compatibility is the only reason to pay it.
So choose JPEG when the destination requires it — an upload form that rejects WebP, a printing service, an older application — and not as a general habit. If the image is going onto a web page you control, keeping the WebP is both smaller and sharper.
Transparency is filled, not preserved
WebP supports an alpha channel and JPEG does not. Transparent areas therefore have to become a solid colour, and this tool fills them with white. For a photograph with no transparency, nothing changes. For a logo or a cut-out product shot, the transparent background becomes a white rectangle that cannot be removed afterwards.
If transparency matters, convert to PNG instead. If the destination requires JPEG and the image has transparency, decide deliberately what the background colour should be rather than discovering it after the fact.
Where the work happens
The browser decodes the WebP and re-encodes it as JPEG on your own machine at a high quality setting. Nothing is uploaded, which matters for the saved images people most often need to convert: screenshots, product photographs, images from private systems.
Because both steps run locally, batch conversion is limited by your device's memory rather than by an upload quota. Converting a handful of images at a time is smoother than queueing a hundred, particularly on a phone.
Judging whether the conversion cost anything
The honest test is to compare the two files at full size on a real screen rather than in a thumbnail. Look at the places lossy compression fails first: smooth gradients such as skies and skin, fine repeated texture like fabric or foliage, and any hard edge between two strong colours. If those survive, the rest will.
If you do see degradation, the cause is almost always that the WebP was already heavily compressed rather than that the JPEG step was too aggressive. Converting from a better source is the fix; lowering the JPEG compression only makes a large file that faithfully reproduces damage that was already there.