Convert WebP to JPG in your browser
The format everything opens, from the format some things refuse. Set the quality yourself, and know that a transparent background will come out white.
or browse your device. Everything is processed on this device
No WEBP to hand?
JPG cannot hold it, and flattening onto white cannot be undone. PNG can, and the conversion is the same two clicks.
Convert to PNG insteadHow to convert WebP to JPG
One or a hundred. Nothing is uploaded at any point, so a batch is no slower for us and no different for you.
82 is a safe default for a file that has already been compressed once. Drag the divider to see it against the original.
The download is a .jpg that every phone, camera app, print shop and upload form will accept.
JPG or PNG, from a WebP?
Pick JPG if the image is a photograph and there is no transparency in it. It will be far smaller than the PNG alternative, every piece of software on earth opens it, and the quality loss from one careful pass is invisible at normal viewing size.
Pick PNG if there is any transparency at all, or if the image is flat artwork with hard edges: logos, icons, screenshots, charts, anything with text in it. JPG has no alpha channel, so a transparent background becomes a white rectangle, and JPG compression puts visible smearing around sharp edges that PNG does not.
One thing worth knowing either way. Your WebP is already lossy, so converting to JPG is a second lossy pass over an image that has been through one. That is why the quality here defaults higher than it does on the JPG compressor: it is compensating for damage that was done before the file reached you, and no setting on this page can undo it.
WebP to JPG FAQ
What happens to a transparent background?
It becomes white. JPG has no alpha channel, so transparency has to be flattened onto something and white is the convention. This cannot be undone afterwards, so if the image is a logo or an icon meant to sit on a coloured background, convert it to PNG instead.
Will the quality get worse?
A little, and it is worth understanding why. A WebP is already lossy, so this is a second lossy pass over an image that has been through one, and the two compound. At the default of 82 the difference is invisible at normal viewing size. Below about 70 on an image that started as a low-quality WebP, it starts to show.
Can I convert an animated WebP?
You will get the first frame as a still JPG, and the page says so when it happens, because JPG cannot hold an animation at all. To keep the animation, compress it as a GIF or leave it as a WebP.
How do I hit an email or upload size limit?
Turn on "Compress to a target size" and type the figure. We search for the highest quality that still fits under it and tell you where we landed, which beats guessing at a quality slider and re-checking the file size.
Are my WebP files uploaded to convert them?
No. The WebP is decoded and the JPG is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.
Does this remove EXIF, GPS and AI metadata?
Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.
Related
Same format joins the queue. Anything else re-routes to its own tool.