How to convert WebP to JPG on Mac (batch, offline, 2026)

You right-clicked an image on a website, chose “Save Image,” and got a file ending in .webp. Now the thing you saved it for — dropping it into a slide deck, uploading it to a print service, attaching it to a listing, opening it in an older version of Photoshop — refuses to take it. The site handed you a format the rest of your workflow doesn’t speak.

This has become the single most common “why won’t this image open” complaint on the Mac, because the web quietly switched. Chrome, Shopify, Etsy, Wikipedia, WordPress with any modern optimization plugin — they all serve WebP now, so “save image from the web” increasingly means “get a WebP whether you wanted one or not.”

This guide covers every way to convert WebP to JPG on a Mac — the built-in free tools, the command line, and the one-drag batch route — plus the two gotchas (transparency and animation) that produce ugly results if you don’t see them coming.

What WebP is, and why your tools reject it

WebP is Google’s image format, built for the web: it compresses roughly 25–35% smaller than an equivalent JPG, and unlike JPG it also supports transparency and animation. For a website serving millions of images, that’s real bandwidth money, which is why so many sites converted their catalogs.

The catch is on the receiving end. Browser support is universal, but support everywhere else still isn’t: older versions of Photoshop and Lightroom, plenty of print kiosks and photo-book services, corporate upload portals, Microsoft Office on some Windows machines, embroidery and laser-cutter software, government form uploads. When any of those is the destination, the fix is the same — hand it a plain JPG, the one image format that opens literally everywhere.

The good news: macOS reads WebP natively (it has since Big Sur, and Zumkor’s macOS 14 baseline is well past that), so your Mac can already do this conversion without installing anything. You just need to know where the converters are hiding.

Can you avoid saving WebP in the first place?

Sometimes, and it’s worth knowing the tricks, because the best conversion is the one you skip.

Many sites don’t store WebP at all — they store JPG or PNG and let a CDN convert on the fly, serving WebP only to browsers that advertise support. That has two useful consequences. First, the same image sometimes comes down as a JPG in a different browser: if a site hands Chrome a WebP, try the same page in Safari, which is more conservative about what it accepts on some sites. Second, the URL itself sometimes gives it away — if the image address ends in .jpg but the file saves as .webp, or the URL has a query string like ?format=webp or &fm=webp, editing the URL in the address bar and reloading can fetch the original JPG directly.

There’s also the clipboard route for a quick one-off: right-click the image, choose Copy Image (not Copy Image Address), and paste directly into the destination — Pages, Keynote, a mail message, an image editor. The clipboard carries decoded bitmap data, so the WebP wrapper never touches the receiving app.

All three tricks are hit-or-miss, which is why they’re a sidebar and not the guide. When they fail — or when you already have a folder of forty .webp files — you convert. Here’s how, from lightest to heaviest duty.

First: skip the web converters

Googling “webp to jpg” surfaces a wall of free converter websites. Don’t use them, for two reasons.

First, it’s backwards: you’re uploading a file to a remote server, waiting, and downloading it again to perform an operation your Mac completes locally in a fraction of a second. Second, everything you upload is now on someone else’s server, and free converter sites are ad-funded precisely because your files and attention are the product. For a random meme it hardly matters; for product photos, client work, or anything private, it does.

Everything below runs entirely on your Mac, offline. Nothing leaves the machine.

Method 1: Preview (best for one or two images)

Preview opens WebP files like any other image, and exporting is one dialog:

1. Double-click the .webp file — it opens in Preview.
2. Choose File → Export.
3. Set Format to JPEG.
4. Set the Quality slider — 80–90% is visually identical to the source and much smaller than 100%.
5. Click Save.

That’s it for a single file. Preview can also handle a small batch: select several WebP files in Finder, open them all in Preview at once, press ⌘A in the thumbnail sidebar to select every image, then File → Export Selected Images and pick JPEG in the options. Workable up to a couple dozen files; past that the sidebar-selection dance gets old.

Method 2: Finder’s Quick Action (fastest free batch)

The converter most Mac users never find is in the right-click menu:

1. In Finder, select the WebP files — ⌘-click a handful, or ⌘A for a folder’s worth.
2. Right-click the selection.
3. Choose Quick Actions → Convert Image.
4. Set Format to JPEG, choose an image size (Actual Size keeps original resolution), and untick “Preserve Metadata” if you don’t want it carried over.
5. Click Convert to JPEG.

Fresh .jpg copies appear next to the originals, originals untouched. For a one-off batch of saved web images this is the best free answer on the platform.

Its limits are the same ones it’s always had: output is restricted to JPEG, PNG, or HEIF; there’s no precise quality percentage, just Actual Size and three smaller presets; and there’s no renaming, so you inherit whatever chaotic filenames the websites gave you.

Method 3: sips in Terminal (scripted batches)

macOS ships with sips, a command-line image processor that reads WebP on any modern system.

One file:

sips -s format jpeg image.webp --out image.jpg

A whole folder:

cd ~/Downloads/webp-images
for f in *.webp; do
  [ -e "$f" ] || continue
  sips -s format jpeg "$f" --out "${f%.*}.jpg"
done

With an explicit quality level (0–100):

sips -s format jpeg -s formatOptions 85 image.webp --out image.jpg

sips is fast, free, and scriptable — ideal if WebP conversion is one step in an automated pipeline. It’s also unforgiving: no preview, no undo, and a mistyped --out can clobber a file. Reach for it when you’d be writing a script anyway.

Method 4: Zumkor (drag the folder, done)

