You right-clicked an image. You hit "Save image as." You tried to use it — a listing photo, a form upload, an old editor — and got the message: file type not supported.

The file ends in .webp. You didn't choose that. Nobody chooses that. The website chose it for you, and now the format problem is yours.

Here's the part that makes people angry: this isn't a bug, and it isn't going away. WebP is winning on the web for good reasons — while staying annoying everywhere else for equally real reasons. Once you understand why both things are true, converting becomes a two-second habit instead of a recurring crisis.

Why the web serves you WebP

WebP is Google's image format, and it exists for one reason: smaller files.

Google's own numbers, from the official WebP documentation: lossless WebP images are 26% smaller than equivalent PNGs, and lossy WebP comes in 25-34% smaller than comparable JPEGs at equivalent quality. Transparency — the thing that used to force everyone into heavy PNGs — costs just 22% additional bytes in lossless mode, and a lossy WebP with transparency is typically 3x smaller than the PNG version.

For a website, that's not a rounding error. Images are usually the heaviest thing on a page. Cut them by a quarter to a third and pages load faster, servers pay less for bandwidth, and Google's own ranking systems — which reward fast pages — smile upon you.

So every serious site converts its images to WebP automatically. The product photo you're saving was probably uploaded as a JPG by some employee. The server converted it. You're downloading the converted copy.

You're not going crazy. The web really did switch formats under your feet.

Why your apps still choke on it

Browsers moved fast. Everything else didn't.

Per caniuse.com, WebP now works for about 96% of web users globally — Chrome since version 32, Firefox since 65, Edge since 18, Safari fully since version 16. Even that list tells a story: Safari held out for a decade and only shipped full support in 2022. Internet Explorer never supported it at all.

And that's just browsers — the part of the world that moves quickest. Beyond them sits the long tail: government upload portals, print shops, embroidery and print-on-demand services, old desktop software, photo kiosks, HR systems, email clients rendering attachments, that one internal tool at work built in 2013. Systems that were built when "image" meant JPG or PNG, and that validate file extensions accordingly.

So you live in the gap. The modern web hands you WebP; the rest of your life demands JPG. The conversion is the bridge, and you want it to be free, instant, and private.

First, a cheat: you might not need JPG at all

Half the time the requirement isn't "JPG" — it's "not WebP." Job portals, editors, and forms almost universally accept PNG too. If whatever you're uploading to takes PNG, converting WebP to PNG is just as good, sometimes better (no extra quality loss, transparency survives).

Keep that in mind through the methods below. Some tools naturally output PNG. That's fine. The mission is compatibility, not a specific extension.

Convert WebP to JPG on a Mac

If your Mac runs a recent version of macOS, Preview opens WebP files directly. From there it's the standard export dance, straight from Apple's Preview guide:

  1. Open the .webp file in Preview.
  2. Choose File > Export.
  3. Click the Format pop-up menu and pick JPEG.
  4. Drag the quality slider — keep it high, more on that below.
  5. Save.

Preview's export menu covers HEIC, JPEG, JPEG 2000, OpenEXR, PDF, PNG, and TIFF, and Apple notes you can Option-click the Format menu for extra formats. One image, five seconds, nothing uploaded.

Convert WebP to JPG on your phone

This is where the problem actually lives. You saved the image on your phone, you need to re-upload it from your phone, and iOS gives you no obvious "convert" button.

That friction is exactly what ConvertApps exists to remove. Pick the WebP files — one or a whole batch — choose JPG or PNG, done. The conversion runs entirely on the device. No account, no server, no "your file will be deleted after 24 hours, trust us." Airplane mode works fine, which is the honest proof that nothing leaves your phone.

That on-device detail isn't a nice-to-have. Random converter websites are the default answer Google gives you, and they're the worst option on the table — I laid out the whole case in stop uploading your files to random sites.

The command-line route (free, official, batch-friendly)

Google ships free tools with libwebp, its own WebP library. The decoder is called dwebp, and Google's documentation is refreshingly clear about what it does: it decompresses WebP into PNG (default), PAM, PPM, PGM, BMP, or TIFF.

dwebp picture.webp -o picture.png

Note what's missing from that output list: JPEG. dwebp gives you a PNG, not a JPG. Remember the cheat above — PNG is usually all you needed anyway. If you genuinely must have JPG, run the PNG through Preview or any image tool afterward.

Wrap it in a shell loop and you can convert a folder of hundreds of WebP files while your coffee brews. For developers and power users, this is the cleanest possible pipeline: official tool, local machine, scriptable.

What about Windows?

Honest answer: it depends on which Windows and which app, and that inconsistency is the whole WebP story in miniature. Your browser on Windows handles WebP perfectly. The app you're trying to feed the file into might be from an era before the format existed.

