How to use the WebP to JPG tool
- Choose or drop one or more WebP files.
- Run the conversion to JPG.
- Download the JPG, or the ZIP if you converted a batch.
To convert WebP to JPG, open the Archive.London WebP to JPG tool, choose or drop your WebP files and run the conversion. Download the JPG, or a ZIP when you convert several files at once. The conversion takes place in your browser, so the images are never uploaded to a server.
When a WebP needs to become a JPG
WebP is now the format many websites serve, so images saved from a browser often arrive as .webp files. Browsers display them without trouble. Older photo editors, some office software, print services and a good many upload forms do not.
JPG is the dependable fallback, because practically everything reads it. Two points are worth knowing before you convert:
- Both lossy WebP and JPG discard detail, so the JPG is a second generation of compression. The change is normally slight, but the JPG cannot be better than the WebP it came from.
- JPG has no transparency. If your WebP has transparent areas they will be flattened to a solid colour. To keep them, convert to PNG instead.
The JPG will often be larger than the WebP. That is expected, since WebP compresses more efficiently.
What WebP is and why you keep meeting it
WebP is an image format released by Google in 2010. Its lossy mode is derived from the VP8 video codec, and it also offers a lossless mode, transparency and animation. Because it usually produces smaller files than JPG at similar visual quality, sites use it to make pages load faster, and all current major browsers can display it.
This tool uses that browser support. Your browser decodes the WebP, draws it to a canvas in memory and encodes a standard 8-bit sRGB JPG. The file stays on your device throughout and nothing is stored.
As with any re-encoding in the browser, metadata and embedded colour profiles in the WebP are not copied into the JPG.
A saved web image is not a source file
It is easy to forget where a WebP usually comes from. An image saved from a web page is a display copy: resized, heavily compressed and frequently stripped of its caption and credit. Converting it to JPG makes it openable but does not make it a good original, and it does not change who owns the copyright.
Picture researchers treat such files as reference only. For publication they go back to the rights holder for a proper file and a licence, which is also the only reliable way to get accurate caption information.
For the Robert Harper Photograph Library, that route is described under professional access.
Frequently asked questions
Why do images download as WebP instead of JPG?
Many websites now serve pictures as WebP because the files are smaller and pages load faster. When you save an image from such a site, the browser saves the file it was actually sent, which is the WebP. The picture is fine; the format is simply newer than some software expects.
Will I lose quality converting WebP to JPG?
A little, in most cases. JPG is a lossy format, so encoding to it discards some detail, and if the WebP was itself lossy this is a second round of compression. For normal viewing the difference is rarely noticeable. The JPG will not be sharper or cleaner than the WebP.
What happens to transparency in my WebP?
JPG cannot hold transparent pixels, so any transparency is flattened to a solid colour in the JPG. If the transparent background matters, use the WebP to PNG tool, which keeps it. If you want to choose the fill colour yourself, the general Image Converter has a background colour option for JPG output.
Can I convert lots of WebP files together?
Yes. Drop or select the whole set and the tool converts them in one pass, then gives you a ZIP containing the JPGs. How many you can do at once depends on your device's memory. Ordinary web-sized images are small, so batches of dozens are normally no difficulty.
Does the tool work on a phone?
Yes. It runs in the browser on iPhone and Android as well as on desktop computers, and nothing needs installing. Web images are usually modest in size, so memory is seldom a problem. Extremely large images, above roughly 100 megapixels, may fail on a phone and are better handled on a computer.
