Convert WebP to JPG
Convert WebP images to standard JPG format for broad compatibility.
How to convert WebP to JPG — 3 steps
- 1
Add your WebP files
Drop in the images, singly or in a batch. Everything is decoded on your own machine rather than uploaded.
- 2
Set the JPG quality
Keep it high — around 90 — because the source has usually been compressed once already and a second heavy pass compounds the damage.
- 3
Download the JPGs
Save the converted images. JPG is understood by every application, device, and upload form you are likely to meet.
Converting between two lossy formats
This conversion has a characteristic worth understanding, because it is the one that determines how good the result looks. Most WebP files are lossy: detail was already discarded when they were created. JPG is also lossy, so converting means decoding an already-reduced image and compressing it again by a different method. The losses do not cancel out — they accumulate, an effect known as generation loss.
In practice a single conversion at a high quality setting is visually fine, and you would struggle to tell the result from the source. The damage appears when the quality is set low, or when a file goes through several rounds of conversion and re-saving. Because the two formats compress differently, JPG has to spend bits reproducing WebP's artefacts as well as the picture, which is why converting at 60 looks noticeably worse than an original photograph saved at 60.
The practical rule is to convert once, at a high quality setting, directly from the best source you have. If you also hold the original photograph the WebP was made from, convert that instead and skip the intermediate loss entirely.
Transparency, animation, and when JPG is the right target
Two things in a WebP have no equivalent in JPG. Transparency is the first: WebP supports an alpha channel and JPG does not, so any transparent area becomes a solid colour, normally white. For a logo or a cut-out product shot that is usually the wrong outcome — you get the subject in a white box — and PNG is the better destination. Animation is the second: WebP can hold an animated sequence, and JPG holds exactly one frame, so an animation converts to a still.
Where JPG is right is photographs destined for somewhere that will not accept WebP. Email attachments that need to preview reliably, documents and presentations, print services, and the many upload forms that list only JPG and PNG among accepted types. For continuous-tone photographic content with no transparency, JPG loses nothing that matters and gains universal compatibility.
It is worth checking what the file actually contains before choosing. If the image has a transparent background, convert to PNG instead. If it is a photograph with an opaque background, JPG is the smaller and more widely accepted choice, and the conversion is clean.
Your files never leave your device
Images are decoded and re-encoded inside your browser, so photographs and client work are converted without being sent to a server.
Most online PDF sites upload your document to their servers, process it there, and keep a copy for minutes, hours, or longer. PilotPDF works differently: the page downloads a small processing engine into your browser, and your file is opened and edited in your device's memory using WebAssembly. Nothing is transmitted, so there is nothing for a server to store, leak, or scan. You can even disconnect from the internet after the page loads and the tool keeps working.
Read more about how this works in our privacy-by-design explainer.