A .webp is a modern image format Google created to make web pages load faster — it produces smaller files than JPG or PNG at similar quality, which is why so many sites now serve it. The problem is that plenty of desktop apps, upload forms and older software still refuse to accept it. The fix is to convert it: WebP to JPG for photos, or WebP to PNG when you need to keep a transparent background. Both run in your browser, so the image is never uploaded.
Why you ended up with a .webp file
You right-clicked an image on a website, chose "Save image as…", and got a file your computer treats as a stranger. That is not a mistake on your part. Most large sites now serve WebP because it is typically 25-35% smaller than an equivalent JPG (per Google's own WebP figures), and page weight is one of the things Google measures. Your browser understands it perfectly, which is why the picture looked fine on the page — the trouble only begins once the file leaves the browser.
What actually breaks
- Upload forms — job portals, government sites, marketplaces and older CMSes frequently accept only JPG and PNG, and reject .webp outright.
- Desktop software — older versions of Photoshop, Office and various photo viewers cannot open it without a plugin.
- Printing — print shops and photo kiosks generally expect JPG.
- Sharing — email the file to someone on an older machine and they may not be able to open it at all.
Renaming the file to .jpg does not work, and it is worth being clear about why. The extension is only a label; the bytes inside are still WebP-encoded. Software reads the actual contents, sees a WebP header, and either errors or shows a broken image. You have to genuinely re-encode the picture.
Convert it in your browser
- For photographs and anything going into an upload form, use WebP to JPG. JPG is the most universally accepted image format there is.
- If the image has a transparent background — a logo, an icon, a cut-out product shot — use WebP to PNG instead. JPG cannot store transparency and will fill it with a solid colour.
- Going the other way, to make your own site faster, JPG to WebP and PNG to WebP will shrink your images significantly.
The conversion happens on your own device using the browser's image engine, so the file is never uploaded to a server. That is worth caring about more often than people think — the images that need converting are frequently screenshots of documents, receipts, or ID photos saved from a portal. It is free, has no sign-up, no daily cap, and works with your Wi-Fi switched off.
Which format should you actually keep?
Use WebP when you control a website and want it to load quickly — every modern browser supports it, and the file-size saving is real. Use JPG when the image has to travel: an upload form, a print shop, a colleague on unknown software. Use PNG when you need transparency or pixel-sharp edges, such as logos, icons and screenshots of text. There is no single best format, only the right one for where the file is going next.
Honest limitations
Both WebP and JPG are lossy formats, so converting between them re-encodes the picture. On a normal photo you will not see the difference, but do not repeatedly convert, edit and reconvert the same image — the losses accumulate. Converting a WebP to JPG will usually produce a noticeably larger file, because you are giving up WebP's better compression in exchange for compatibility, and that is the trade you are making on purpose. Transparency is silently lost when you convert to JPG, so if the original had a cut-out background, go to PNG instead.
If the converted image ends up too large for an upload limit, you have options: reduce the quality on export, or — if the destination wants a document rather than a picture — bundle the images into a single file with Images to PDF and compress that instead. As always, every step of that runs on your machine.