How to Convert WebP to JPG (and Why Sites Give You WebP)
To convert a WebP image to JPG, open it in a converter that re-encodes the pixels (not one that just renames the file), pick JPEG as the output, and download the new file. In UtiliKit's WebP to JPEG converter that's one drop and one click, and the image never leaves your browser. On Windows you can also open the file in Paint and use Save as, and on a Mac, Preview's Export menu does the same job. All three give you a normal .jpg that any form, email client or old program will accept.
The rest of this page explains why you keep getting WebP files in the first place, what changes when you convert, and the few cases where converting is the wrong move.
Why websites hand you WebP instead of JPG
When you right-click an image on a shop page or a news site and save it, there's a good chance you get a .webp file. That's deliberate. WebP files are usually 25 to 35% smaller than a JPG of similar visual quality, so a page full of product photos loads noticeably faster, and site owners care about that because page speed affects search rankings and how many visitors stick around.
Many sites don't even store WebP. They keep the original JPG and a server or CDN converts it on the fly when it sees that your browser supports WebP (every current browser does). Save the same image in an old browser, or through a different link, and you might get the JPG instead.
So the file isn't broken. It's just a format that some software still doesn't open.
Where WebP still causes trouble
Browsers are fine with WebP. The problems show up everywhere else. These are the usual sticking points:
- Upload forms (job portals, government sites, visa and passport services) that only accept .jpg, .jpeg or .png.
- Older versions of desktop software, print shop order systems and some email clients that show a blank attachment.
- Marketplaces and listing tools that reject WebP for the main product photo.
- Messaging apps that send a WebP as a "sticker" or a file instead of a normal photo.
If you hit one of these, converting is the right call. Renaming photo.webp to photo.jpg is not. The bytes inside are still WebP, and a strict upload form will either reject it or, worse, accept it and show a broken image later.
What actually changes when you convert
Three things, and only one of them usually matters.
File size goes up. As a rough example, a 1600 × 1067 px product photo of around 120 KB as WebP will usually land somewhere near 170 to 200 KB as a high-quality JPG. In general, expect the JPG to be roughly 1.3 to 1.8 times bigger. If a form has a size limit, run the result through the Compress to a File Size tool afterwards and set the target, say 100 KB or 200 KB.
Transparency disappears. JPG has no alpha channel. WebP can be transparent like a PNG (logos, cut-out product shots, stickers), and when those become JPG the transparent areas have to be filled with something. UtiliKit fills them with white, which is what most people want for documents and listings. Some other tools fill with black, which is why a logo occasionally turns into a black rectangle after conversion.
Quality changes slightly. WebP and JPG are both lossy (usually), so converting decodes one set of compression artefacts and encodes them again with another. At a high JPEG quality setting the difference is invisible on a normal photo. UtiliKit's converter encodes at 92% quality, which keeps edges clean and doesn't bloat the file the way 100% would.
Animated WebP is the odd one out: JPG can't animate, so you only get the first frame.
Step by step in the browser
Here's the full process with the free tool, for a single file:
Open the WebP to JPEG page, drag the .webp file onto it (or click to pick it), check that JPEG is selected as the output and press convert. The new file downloads as a .jpg with the same pixel dimensions as the original. Nothing gets uploaded: the conversion runs in your browser tab, which also means it works on a slow connection and with files you'd rather not send to a server, like a scanned ID or a signed document.
Converting dozens of files from a folder of saved product images? The batch upload and ZIP export are part of UtiliKit Premium (EUR 0.99 a month or EUR 9.99 lifetime). For the occasional file, the free version is enough.
The general Format Converter handles the other directions too, if you need PNG to WebP or JPG to PNG instead.
When not to convert WebP to JPG
If the image has transparency you want to keep, convert to PNG, not JPG. A cut-out product shot on a transparent background turned into JPG gets a white box behind it, and you can't get the transparency back.
If you're the one running the website, leave your images as WebP. They're smaller and faster, and every browser your visitors use can show them. Converting your own site images to JPG just makes pages heavier.
And if you only need to view the file, you don't need to convert anything. Drag it into a browser tab. It opens.
One more mistake worth avoiding: converting the same image back and forth several times. Each lossy save throws a little more detail away, and after four or five rounds you'll see blocky skies and smeared text. Keep the original somewhere and always convert from that.
What I'd actually do
For a one-off upload, convert in the browser, check the file size, and compress only if the form complains. That's two minutes, and you keep full control of the result.
For anything with a transparent background, go to PNG first, since most upload forms that reject WebP will happily take a PNG.
And if you regularly save images from websites for documents or presentations, it's worth keeping a "converted" folder next to the originals. You'll stop wondering which file is which, and you'll never end up re-compressing a copy of a copy.
Quick reference
| You need | Convert to | Watch out for |
|---|---|---|
| Upload to a form that rejects WebP | JPG | Size limit after conversion |
| Logo or cut-out with transparency | PNG | Larger file than WebP |
| Email attachment for older clients | JPG | Resize if over 2000 px |
| Images for your own website | Keep WebP | Nothing, it's already ideal |
| Print shop order | JPG at high quality | Check their pixel requirements |
If the converted JPG ends up too heavy for wherever it's going, the Image Compressor will bring it down without changing the format, and you can watch the file size update before you download.
Frequently asked questions
Can I just rename a .webp file to .jpg?
No. Renaming changes only the extension, not the data inside. Some programs will refuse the file, and some upload forms will accept it and then display a broken image. Use a converter that re-encodes the image.
Does converting WebP to JPG lose quality?
Slightly, because both formats are usually lossy and the image is compressed again. At a high JPEG quality, such as the 92% UtiliKit uses, the difference isn't visible on normal photos.
Why did my image get a white background after converting?
The WebP had transparent areas and JPG can't store transparency, so those areas were filled with white. If you need to keep transparency, convert to PNG instead.
Is my image uploaded when I convert it on UtiliKit?
No. The conversion runs in your browser on your own device, and the file isn't sent to a server. That also makes it suitable for documents and photos you'd prefer to keep private.