2026-08-21

Why right-click-save gives you a .webp file — and how to turn it into a JPG or PNG

You right-click a photo, hit "Save image as…", and the file that lands in your Downloads folder is something.webp — a format you never asked for, and one that the form, app, or person you wanted to hand the image to may promptly refuse. It feels like a glitch. It isn't: it's the modern web working exactly as designed, and once you see the mechanism, both the "why" and the fix take about a minute each.

WebP is the web's format — on purpose

WebP is an image format Google built specifically for the web, and its pitch is file size. Google's own documentation puts the numbers at: lossless WebP images are 26% smaller than comparable PNGs, and lossy WebP images are 25–34% smaller than comparable JPEGs at equivalent visual quality (SSIM). Smaller images mean faster pages and lower bandwidth bills, so adoption has been steady and real — W3Techs' survey puts WebP on 21.5% of all websites as of August 2026. More than one site in five.

Browser support stopped being a problem years ago. Per caniuse.com, roughly 96% of browsers in global use render WebP: Chrome has had full support since version 32 back in 2014, Edge since 18 (2018), Firefox since 65 (2019), and Safari — the last major holdout — reached full support with Safari 16 in 2022. The only notable never-adopter is Internet Explorer, which is itself retired.

The JPG you wanted often does exist — a machine just decided not to give it to you

Here's the part that makes the whole thing click: in many cases the site owner really did upload a JPG or PNG. What happens next is automated. CDNs and image-optimization layers sit between the site's original files and your browser, and converting to WebP is a checkbox feature for them — Cloudflare's own documentation for its Polish feature describes the option as optimizing "PNG and JPEG images stored in the origin server, and serve them as WebP files to browsers that support this format." Your browser announces WebP support with every image request, so that's what the server hands it. Sites doing it by hand get the same result with HTML: MDN's image-format guide recommends listing a WebP source plus a JPEG/PNG fallback inside a <picture> element, and the browser takes the first format it supports — which, for every current browser, is the WebP.

So why won't anything open it?

Because software outside the browser adopted WebP much later than browsers did — and upload forms are the slowest of all. Photoshop is the canonical example: per Adobe's own documentation, native open/edit/save support for WebP only arrived in Photoshop 23.2, released in February 2022. On anything older, a .webp simply won't open without Google's WebPShop plug-in. And plenty of upload forms — job portals, government sites, listing tools, older CMS installs — still whitelist .jpg and .png literally, so a perfectly valid WebP gets bounced at the file picker regardless of what your own machine can display. The result is the modern-web paradox: the format your browser prefers is the format some other system's form field has never heard of.

The fix: convert it on your own device

NearIMG has dedicated WebP → JPG and WebP → PNG converters, and because every browser decodes WebP natively, the whole conversion runs in your own browser tab — the file never uploads anywhere. Drop the .webp in, download a JPG or PNG. A few practical calls:

• Photos → JPG. For photographic content, JPG is the compatible, compact choice, and NearIMG's quality slider lets you see the output size before you commit. Keep quality high — the WebP you saved was usually lossy-compressed once already, and every lossy re-encode is a new generation of loss.
• Transparency or hard-edged graphics → PNG. JPG has no transparency: convert a transparent-background WebP to JPG and the see-through areas become a flat solid background. PNG keeps the transparency and is lossless, which also suits logos, screenshots, and text-heavy graphics.
• A folder's worth at once. NearIMG takes a multi-file drop and hands a batch back as a zip, so cleaning up a pile of accumulated .webp downloads is one drag, not twenty.

What converting can't do

Being straight about the limits. Converting doesn't recover the site's original JPG — the WebP your browser received is the source you have, and if the optimizer compressed it lossily, that loss is baked in; a conversion changes the container, not history. It also doesn't stop future downloads from being WebP — that's the website's serving choice, not your browser's setting. (You'll find advice about editing a format= parameter out of the image URL to get the original; it genuinely works on some CDNs and does nothing on others, so treat it as a lottery ticket, not a method.) Animated WebP exists too, and a still format can't hold animation — converting one to JPG or PNG gets you a single frame. And if your mystery download is .avif rather than .webp, that's the same serving mechanism at work with an even newer format — same cause, different file extension.

The short version

Sites serve WebP because it's measurably smaller — 25–34% under a comparable JPEG by Google's own numbers — and over a fifth of the web now does it, with CDNs often making the conversion automatically from the JPG the site owner actually uploaded. Your browser is fine with it; your other software and half the web's upload forms may not be. When a WebP needs to be a JPG (photos) or a PNG (transparency, sharp graphics), NearIMG converts it right in the tab it's already sitting in — batch-friendly, quality slider in view, and with no upload involved, because the one thing a format-compatibility errand shouldn't cost you is sending your files to another server.