If stray WebP files are a recurring irritation rather than a once-a-year event — you save product images for listings, collect reference art, prepare web assets for clients, or just download a lot of images — this is the exact chore Zumkor exists to delete (it needs macOS 14 or later on an Apple silicon Mac — any M-series machine).

1. Open Zumkor and drag in the WebP files, or the whole folder they’re sitting in.
2. Pick JPG as the output format.
3. (Optional) Pick a resize preset — “Email-friendly” (1600 px) or “Web small” (1280 px) if these are headed for email or a document — and flip on Strip personal data if the images shouldn’t carry metadata.
4. Click Convert.

Every file converts in one pass, on your Mac, with nothing uploaded — it works with Wi-Fi off. And because Zumkor is free for 7 days and then a one-time $19.99 purchase, not a subscription, the math is simple: it costs less than one month of most “pro converter” subscriptions and you keep it forever.

The honest trade-off, same as always: for one image, once, Preview is free and already open. Zumkor earns its keep when the folder has forty files in it, when you also need the reverse trip — JPG or PNG to WebP for a website, or when the same afternoon involves HEIC photos and a video that’s too big to send and you’d rather have one tool than five.

The two WebP gotchas

Two properties of WebP don’t survive the trip to JPG, and both can bite silently.

Transparency. WebP supports transparent backgrounds; JPG does not. Convert a logo or a product cut-out with a transparent background to JPG and the transparency gets flattened — typically to white. If white is fine (it usually is for product shots), proceed. If you need the transparency to survive, convert to PNG instead — every method above offers PNG in the same menu (the WebP-to-PNG guide walks the same tools in that direction), and Zumkor writes PNG (and HEIC, TIFF, WebP, and AVIF) alongside JPG.

Animation. WebP can be animated, like a GIF. JPG is a still format, so converting an animated WebP gives you a single frame — usually the first — and the motion is gone. There’s no way around that in a still format; if a file seems to have “lost” its animation, this is why.

Neither of these is a tool failure. They’re format physics: you’re moving from a richer container to a simpler, more compatible one, and that’s precisely the point of the conversion.

Getting the output right

• Quality. JPG is lossy, and WebP sources are often already compressed. Exporting at 100% inflates the file for nothing; 80–90% is the sweet spot. Below ~60%, gradients and flat-color areas start showing blocky artifacts.
• Don’t round-trip repeatedly. WebP→JPG→edit→JPG stacks lossy compression on lossy compression. Convert once, keep the output, and go back to the original WebP if you need a fresh copy.
• Resolution. Images saved from the web are sometimes enormous. If the JPG is bound for email or a document, downsizing the long edge cuts the size dramatically with no visible difference on screen. Preview’s export can’t resize in the same step; the Quick Action has coarse size presets; Zumkor’s “Email-friendly” (1600 px) and “Web small” (1280 px) presets resize right in the conversion pass.
• Metadata. Most web-saved WebP files carry little metadata, but images that came off a camera or through an export chain can. If the JPG is going anywhere public, strip it — the Quick Action’s checkbox or Zumkor’s one-click strip both work.

While you’re at it: AVIF is the next one coming

WebP was the first web-native format to leak into everyday downloads; AVIF is the second. It compresses even harder than WebP, big image CDNs already serve it, and files ending in .avif are starting to show up in Downloads folders the same way .webp did five years ago. The playbook is identical — macOS 14 reads AVIF natively, Preview exports it to JPEG, and Zumkor both reads and writes AVIF alongside WebP. If you build for the web rather than just save from it, that write direction matters: converting your JPG and PNG assets to WebP or AVIF is the same drag-and-drop in the other direction, and it’s how you make your own pages faster instead of merely coping with everyone else’s.

Bottom line

• One or two images: Preview → File → Export → JPEG. Ten seconds, free.
• A folder, occasionally: select all in Finder → right-click → Quick Actions → Convert Image. The best free batch option.
• Part of a script: a sips loop.
• A recurring chore, or mixed with other formats: Zumkor — drag the folder, pick JPG, everything converts offline in one pass, and the same app handles the return trip to WebP plus your audio and video.

Whatever you pick, keep it on the Mac. Uploading images to a converter site to fix a format your own machine already reads natively is the one genuinely bad option on the list.

And if the file that won’t open is a video instead of an image, the same logic — and the same app — applies: see how to convert MKV to MP4 on Mac.

FAQ

Why do images save as WebP instead of JPG?

Because the website chose it: WebP files are 25–35% smaller than equivalent JPGs, so sites and CDNs serve them to save bandwidth, and “Save Image” hands you whatever the server sent. Sometimes the site stores an original JPG behind a CDN conversion — trying Safari instead of Chrome, or trimming a ?format=webp query from the image URL, occasionally fetches it directly.

Does converting WebP to JPG lose quality?

Slightly, in principle — web-saved WebP is almost always lossy, JPG always is, and re-encoding discards a little data — but at 80–90% JPG quality the change is invisible. The real risks are structural: JPG flattens WebP transparency (usually to white; convert to PNG if you need it kept) and reduces an animated WebP to a single still frame. Convert once and keep the output rather than round-tripping.

How do I batch convert WebP files to JPG on a Mac?

For a free one-off, select the files in Finder, right-click, and use Quick Actions → Convert Image → JPEG. For scripted pipelines, loop sips -s format jpeg in Terminal. For a recurring chore, drag the folder into Zumkor, pick JPG, and convert everything offline in one pass — with resize presets and metadata stripping applied in the same step.