Two routes always work:

  1. dwebp, exactly as above — Google's tools run fine on Windows, and you get a clean PNG out.
  2. The browser as translator. Open the WebP in your browser (which understands it), then use any print or export path from there to get to a format your target app accepts.

If a Windows image editor on your machine opens the file, use its own Save As and you're done. Just don't be surprised when one app opens it and the next one doesn't. That's not you. That's the gap.

Last resorts (know them, rarely use them)

The screenshot. Open the WebP, screenshot it, use the screenshot. It works, but your image quality is now capped at your screen resolution, and you've probably got status bars to crop. Emergency use only.

Re-saving from the browser. Some sites keep JPG originals and only serve WebP to browsers that advertise support, so occasionally copying an image URL and editing the extension works. It's a lottery. Don't build a habit on it.

What you lose in the conversion — and how to lose less

Here's the honest part most guides skip.

Most WebP files on the web are lossy — compressed by throwing away detail, same idea as JPEG. When you convert lossy WebP to JPG, you compress an already-compressed image. Each generation loses a little more. Do it once at high quality and nobody will ever see the difference. Do it five times at medium quality and the artifacts start crawling.

Three rules keep you safe:

  1. Convert once. Keep the original WebP until you're sure you're done with it.
  2. Export at high quality. On Preview's slider or any quality setting, stay near the top. The size savings from crushing quality are not worth it for a file you're uploading once.
  3. Transparency means PNG, not JPG. JPEG has no transparency. Convert a transparent WebP logo to JPG and the transparent parts become a solid background. If the image has transparency, PNG is the only correct answer.

The flip side: if you run a website

Quick word to the site owners reading this, because you're the ones creating the problem for everyone else — and rightly so.

Serve WebP. The bandwidth math is too good to ignore, and every modern framework or CDN will convert automatically. But keep two things in mind. First, keep your originals; WebP should be a delivery format, not your only copy. Second, remember that people save your images to reuse them — product photos end up in comparison sites, recipe images end up on shopping lists, logos end up in slide decks. Every one of those users hits the exact wall this article solves. You won't change your setup for them, but at least understand the trade you're making: your bandwidth bill versus their five seconds of friction.

The web made its choice. Users just need the exit ramp.

The decision table

Use this today:

Situation Best move
One WebP on a Mac Preview > File > Export > JPEG
WebP files on iPhone ConvertApps — batch, offline
A whole folder, any OS dwebp in a loop > PNG output
Target accepts PNG Convert to PNG, skip JPG entirely
Image has transparency PNG. Always PNG.
No tools, 30 seconds, low stakes Screenshot it
Sensitive image, any platform Anything offline — never an upload site

One more scenario worth naming: the batch you didn't plan for. You saved thirty product images for a comparison, or a folder of reference pictures for a project, and every single one is WebP. Converting them one by one in Preview is a lesson in patience you didn't sign up for. That's the moment the dwebp loop or a batch-capable converter pays for itself — the difference between a two-minute task and a lost evening.

FAQ

Why do images I save from websites end up as WebP?

Because the site converted them to save bandwidth. Google's format compresses 25-34% smaller than comparable JPEGs, pages load faster, and hosting costs drop, so modern sites serve WebP to every browser that supports it — which is about 96% of them. The original JPG you imagine you're saving often no longer exists on the server.

Is WebP better than JPG?

For websites, mostly yes — smaller files at similar quality, plus transparency and animation support that JPEG never had. For compatibility with the rest of the world — printers, portals, old software — JPG still wins, which is exactly why this conversion exists. "Better" depends on whether the file is going to a browser or to everything else.

Does converting WebP to JPG lose quality?

Slightly, yes — JPEG re-compresses the image, and most WebP files were already lossy. Converted once at a high quality setting, the loss is invisible in practice. Avoid repeated convert-edit-convert cycles, and never convert transparent images to JPG (the transparency is discarded).

How do I convert WebP to JPG without uploading my image anywhere?

On a Mac, Preview's File > Export does it locally. On any OS, Google's free dwebp tool decodes WebP on your machine. On a phone, an on-device converter like ConvertApps does it without a network connection at all. Every one of these works with Wi-Fi off — that's the test.

Can I stop websites from giving me WebP in the first place?

Not really. The server decides what to send, and most send WebP to any browser that accepts it. Extension tricks and URL editing work on a minority of sites. The reliable fix is downstream: a conversion habit that takes five seconds and runs on your own device.

The takeaway

The web optimized for its own bandwidth, not for your upload forms — WebP is permanent, so make the fix permanent too: a five-second, on-device conversion with Preview, dwebp, or ConvertApps, and never a stranger's upload button. The full argument for keeping conversions offline is here: file converters, privacy, and why offline wins.

The format war isn't your problem once the fix lives on your own device.

— Dolce