You right-clicked an image on a web page, chose Save image as, and got a file ending in .webp. Now Photoshop refuses it, Word will not insert it, and the print shop's upload form says the file type is not supported. The picture looked perfectly normal in your browser a moment ago.

Nothing is wrong with the file. It is in a format your browser understands and most other software does not. Here is why that happens, why the obvious fix makes it worse, and what to do instead.

What WebP actually is

WebP is an image format Google released in 2010 and pushed hard from about 2014 onwards. Its selling point is size: a WebP file is typically 25 to 35 percent smaller than a JPG of the same visual quality, and it can do something JPG cannot, which is store transparency.

For anyone running a website that is a genuinely good deal. Images are usually the heaviest thing on a page, page speed affects search rankings, and Google made the format easy to adopt. So sites switched. Today a large share of images served on the open web are WebP, and Google Images serves WebP in its own results.

The catch is that adopting a format on the serving side and supporting it on the receiving side are different problems. Every current browser reads WebP. The rest of the software on your computer mostly does not, because most of it was designed before WebP existed and adding a new image decoder is not a small change.

Why your software refuses it

The specific answer depends on what you are using, and the patterns are worth knowing because they tell you whether to wait for an update or just convert the file.

Windows. Windows 11 opens WebP in Photos without any help. Windows 10 is the awkward one: later builds handle it, earlier ones do not, and whether it works can depend on whether a particular codec package was ever installed. This is why one person insists WebP opens fine on Windows and the next person swears it does not. They are both telling the truth about their own machine.

Photoshop. Native WebP support arrived in version 23.2, released in early 2022. Before that you needed a third-party plugin dropped into the plugins folder. If you are on an older perpetual licence rather than a current Creative Cloud subscription, you do not have it and no update is coming.

Microsoft Office. Word, PowerPoint and Excel will not insert a WebP. There is no setting to enable and no plugin worth hunting for. This catches people out constantly, because dropping an image into a document is such an ordinary thing to do that it does not occur to anyone it might fail.

Print services and upload forms. Photo printers, business card services, job application portals and council forms overwhelmingly accept JPG and PNG only. Their validation often rejects the file without explaining why, or worse, accepts it and fails silently later.

Older phones and tablets. Android has handled WebP for years. iOS gained proper support in iOS 14. An older device may show you a grey box where the picture should be.

The fix that does not work

The first thing almost everyone tries is renaming the file. Change photo.webp to photo.jpg and the problem should go away, because the extension is what tells the computer what the file is. Right?

No, and it is worth understanding why, because the same misunderstanding causes a lot of wasted time.

The extension is a label, not the contents. Inside every image file is a sequence of bytes arranged according to the rules of a particular format, and the first few of those bytes identify which format it is. A JPG begins with the bytes FF D8 FF. A WebP begins with the letters RIFF, then four bytes of length, then the letters WEBP.

When Photoshop opens a file it does not trust the extension. It reads the start of the file and works out what it is really dealing with. Rename a WebP to .jpg and Photoshop sees RIFF where it expected FF D8 FF, concludes the file is damaged, and tells you so. You have not converted anything. You have given a file a misleading name, and the error message you get now is less helpful than the one you got before.

Converting means re-encoding: decoding the image back to raw pixels and writing those pixels out again following JPG's rules. That is real work, and it is what any genuine converter does.

AVIF is the same story, one format later

If you have started seeing .avif files, that is the sequel. AVIF compresses even better than WebP, browsers adopted it from around 2020, and desktop software is once again several years behind. Everything above applies, with the support thresholds shifted later: Chrome 85, Firefox 93, Edge 85, Safari 16.4.

There will be another one after AVIF. The gap between what browsers read and what everything else reads is a permanent feature of the web, not a temporary glitch, which is why knowing how to convert is more useful than waiting for support to arrive.

Converting it properly

You have three sensible options, and which one suits you depends on how often this comes up.

Re-save it from software that already reads it. On Windows 11, open the file in Paint and use Save as → JPEG. On a Mac, open it in Preview and use File → Export. This costs nothing and works for a single file. It becomes tedious at about the third one.

Use a browser-based converter. Since your browser already decodes WebP and AVIF, a web page can do the conversion on your own machine without sending the image anywhere. Our WebP to JPG converter works this way: drop in up to fifty files, pick JPG or PNG, and download them individually or as one ZIP. Nothing is uploaded, which matters if the images are client work, documents or anything you would not post publicly.

Install a codec or plugin. Worth it only if you are dealing with WebP constantly and need it inside one specific program. For occasional use it is more effort than converting.

The detail most converters get wrong

If you convert a logo with a transparent background to JPG and end up with a black rectangle behind it, you have met the one real trap in this process.

WebP, AVIF and PNG can all record transparency: each pixel carries an extra value saying how see-through it is. JPG has no such thing. Every JPG pixel is fully opaque, with no exceptions.

So when transparency meets JPG, something has to fill the transparent areas, and the converter has to decide what. The usual implementation draws the image onto a blank canvas and encodes the result. In most graphics systems a blank canvas is transparent black, and when the transparency is discarded what remains is the black. Your logo arrives sitting in a dark box.

A converter that handles this properly fills the canvas with a colour first, normally white, so the discarded transparency is replaced by something sensible. Better still, it lets you choose the colour, because white is wrong if the logo is going onto a dark background.

The alternative is to not discard the transparency at all. If the image has a transparent background you actually need, convert to PNG instead of JPG. PNG is universally supported, keeps transparency intact, and is the right choice for logos, icons, screenshots and anything containing text or sharp edges. JPG remains the better choice for photographs, where its compression is designed for the kind of detail photographs contain.

Why the JPG comes out bigger

A common surprise: you convert a 180 KB WebP and get a 260 KB JPG. Something has gone wrong, surely?

No. That is the trade you just made. WebP and AVIF are more efficient formats, so the same picture needs fewer bytes in those formats than in JPG. Converting to a less efficient format at comparable quality produces a larger file. You exchanged some bytes for the ability to open the thing in Word.

If the size matters, drop the quality setting. The difference between quality 90 and quality 80 is hard to see on most images at normal viewing sizes, and it will often bring the JPG back under the original. Stay at 90 or above for anything you intend to edit further or print, because every re-encode of a JPG throws away a little more detail permanently.

A note on metadata

Converted files usually do not carry the original EXIF metadata: camera model, exposure settings, the date the photo was taken, and any GPS coordinates recorded at the time.

That is often exactly what you want. Stripping location data before publishing a photo is a sensible habit, and most people are surprised how much is embedded in an ordinary phone picture.

It is a problem if you rely on the capture date to sort an album, because the converted copies will be dated today. If that matters, keep the originals alongside the converted versions rather than replacing them.

Short version

A WebP file that will not open is not broken. It is a modern format your browser reads and your other software does not, and the number of programs in the second group is shrinking slowly rather than quickly.

Renaming it achieves nothing, because programs read the bytes rather than the extension. Converting re-encodes the picture and fixes it properly. Choose JPG for photographs, PNG when you need to keep a transparent background, and check the result if the image had transparency, because a black rectangle where the background should be is the sign of a converter that skipped a step.

If you have a folder of them to deal with, the WebP to JPG converter handles fifty at a time in your browser without uploading anything. It converts AVIF in the same batch, which will save you looking this up again in a year.