How to save WebP as JPG comes down to a menu you already have. On Windows, right-click the file, open it in Paint, then File, Save as, JPEG. On a Mac, open it in Preview and choose File, Export with the Format set to JPEG. Both apps have had native WebP support since 2023, no converter needed.
The usual trigger is a right-click save off a website, a screenshot tool, or a phone that hands you a .webp when the form on the other end only takes JPEG. Downloading a dedicated converter for one file is overkill when the save-as-JPG step already lives in apps that are open on your machine. Below is every real method, the one that quietly does not work, and what the format swap costs you. If you want the background on why WebP keeps turning up at all, the guide to WebP and AVIF covers the format itself.
How to Save WebP as JPG on Any Device
The fastest route depends on where the WebP is. If it is already saved on your computer, a built-in app re-encodes it in three clicks. If it is still sitting in your browser, an extension or a copy-paste skips the download entirely. Match the method to your situation and you never install anything.
| Your situation | Best method |
|---|---|
| One WebP already saved to disk | Paint on Windows, Preview on Mac |
| A whole folder of WebP files | Photos on Mac, or the browser tool's batch |
| A web image not downloaded yet | Browser extension or copy-paste |
| You want a visible quality slider | Preview or the browser tool |
Here is each method in full, shortest first.
Use the browser tool for a quality slider or a whole folder
Drop the WebP straight into the WebP to JPG converter, which already has JPG set as the output, and download the result. There is no install, and no signup for files up to 25 MB in batches of up to 30 images, so a folder of product shots or saved graphics converts in one pass. EXIF metadata, the hidden camera and location block a phone writes into a file, gets stripped as the image is rewritten. A free account raises the batch to 100 images a month with a usage dashboard, and Pro is 12 dollars a month flat for 10,000 images, files up to 50 MB, and batches of 100. Paint and Preview each handle a single file well, but neither batches a folder, and Paint gives you no quality control at all.
Save WebP as JPG on Windows with Paint
To save WebP as JPG on Windows with nothing to download, use Paint. Right-click the .webp file, choose Open with, then Paint. Paint has read and written WebP natively since 2023, so once the image is open, go to File, then Save as, and choose JPEG picture from the file-type list (PCWorld). Name it, pick a folder, and save.
Paint applies its own default JPEG quality with no slider, so you trade fine control for speed. If Paint does not list JPEG or refuses the WebP outright, run Windows Update before assuming the file is broken, since native WebP support arrived in that 2023 update and an older installation may not carry it yet.
Save WebP as JPG on Mac with Preview
To save WebP as JPG on Mac, Preview does it built in. Double-click the WebP to open it in Preview, or right-click and choose Open With, then Preview. Go to File, then Export, set the Format menu to JPEG, drag the Quality slider to the level you want, and save (iDownloadBlog). Preview gives you the one thing Paint does not, a visible quality tradeoff you set before you commit to the file.
Batch-save a folder on Mac with Photos
For more than one file at a time, use Photos instead of Preview. Select every WebP you want converted, then File, Export, Export n Photos, set Photo Kind to JPEG, choose a JPEG Quality, and export. That single pass handles a whole folder without opening each file by hand, the same job the browser tool's batch mode does minus the upload.
The copy-paste trick when the image is still open
You do not always have to save the WebP to disk first. Right-click the image in your browser, choose Copy image, open Paint, paste with Ctrl and V, then File, Save as, JPEG. This skips the download step entirely and suits a single image you are grabbing off a page rather than a whole folder. It is community-documented rather than an official Paint feature, so confirm it behaves the same way in your Windows version before leaning on it for anything time-sensitive.
Save Straight to JPG in the Browser With an Extension
When the WebP is a web image you have not downloaded yet, a browser extension can save it as a JPG in one right-click. The AI Overview for this query leads with a dedicated extension, and it is a fair pick if you save images off the web constantly rather than once in a while.
The Save WebP as JPG extension for Chrome and Firefox
To save WebP as JPG in Chrome, install the Save WEBP as JPG/PNG extension from the Chrome Web Store, then fully close and reopen the browser to activate it. After that, right-click any web image, choose Save Image As Type, and pick JPG. Firefox has equivalent add-ons that intercept the download the same way. The save webp as jpg extension route only helps for images still in the browser; a WebP already on your disk goes through Paint, Preview, or the browser tool above.
The All Files rename workaround, and why it backfires
The AI Overview's second method tells you to open the browser Save As dialog, switch Save as type to All Files, and change the extension from .webp to .jpg by hand. Skip it. That renames the file without re-encoding a single byte, which is the exact trap the next section takes apart.
Can I Just Rename WebP to JPG?
No. Renaming a .webp file to .jpg changes the label, not the bytes, so you are left with a WebP wearing a JPG name that strict software rejects. A real conversion re-encodes the pixel data into JPEG; a rename does neither, and most of the time you find out only when an upload form or an editor refuses the file.
What the file's own bytes say
You can prove this without any special software. A WebP is a RIFF container, so open one in any hex viewer and the first four bytes read RIFF, while bytes nine through twelve read WEBP (Google Developers). A genuine JPEG instead begins with the bytes FF D8 FF. Rename the WebP to photo.jpg and every one of those bytes stays exactly where it was; the file still announces itself as WEBP to anything that reads the header instead of the extension. That is why a photo editor, a print service, or an upload form that checks the file signature throws the mislabeled file back, while a forgiving image viewer that trusts the extension might show it and hide the problem until it costs you.
Which apps notice a rename, and which do not
The reason the rename trick seems to work sometimes is that programs split into two camps. Web browsers and simple image viewers often trust the extension and render the mislabeled file, which is where the false confidence comes from. Editors, print services, operating-system upload validators, and anything that reads the file signature check those header bytes and reject it. So a rename can pass a casual glance and still fail at the one place you needed it to work, which is why it is not worth the gamble when a real re-encode takes the same few seconds.
Rename versus a real re-encode
The difference is one line in a table, and it is the whole reason a converter or a built-in Save As exists at all.
| Step | What changes | Result |
|---|---|---|
| Rename .webp to .jpg | The extension only | Still WebP bytes; strict apps reject it |
| Re-encode in Paint, Preview, or the tool | The pixel data, rewritten as JPEG | A real JPG that any app opens |
Why Are Images Saving as WebP?
Because the website served them that way. Many sites deliver WebP to save bandwidth, since WebP typically runs 25 to 35 percent smaller than a JPEG of the same visual quality, and your browser saves whatever it was handed. It is not your browser corrupting the download or a setting you got wrong.
Chrome, Edge, and most modern browsers request WebP whenever a server offers it, and the Save Image As command then gives you that WebP unchanged. Stopping the pileup is a browser-level fix rather than a per-file one. For the file in front of you right now, any method on this page turns the WebP you already have into a JPG.
On a phone it looks the same. A long-press Save from a mobile browser stores the WebP the site sent, and the gallery then shows a .webp you need as a JPG for an app that will not accept it. The fix is identical: run the file through one of the methods here once it reaches a computer, or use a mobile converter that genuinely re-encodes the image rather than just renaming it.
What Do You Lose When You Save a WebP as JPG?
Two things, every time: transparency and animation. JPEG has no alpha channel and no way to store multiple frames, so a transparent WebP loses its see-through areas and an animated WebP collapses to a single still frame. Neither loss is reversible from the JPG, so keep the original WebP as a backup if either one matters to you.
Transparency and animation do not survive
A logo or icon with a transparent background comes out of the JPG save with that area filled by a solid color, almost always white, because there is nowhere in a JPEG to store the alpha channel. An animated WebP keeps only its first frame. If the destination genuinely needs a raster with intact transparency, export to PNG instead of JPEG, the same File, Export dialog with a different Format choice.
| What you are saving | Comes back clean as a JPG? |
|---|---|
| A photo with a solid or busy background | Yes |
| A logo or icon on a transparent background | No, the transparency fills with a solid color |
| An animated WebP | No, only the first frame survives |
The size surprise: a JPG usually gets bigger
There is a counterintuitive cost too. Re-saving a WebP as a JPG usually makes the file larger, not smaller, because WebP already held the same picture in fewer bytes. Working backward from the rule that WebP runs 25 to 35 percent smaller than an equivalent JPEG, a 140 KB WebP product photo typically climbs to somewhere around 187 KB to 215 KB once it becomes a JPG. Nothing broke on that trip; JPG just needs more bytes to hold a look WebP had already packed smaller.
| Same product photo | File size |
|---|---|
| Original WebP | 140 KB |
| Re-encoded to JPG | About 200 KB (187 to 215 range) |
Read the bars top to bottom and the swap looks backward, because it is. The reason to move to JPG is compatibility, an app or a form that only accepts JPEG, not size. If size is the goal, the JPG is the wrong direction and the WebP was already doing the job.
When Is Saving as JPG the Wrong Move?
Whenever the file has transparency or animation you need to keep. Converting either one to JPG is a one-way trip, so if the destination needs a see-through background, export to PNG instead, the same File, Export dialog in Preview or Photos with PNG chosen as the Format.
Picture a shop logo saved as a transparent WebP that you need on a printed flyer. Save it as a JPG and the transparent area turns into a white box that sits on the flyer's colored background like a sticker. PNG keeps the cutout; JPG cannot. That single case decides the format more often than file size does.
If your actual goal is a smaller file rather than a JPG specifically, saving as JPG is also the wrong direction, since it usually inflates the size rather than cutting it. In that case keep the WebP, or compress it further, rather than trading it for a heavier JPEG. I built this tool to convert between JPG, PNG, WebP, and AVIF, and I still tell people to keep a transparent graphic as PNG and an efficient WebP as WebP unless a specific form or app is refusing to take the file.