Why you need this tool
You right-clicked an image on Google Image Search, picked "Save image as," and got a .webp file. Now you can't paste it into Microsoft Word. You can't attach it to your Outlook email and have it preview inline. Photoshop CS6 won't open it. Your company's web upload form rejects the extension. The HR portal at your job won't take it. Your in-laws' Windows 10 laptop opens it as a broken icon.
This is the WebP problem. WebP is Google's image format — efficient, modern, 25-35% smaller than JPG at the same quality. Browsers picked it up between 2010 and 2020. The rest of the world's software did not. Convert the WebP to JPG and every one of those problems disappears, because JPG is the format everything supports.
That's what this tool does. Drop a WebP, get a JPG. No upload, no watermark, no 5MB free-tier cap, no email signup. The conversion runs in your browser using the native canvas.toBlob API — the same code path that desktop image editors use, just running in JavaScript instead of compiled C.
How to use the WebP to JPG Converter
Four steps. The whole thing takes under fifteen seconds for a single image.
- Drop your WebP files. Multiple at once is fine. Up to 50 MB per image, 200 MB combined. Folders work — drag the whole folder into the drop zone and the tool finds every .webp inside it.
- Pick JPG quality. 92% (default) produces output that's visually identical to the source. 75% is the web-friendly sweet spot — about a third smaller with no perceptible quality loss. 50% is for previews where visible compression artifacts are acceptable in exchange for a much smaller file.
- Click Convert. Each WebP gets decoded via the browser's native image loader, painted onto an HTML canvas with a white background (JPG can't carry transparency), and re-encoded as JPG. The per-row size delta shows you exactly how much the conversion changed the file size.
- Download individually, or click "Download all" to get sequential downloads of the whole batch. Filenames mirror the input: photo.webp becomes photo.jpg.
That's the whole flow. There's no account, no "verify your email" step, no "you've used 3 of 5 free conversions this month" gate.
Which apps reject WebP (and which accept it)
If you're converting a WebP to JPG, you're almost certainly doing it because something downstream refused the WebP. Here's a non-exhaustive map of which apps fall on which side of the line, current as of 2026.
| App / surface | WebP support | Workaround if no |
|---|---|---|
| Modern browsers (Chrome, Firefox, Safari 14+, Edge) | Yes | None needed |
| Microsoft Word (all current versions through 2026) | No — refuses to embed | Convert to JPG |
| Microsoft PowerPoint | Partial — newer versions work, older versions reject | Convert to JPG for compatibility |
| Outlook (desktop, inline images) | No — broken-image icon | Convert to JPG |
| Gmail web client | Yes (browser does the rendering) | None needed |
| Photoshop CC 2022+ | Yes | None needed |
| Photoshop CS6 and older | No — file format not recognized | Convert to JPG or PNG |
| Most corporate web upload forms | Often no — extension whitelist forgets .webp | Convert to JPG |
| WhatsApp / iMessage (sending an image) | Partial — strips animation, may auto-convert | Pre-convert to JPG for predictability |
| Older Android gallery apps | Partial | Convert to JPG |
| Most stock photo upload portals (Shutterstock, etc.) | No — JPG/TIFF only | Convert to JPG |
| Print-on-demand services (Vistaprint, Printful, etc.) | No — JPG/PNG/PDF only | Convert to JPG |
| LinkedIn / Twitter / Facebook uploads | Yes — they auto-convert internally | Either works, but JPG is more predictable |
The pattern: anything that runs in a modern browser handles WebP. Anything that's been around long enough to have a desktop install base — Word, Outlook, older Photoshop — generally doesn't. Conversion to JPG is the universal fix.
A worked example: WebP from Google Image Search to a Word document
You're writing a quarterly report in Microsoft Word. You search Google Images for "city skyline at dusk," right-click the result you want, and pick "Save image as." Chrome saves it as skyline.webp (about 180 KB).
You open Word, click Insert → Pictures → This Device, navigate to skyline.webp. Word's file picker either hides the .webp extension entirely or shows it but won't let you click it. (Behavior varies by Word version, but the outcome is the same: WebP doesn't embed.)
Open the WebP to JPG Converter, drop skyline.webp into it, click Convert. Default 92% quality. About one second later, you have skyline.jpg — around 240 KB (JPG is less compression-efficient than WebP, so the file grows slightly even at high quality). Insert that into Word. It works. The document embeds the image, the print preview shows it, the PDF export keeps it.
Total time: about twelve seconds, including the file-picker round-trip. Compare this to the iLoveIMG flow — upload the file, wait for the server to process it, click the download link, wait for the download, find it in your Downloads folder — which is roughly forty-five seconds for the same outcome, plus your image is now on someone else's server.
The "save image as" gotcha: on Chrome and Edge, right-clicking a Google Image Search result and picking "Save image" defaults to .webp because Google serves images as WebP to modern browsers. Firefox and Safari sometimes save as the original format depending on settings. If you frequently need JPGs from Google, either install a "Save Image as JPG" browser extension (works, but adds a third-party extension to your browser) or just plan to run the WebP through this converter as a normal part of the workflow.
Quality settings: how to pick
The quality slider runs from 30% to 100%. Three settings cover almost every real-world case.
- 92% (default). Visually identical to the source. Use this when the destination is a document, a presentation, a print job, or anywhere you can't risk visible compression artifacts. File size will typically be 20-40% larger than the source WebP.
- 75%. The web-friendly sweet spot. Visually indistinguishable from 92% for most photos but produces files closer to the size of the source WebP. Good for embedding in blog posts, sending in chat, uploading anywhere the destination will further compress the image (social media, most web forms).
- 50%. Visible compression artifacts on close inspection but acceptable for thumbnails, previews, and rough drafts where file size matters more than perfect fidelity.
Worked example: a 500 KB WebP photo of a person's face. At 92% JPG, the output is around 700 KB. At 75% JPG, around 480 KB. At 50% JPG, around 220 KB. The 92% version is indistinguishable from the source; the 75% version requires a side-by-side comparison at 200% zoom to spot any difference; the 50% version shows visible blocking around fine details (eyelashes, hair texture) when viewed at full size.
What happens to transparency and animation
JPG doesn't support transparency or animation. Two implications for WebP-to-JPG conversion.
Transparency: WebP supports an alpha channel, so a WebP can have transparent or semi-transparent regions. JPG cannot. The converter paints any transparent areas white before encoding the JPG. This is the only sensible default — there's no "transparent" color in JPG to map to. If you need the transparency preserved, convert to PNG instead (use the Image Format Converter and pick PNG as the target). PNG carries the alpha channel exactly as WebP does.
Animation: WebP can be animated (like an animated GIF, but with much better compression). JPG can't be animated. The converter uses the first frame of an animated WebP and discards the rest. There's no way around this — JPG fundamentally doesn't support motion. If you need to keep the animation, you'd convert to GIF or to a video format like MP4, both of which are different toolchains.
How this compares to the alternatives
Every major online converter does WebP-to-JPG. The differences are in the trust model, the cost, and the cap.
| Tool | Where it runs | Free-tier cap | Watermark | Account required |
|---|---|---|---|---|
| Microapp WebP to JPG | Your browser | None (browser memory only) | None | No |
| iLoveIMG | Their server (upload) | 15 files / 100 MB on free tier | None on output | Optional |
| Convertio | Their server (upload) | 100 MB total, 10 conversions/day on free tier | None | Pushed hard for higher limits |
| CloudConvert | Their server (upload) | 25 conversions/day free | None | Optional, required past free tier |
| ezgif (webp-to-jpg) | Their server (upload) | Single file at a time, no batch | None | No, but ads everywhere |
| TinyPNG | Their server | 20 images, 5 MB each | None | Optional |
The same outcome (WebP becomes JPG) with opposite trust models. iLoveIMG, Convertio, CloudConvert, and ezgif all upload your image to a remote server, run the conversion there, and send the result back. Microapp does the conversion in your browser using the canvas API that ships with every browser since 2012. Same JPG out the other end. Different privacy properties.
Free is a fact, not a slogan. We don't charge because there's nothing to charge for — no server compute, no bandwidth, no storage. The whole tool is a 30 KB JavaScript widget that runs on your hardware. The big commercial converters charge for their paid tiers because they actually do spend money on server infrastructure. Different economic shape, different price.
Why does the JPG sometimes look larger than the WebP?
Because JPG is a less compression-efficient format than WebP. A 500 KB WebP at 80% quality typically becomes a 700 KB JPG at 92%. That's not a bug — it's just the math. WebP was designed twenty-five years after JPG, with twenty-five more years of compression research behind it, and it shows in the file sizes.
To match the WebP's file size in the JPG output, lower the JPG quality to around 75%. Most photos at 75% JPG are visually indistinguishable from 92% JPG and roughly the same size as the source WebP. If file size doesn't matter for your use case (you're embedding in a Word doc that'll be 4 MB regardless), leave it at 92% and ignore the size growth.
Related Microapp tools
- PNG to WebP — the reverse direction. Useful when you have a PNG and want to shrink it for web embedding.
- Image Format Converter — universal converter for PNG, JPG, and WebP in any direction. Same underlying engine as this tool, with the format picker exposed.
- Image Compressor — reduce file size at the same format. Useful if you want a smaller JPG without changing format.
- Image Resizer — change pixel dimensions. Useful before conversion if the destination has a specific size requirement.
- HEIC to JPG — same kind of problem, different format. HEIC is Apple's WebP equivalent — efficient, modern, and rejected by half the desktop world.
Frequently asked questions
Why won't my WebP open in [some app]?
WebP is Google's image format — efficient (25-35% smaller than JPG at the same visual quality) but newer. Browsers picked it up in 2010-2020. Microsoft Word, older Photoshop, many email clients, and a lot of corporate web upload forms simply don't support it. JPG is universally supported. Converting WebP to JPG is the standard fix and the reason this tool exists.
What happens to transparency?
JPG doesn't support transparency. Anywhere your source WebP is transparent gets painted white before encoding. If you need the transparency preserved, use the Image Format Converter and pick PNG as the target — PNG supports alpha just like WebP.
Is my WebP really not uploaded?
Correct. WebP decoding uses the browser's native image loader; JPG encoding uses canvas.toBlob. Zero outbound requests during the convert. Open DevTools, switch to the Network tab, drop your WebP into the tool, run the conversion, and check that no new requests for your image data appear. That's the test.
Can I batch-convert?
Yes. Drop multiple WebP files (or a folder), all get converted to JPG with one operation. Each becomes its own download. The 200 MB combined cap is there to protect your browser from running out of memory — past that, performance degrades and the conversion may stall.
Why does the JPG sometimes look larger than the WebP?
JPG is less compression-efficient than WebP. A 500 KB WebP at 80% quality usually becomes a 700 KB JPG at 92%. To minimize the size increase, lower the JPG quality (75% gives roughly the same file size as the source WebP for most photos). The visual difference between 92% and 75% JPG is hard to spot without a side-by-side comparison.
What about animated WebP?
The tool uses the first frame. JPG doesn't support animation, so there's no way to preserve motion. For animated WebP, you'd want to convert to GIF or to a video format like MP4 — different toolchains, different tools.
Will EXIF metadata transfer?
Mostly no. Canvas re-encoding strips most EXIF (camera model, GPS coordinates, exposure data). For most users sharing photos or embedding in documents, the lost EXIF is a feature — it means you don't accidentally leak GPS coords that were embedded by your phone's camera. For archival use where EXIF matters, use a tool that preserves it (ImageMagick from the command line is the standard option).
How does this compare to iLoveIMG, Convertio, and CloudConvert?
Same outcome (WebP becomes JPG), opposite trust model. They upload your image to their server and run the conversion there. We do the same conversion in your browser using canvas.toBlob. No file size limit beyond browser memory, no free-tier batch cap, no watermark on the output, no email signup, no "you've used 5 of 10 free conversions today." The conversion math is identical because the JPG encoder spec is identical; the privacy and cost properties are not.