What to do with .webp images on a Mac

You save a picture from a website, and instead of the .jpg you expected, the file that lands in Downloads ends in .webp. Drag it into an older copy of Word, upload it to a form built for photos, or open it in an app nobody has updated in a while, and nothing happens. No preview, no upload, sometimes not even an error, just silence.

None of that means the website did something wrong, or that the picture is broken. WebP is a real, widely used image format, and the site gave it to you on purpose because it is smaller and faster to load than the alternatives. The task here is not to fight the format. It is to get one image, or a folder of them, into something every app on your Mac already understands, which takes a minute once you know where to look.

Why did the site give you a .webp file?

WebP is a format Google built specifically to make web pages faster, and the numbers behind it are the reason so many sites switched. Google's own comparison puts lossless WebP images at 26% smaller than an equivalent PNG, and lossy WebP at 25 to 34% smaller than a comparable JPEG at the same visual quality, with transparent images running up to three times smaller than PNG. A page carrying dozens of product photos or thumbnails loads noticeably faster in that format, which matters directly for anyone on a slow connection and indirectly for the site's own search ranking, since page speed is part of how search engines judge a page.

That is why WordPress, Shopify and most image delivery services now serve WebP by default, particularly to phones. It is a genuine engineering improvement, not a website being difficult, and converting every image you own to PNG on principle just undoes the saving and leaves you with bigger files for no real benefit. The honest position is that WebP earns its place. The problem is narrower than the format itself: getting the odd file into an app that has not caught up yet.

Can your Mac actually open a .webp file?

On any reasonably current Mac, yes, and directly. Preview and Quick Look have opened WebP files natively since macOS Monterey, released in 2021. Double-click a .webp file in Finder and Preview shows it exactly like a jpg or png. Select it and press the Space bar, and Quick Look previews it the same way, full size, no separate viewer needed.

If nothing opens at all, the most likely cause is an older macOS. On Big Sur or Catalina, pressing Space on a .webp file shows only the filename and file size, with no picture, because those versions predate native support. Check your version under the Apple menu, About This Mac. Anything from Monterey onward should show the image immediately, no extra software required.

Converting one image in Preview

Preview can open a WebP file, but it cannot save one back out. That makes exporting to something else the natural first move, and it takes four steps.

1. Open the .webp file in Preview. Double-click it, or right-click and choose Open With, then Preview.
2. Choose File, then Export. A save panel appears with a Format dropdown.
3. Pick a format from the dropdown. Preview's own export options are PNG, JPEG, TIFF, HEIC, JPEG 2000 and OpenEXR, confirmed on Apple's Preview user guide. WebP is not among them, which is exactly why this step exists: Preview reads the format but does not write it.
4. Click Save. The converted copy appears at the location you chose, and the original .webp file is untouched.

Converting a whole folder at once

Doing that once is easy. Doing it for forty files is where the two free batch routes matter.

The simpler one lives in Finder. Select every .webp file in the folder, either Command-A for all of them or Command-click for a subset, then right-click and choose Quick Actions, then Convert Image. Apple's own guide to Quick Actions describes it as converting a selection to another format or a smaller size in one pass, and it has shipped as a built-in Finder action since Monterey. Pick a format in the dialog that appears, and Finder converts the whole selection at once.

The other route is Terminal, using sips, the image tool macOS has included since Mac OS X. For a single file:

sips -s format png photo.webp --out photo.png

For every .webp file in a folder, open Terminal, move into that folder, and run:

for f in *.webp; do sips -s format png "$f" --out "${f%.webp}.png"; done

That one line steps through each .webp file in the current folder and writes out a matching .png alongside it. Swap png for jpeg in both commands for smaller files instead. One limit worth knowing: sips can read a WebP file but cannot write one, so this only runs in one direction, out of WebP and into something else, never back. For the ordinary problem of an app that refuses a .webp file, that is the only direction that matters.

Which apps still trip over it

Preview, Quick Look, Safari, Photos and current Photoshop all handle WebP without complaint now. What still catches people out is anything running an older version: a copy of Microsoft Office installed before its WebP support arrived in the early 2020s, a print lab or stock-photo upload form with a hard-coded list of accepted extensions, or any app that has simply gone a couple of years without an update. When an upload silently rejects a .webp file, that is almost always the form's own allow-list talking, not a fault in your Mac or the picture itself.

The bit that actually loses images

Converting solves the will not open problem. It does not solve the other one, which is usually the bigger cost: the file lands in Downloads under a name like 8f3a2c19.webp or download (4).webp, and once thirty more files land on top of it, it is gone in every practical sense, format aside. That is a filing problem, not a format problem, and it is worth treating as a separate one, covered in organising images without a folder tree.

Muse displays .webp files directly, alongside jpg, png, heic and the rest, so there is no conversion step before a picture can go into a library. It will not solve the apps above that still reject WebP outright, the routes in this article cover that. What it solves is the naming problem: every image kept its source and a note beside it, in one searchable place, instead of scattered through Downloads under a filename nobody chose.