Why Images Download as WebP Instead of JPG — And How to Fix It

Your image is downloading as a .webp file because the website is serving a WebP version of the image to your modern browser. This is intentional on the website's end — they're using WebP because it's smaller and faster to deliver. Your browser requested an image, the server sent the most efficient version it had, and that version was WebP.

To get a JPG, you need to convert the WebP file you downloaded. Here's how, and why this happens in the first place.

Why This Happens: Websites Automatically Serve WebP

When your browser loads a webpage, it tells the server which image formats it supports via an Accept header. Modern browsers (Chrome, Firefox, Edge, Safari) include WebP in that list. The server sees that and responds with the WebP version of the image instead of the JPG, because WebP is smaller and loads faster.

This is transparent when viewing the image on the page — you just see the image. But when you right-click and save, or right-click "Open image in new tab," you get the WebP version that was actually delivered to your browser.

Some sites use CDN services like Cloudflare, Imgix, or Shopify's image CDN that convert images to WebP on the fly — the original on the server might be a JPG, but what you get in your browser is always WebP.

Three Ways to Get the JPG You Actually Want

Option 1: Convert the WebP file you downloaded (easiest)

Download the .webp file normally, then use the WildandFree WebP to JPG converter to convert it. Drop the file, download the JPG result. The entire process takes under 30 seconds and the file never leaves your device. This is the fastest approach for most situations.

Option 2: Request the original URL without WebP

Some CDN services allow you to request the original format by modifying the URL. For example, if the image URL contains format=webp or .webp in the query string, removing that parameter sometimes returns the original JPG. This is site-specific and unreliable — try Option 1 if this doesn't work.

Option 3: Use a browser extension (Chrome-specific)

Extensions like "Save image as JPG" (available in the Chrome Web Store) can intercept image downloads and convert them to JPG on the fly. Useful if you frequently need to save images from sites that always serve WebP. Note that installing browser extensions gives them access to your browsing — read the permissions carefully before installing.

Sell Custom Apparel — We Handle Printing & Free Shipping

When the Original JPG Doesn't Exist Anymore

Some websites convert all uploaded images to WebP at upload time and delete the JPG originals. Platforms like Cloudinary and some e-commerce CMSs do this. If that's the case, there's no JPG to retrieve — the WebP is the source of truth for that image on that server.

Converting the WebP to JPG is still a valid solution in this case. You'll get a JPG that looks identical to the WebP on screen. The technical difference is that you've converted from WebP (which was potentially converted from the original JPG at some point) — so you've gone through two lossy conversions. For most practical uses — printing, editing, inserting into a document — this is fine. For professional archival or print production, try to get the source file directly from the person or organization that owns it.

Specific Case: Saving JPG from Stock Photo Sites

Stock photo sites like Shutterstock, Getty, Adobe Stock, and Unsplash serve preview images as WebP to reduce bandwidth. When you right-click and save the preview, you get a WebP file.

For purchased images from stock sites, the download you receive (after payment or using a license) is always the original high-resolution file in JPG, TIFF, or PNG. If you're saving a preview watermarked image for reference, the WebP is fine to convert to JPG for internal use — just be careful about using watermarked images for anything beyond reference.

Shutterstock specifically uses a CDN that serves WebP previews. The actual purchased download comes as full-quality JPG — no conversion needed after purchase.

The Fastest Fix: Convert Your WebP File to JPG

Whatever the reason your image ended up as WebP, converting it back to JPG is fast:

1. Go to the WildandFree WebP to JPG converter
2. Drop your .webp file onto the drop zone (or click to select it)
3. Adjust quality if needed (85 is the default)
4. Click download — your JPG is ready in seconds

No upload, no account, no file size limit. The conversion happens in your browser. For a batch of WebP files you've downloaded, drop them all at once — the tool converts each one and gives you individual download buttons.

If you're dealing with the opposite problem — you have JPGs and want to serve WebP versions of them on your website — use the JPG to WebP converter to pre-convert your uploads.

Frequently Asked Questions

Why does my photo save as .webp when I right-click "Save image as" in Chrome?

Chrome tells websites it supports WebP, and the server sends a WebP version. When you right-click to save, you get whatever the server delivered — which is WebP. Convert the .webp file to JPG using the WebP to JPG converter tool after saving.

How do I make my browser download JPG instead of WebP?

You can't easily change this behavior at the browser level without extensions — the server decides which format to send based on your browser's Accept header. The practical solution is to download the WebP and convert it to JPG after.

Is a WebP file I converted to JPG the same quality as the original JPG?

Close but not identical. Each lossy conversion step introduces tiny artifacts. A WebP converted to JPG at quality 85 is very close to the original JPG quality for most practical purposes (viewing, printing, editing). For professional archival, try to obtain the original source file instead of re-converting.

Can I stop a website from sending me WebP images?

Some browser extensions let you modify Accept headers to remove WebP from your browser's supported format list, which would make servers fall back to JPG. This is technically possible but slows down every page you visit because you receive larger JPG files instead of smaller WebP. It's not a practical general solution.