How to Convert WebP to JPG: 3 Simple Ways
By Bruce Shang
August 13, 2026· Updated on Sep 6, 2026· 6 min read
You downloaded an image, tried to attach it to an email, and your mail client shrugged. You uploaded it to a form, and the site said "unsupported format." That's WebP, an excellent web format that some older tools and workflows still refuse to accept. Converting it to JPG takes seconds.
Why convert WebP to JPG at all
WebP is smaller and modern browsers love it, but JPG wins on compatibility:
- Email clients and corporate systems
- Print shops and document workflows
- Older photo editors
- Some upload forms and CMS
- Sharing with less tech-savvy recipients
If the destination doesn't speak WebP, JPG is the universal fallback.
Method 1: The free browser converter (recommended)
The Image Converter on SlimImg converts WebP to JPG with zero uploads:
- Open the converter
- Drag in your WebP files, batch works
- Choose JPG as the output and set quality (90 is a safe default)
- Download the JPGs
Your images stay on your device the whole time.
Method 2: Built-in OS tools
No browser needed for a single image:
- macOS: open the file in Preview → File → Export → choose JPEG
- Windows: open in Paint → File → Save As → JPEG
Fast, but you lose batch support and quality control.
Method 3: Command line (for developers)
On macOS, sips ships with the system:
sips -s format jpeg input.webp --out output.jpg
Great for scripts and folders. (Want to know which format is right in the first place? See WebP vs PNG and the image formats guide.)
Quality notes
- Converting a lossy WebP to JPG recompresses it, export at quality 90–95 to avoid visible artifacts
- If the WebP came from a lossless source, converting to JPG is still lossy; keep the original WebP as your master
- JPG has no transparency, any transparent areas will flatten to a background (white by default, or choose another in the converter)
When you should not convert to JPG
Converting WebP to JPG is the right default for compatibility, but three cases call for something else:
- You need transparency, JPG has no alpha channel. If the WebP has transparent areas (logos, cutouts, UI elements), convert to PNG instead and keep the transparency.
- The image is a graphic with text, a screenshot or diagram stored as WebP will get JPG compression artifacts on its sharp text edges. Convert to PNG if you must change format, or keep WebP.
- It's for a website, not a tool, if the destination is a web page that supports WebP, don't convert at all. You lose the 25–35% size advantage for no benefit.
The deciding question is always the same: what does the destination accept, and what does the image contain? Compatibility says JPG, transparency says PNG, web display says keep WebP.
A worked example with real numbers
Here's what a typical conversion costs in size:
| Source | Size | After JPG q90 | Note |
|---|---|---|---|
| WebP photo (quality 75) | 450 KB | 680 KB | JPG is bigger, you're paying for compatibility |
| WebP screenshot (lossless) | 900 KB | 1.4 MB | Text survives but size grows |
| WebP with transparency | 380 KB | 420 KB (white bg) | Only worth it if JPG is required |
The pattern to notice: converting to JPG rarely makes a file smaller. You're not optimizing, you're translating for compatibility. Budget for the size increase, and if the result is too big, compress it afterward with the Image Compressor rather than converting again.
Getting the quality setting right
The converter's quality slider is where "acceptable" becomes "invisible":
| Quality | Use when | Result |
|---|---|---|
| 95 | The JPG will be printed or edited further | Nearly invisible loss, larger file |
| 90 | Email, documents, most sharing | Safe default, artifacts imperceptible |
| 85 | Web uploads, small attachments | Slight compression, still fine for photos |
| 75 | Thumbnails, previews | Visible artifacts in smooth areas up close |
Because the source WebP may already be lossy, set JPG quality at 90–95, a second lossy pass at 75 compounds artifacts. If the WebP was lossless to begin with, you lose nothing by the JPG being at 95, but the master should stay lossless (see below).
Keeping a master you can reconvert from
The biggest mistake in WebP→JPG workflows is throwing away the WebP after converting. Keep the WebP as your master: it's smaller than the JPG, lossless-capable, and re-converting later starts from a clean source. Store both if you need the JPG for compatibility, but never re-encode from the JPG again, every generation costs quality.
The two conversion directions, compared
WebP sits in the middle of the format ecosystem, which is why it converts both ways:
| Direction | Purpose | Result |
|---|---|---|
| WebP → JPG | Compatibility (email, print, old software) | Lossy, larger file, universal |
| WebP → PNG | Transparency or lossless editing | Lossless, larger file |
| JPG/PNG → WebP | Web optimization | Smaller, needs modern support |
For the web-optimization direction and the transparency question, the WebP vs PNG guide is the full reference.
The one-line decision table
| Situation | Convert to |
|---|---|
| Email, print, old software needs it | JPG |
| Image has transparency | PNG (not JPG) |
| Graphic with sharp text | PNG or keep WebP |
| Destination is a website | Keep WebP |
| Not sure | JPG at quality 90 |
When in doubt, a quality-90 JPG is the safe universal answer, small enough to send, large enough to look identical to the source, and accepted everywhere. Keep the original WebP as the master, note the output size, and you're set.
WebP conversion questions
Is WebP better than JPG?
For web images, usually yes, WebP is smaller at the same quality. For compatibility, JPG wins. That's why you convert one direction on the web and the other direction for email and print.
Can I convert WebP back to PNG instead?
Yes. If you need transparency or a lossless format, the Image Converter also outputs PNG, see WebP vs PNG for when that makes sense.
Does converting WebP to JPG lose quality?
Any conversion to JPG is lossy, but at quality 90–95 the difference is invisible. The bigger risk is converting a low-quality WebP, garbage in, garbage out.
Can I convert many WebP files at once?
Yes, the browser converter handles batches, so a folder of WebP images converts in one step.
Why does my converted JPG have a white background?
JPG doesn't support transparency. Transparent areas in the original WebP became white (or your chosen color). If you need transparency in the output, convert to PNG instead.
The converted JPG is still heavier than you would like? The compression guide covers the quality settings that keep it sharp while cutting size.
When conversion is the right call
Convert WebP to JPG when compatibility beats file size: email, print shops, and older software still expect JPG. Keep WebP for the web where it loads faster, and use quality 90 to 95 for the conversion so the lossy step costs as little as possible.
Try the Image Converter
Free, private, and no account needed — your files never leave your browser.
Open Image Converter →