You saved an image from a website and now Windows Photo Viewer, an old Photoshop version or your online shop's upload form refuses it: it's a .webp file. You're not alone — this is one of the most common format headaches of the last few years.
Here's what WebP actually is, and three ways to deal with it — including converting it to JPG or PNG right in your browser.
What is WebP, and why is everything using it?
WebP is an image format Google released in 2010, built on the same VP8 video technology as WebM. Its selling point: 25–35% smaller than JPEG at the same visual quality, plus transparency (like PNG) and animation (like GIF). For websites, that means faster pages and lower bandwidth bills — so CDN operators and sites serve WebP aggressively.
The catch: modern browsers love it, but plenty of desktop apps, older operating systems, CMS plugins and upload forms still don't. That mismatch is why conversion is a daily task.
Option 1: Just open it (no conversion)
Modern systems handle WebP natively: Windows 10/11 with up-to-date Photo Viewer (or any current browser), macOS Ventura+, Android, iOS 14+. The fastest "viewer" is your browser — drag the file onto a Chrome or Edge window.
If your app genuinely can't open it, or a form rejects it, move to option 2.
Option 2: Convert WebP to JPG or PNG in your browser
1. Open the converter
Use WebP to JPG for photos and uploads, or WebP to PNG when you need transparency preserved.
2. Drop your files
One file or a hundred — animated WebP is handled too (use the frame options to pick frames or export all of them).
3. Choose quality and download
For JPG, quality 85–92 is visually indistinguishable from the source for photos. Download each result or the whole batch as a ZIP.
The conversion happens locally in your browser — no upload, no queue, no waiting-for-email-with-download-link.
Option 3: Batch-convert a whole folder
If you've downloaded a site's images or a client sent a folder of WebP assets, use the Bulk Image Converter — it converts between JPG, PNG, WebP, AVIF, BMP and more in one pass, with dozens or hundreds of files at once.
Which target format should you pick?
| Goal | Convert to | Why |
|---|---|---|
| Upload to a form or old CMS | JPG | Universally accepted, small for photos |
| Keep transparency (logos, overlays) | PNG | Lossless, alpha channel preserved |
| Editing in old software | PNG | No generation loss when re-saving |
| Re-publishing on the web | Keep WebP! | It's already the optimal web format |
That last row matters: if your problem is "some old tool can't read it" but the file is destined for a website, don't convert — you'd be inflating the size. Convert a working copy instead.
FAQ
Does converting WebP to JPG lose quality?
It's a lossy-to-lossy re-encode, so technically yes — but at quality 85+ the difference is imperceptible. Convert from the original download, not from an already-compressed copy, and convert only once.
Can I convert animated WebP to GIF?
Yes — see the animated conversion guide. Animated WebP→GIF may increase file size, since GIF is the older, less efficient format.
Why did a website send me WebP when I asked for JPG?
Most CDNs now content-negotiate: browsers that accept WebP get WebP regardless of the original format. Saving with "save image as" grabs what the server delivered.
Is this conversion safe for private images?
As safe as it gets: the file is decoded and re-encoded inside your browser tab. Nothing is transmitted — disconnect from the internet and it still works.
Got a .webp file stuck right now? Convert it to JPG — the whole process takes about ten seconds.