WebP to JPG converter
Turn the .webp files you saved from websites into ordinary JPGs that any app will open.
- Processed on your device. Your photos are never uploaded. How we know
- Free, no sign-up, no watermark
Drop WebP images to convert to JPG
Drop files, paste with Ctrl+V, or choose them from your device.
PixWrench’s code runs on your device. We don’t receive your files, file names or their contents.
PixWrench’s code runs on your device. We don’t receive your files, file names or their contents. What happens to your files
How to convert WebP to JPG
You right-click a product photo or a recipe picture, choose “Save image”, and end up with a file ending in .webp. Your browser shows it fine. Then the photo app, the print kiosk or the job application form refuses it. That gap is exactly what this converter closes.
It decodes the WebP on your own device and writes a standard JPG. You choose the quality, and if the WebP had a transparent background, you choose what color fills it. No account, no upload, and no waiting in a server queue.
- 1
Add the .webp files
Drag them in from your Downloads folder or use the file picker. Several at once is fine.
- 2
Check the settings
Quality starts at 90, which keeps the picture looking like the original. Set a fill color if any image has transparent areas.
- 3
Download as JPG
Take the files one at a time or as a zip. The WebP originals stay untouched on your device.
What this tool does
- Still WebP images, lossy or lossless
- JPG quality setting, default 90
- Fill color for see-through areas
- Also takes JPG, PNG, AVIF and HEIC
- Batch mode with one zip download
- Upright output, color profile kept
- Choose how much metadata survives
Worked example: a 113 KB WebP photo
Our test WebP is a 1200 × 800 photo of 113,156 bytes. Converted with MozJPEG, the encoder used here, measured in Node:
- JPG at quality 90 (the default): 114,387 bytes, about 1% larger than the WebP.
- JPG at quality 80: 65,647 bytes, about 42% smaller.
At the default the file stays roughly the same size, because the JPG has to describe the same detail the WebP kept, and WebP usually needs fewer bytes to do it. Dropping to 80 makes a lighter file, but that is a second round of lossy compression on an image that was already compressed once, so look closely at fine textures before you commit. (1 KB = 1,000 bytes.)
From WebP pixels to a JPG file
The tool first reads the file’s opening bytes to confirm it really is a WebP, whatever its name says. Google’s libwebp decoder, compiled to WebAssembly, unpacks it into raw pixels in a background worker. Lossy WebP and lossless WebP both decode to the same kind of pixel grid, so either works.
If the image has an alpha channel, transparent pixels are blended onto your chosen color, because JPG cannot store transparency. MozJPEG then encodes the result at your quality setting, and any embedded color profile is copied across.
Why websites hand you WebP in the first place
When a browser asks a server for an image, it sends an Accept header listing the formats it can display. MDN documents that current Chrome, Firefox and Safari all include image/webp in that list, so a site can safely send WebP instead of JPG. Google reports lossy WebP files as 25–34% smaller than comparable JPEGs, which makes pages load faster. When you save the image, you get the WebP the site sent.
Not every app, editor or upload form accepts WebP yet, which is where the trouble starts. If you want to keep a transparent background, the WebP to PNG converter is the better choice. For the full format picture, see JPG vs PNG vs WebP vs AVIF.
Good to know
- Animated WebP is not supported. Moving WebP images are turned away with a message rather than silently cut down to their first frame.
- Transparency becomes a solid color. Pick white, black or a brand color; use WebP to PNG if you need the see-through areas.
- The JPG may not be smaller. At quality 90 our test file came out about the same size as the WebP.
- Quality can’t be restored. Detail the WebP encoder removed stays removed in the JPG.
- Big pictures have a ceiling: 50 megapixels on computers, 24 on phones, with an offer to scale to 6000 px on the long edge.
What happens to your files
Processed on your device. Your photos are never uploaded. PixWrench’s code runs on your device. We don’t receive your files, file names or their contents.
Pictures you saved from the web stay on your computer or phone: the WebP is decoded and the JPG encoded by code running in this tab. If a saved image happens to carry metadata, the metadata option decides what is copied into the JPG. We never see the file names or the pictures.
Related tools and guides
Questions people ask
Why does my browser save images as WebP?
Many sites send WebP to browsers that announce support for it, because the files are smaller. Saving the image keeps the format the site served.
Can I convert an animated WebP to JPG?
No. Animated WebP files are rejected with an explanation, because a JPG can only hold one still frame and we don’t want to drop the rest without asking.
Will I lose quality converting WebP to JPG?
A little, since JPG is lossy too. At the default quality of 90 the difference is hard to see. Lower settings save space but soften fine detail.
What if the WebP has a transparent background?
The transparent area is filled with the color you pick. To keep it transparent, use the WebP to PNG tool instead.
Can it also convert AVIF files I downloaded?
Yes, this page accepts AVIF too, and there is a dedicated AVIF to JPG converter with notes specific to that format.
Sources and review
- MDN — List of default Accept values
- Google for Developers — An image format for the Web (WebP)
- MDN — Image file type and format guide
Page reviewed by the PixWrench team · How it works · Changelog · Report a problem