Convert WebP to JPG or PNG when something refuses to open it, or convert your images to WebP to lighten a website. Both directions, up to 50 files at once.
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · max 30 MB
Auto tunes each image.
A hard cap for “under 50 KB” portals.
Empty side keeps the ratio. Never enlarges.
WebP · 229 KB
AVIF · 67 KBThe two populations who type "webp converter" want opposite things. Have WebP, can't use it: images saved from websites that Office, an older Photoshop or a marketplace uploader rejects. Convert out, to JPG for sharing or PNG for editing. Want WebP: site owners chasing smaller pages. Convert in, from JPG or PNG. The same tool above does both, with opposite defaults, and each pair has its own page below.
| Conversion | From | To | Notes |
|---|---|---|---|
| WebP → JPG (Auto) | 234.9 KB | 73.6 KB | the universal share |
| WebP → PNG | 234.9 KB | 188.8 KB | lossless, alpha kept |
| WebP → AVIF (Auto) | 234.9 KB | 68.7 KB | the next rung down |
| JPG → WebP (Auto) | 188.3 KB | 110.9 KB | the web migration |
One engine, both directions. WebP-out rows use our reference WebP; WebP-in rows use the reference JPEG.
How these numbers are measured: every byte count on this page is the size of the actual encoded file our engine produced from the named source image. Those are the same bytes you would download, not an estimate or a best case. Rerun any of them yourself: drop your own file into the tool above and the meter reports your real result.
Browsers were solved years ago (~97% decode WebP). The holdouts are everything else: Photoshop before 2022 (needed a plugin), Microsoft Office (inserting WebP into Word/PowerPoint remains a coin flip by version), many email clients (attachments render as question marks), Discord and marketplaces (uploads accepted inconsistently), and a long tail of photo frames, kiosks and older phones. That list, not quality, is why WebP-to-JPG is one of the most-run conversions on the web. It is also why "just use WebP everywhere" is only true inside a browser tab.
WebP quality behaves like a curve with a knee at ~80. Below it, photographic detail starts visibly degrading. Above it, file size climbs steeply for differences you cannot see. Two practical rules fall out. First, don't transfer JPEG habits: WebP 80 looks like JPEG 90, and encoding WebP at 90+ "to be safe" can produce files as big as the JPEG you started with. Second, let Auto pick within 75–85 per image and overrule it only after looking at the compare slider at 100%. Graphics and flat art are the exception. They belong in lossless mode, where the question disappears.
Every route in and out runs on the same engine and the same rules. Each card is its own page.
The safe upgrade. Around a third smaller at matching quality, and readable essentially everywhere.
Keeps the alpha channel and still cuts real weight. The least disruptive way off PNG.
The universal handoff. Anything that opens an image opens this: print, email, old software.
Keeps transparency for editors and pipelines that won't read WebP. Bigger file, no further loss.
One more step down the size curve for pages already on modern formats. Keep WebP as the fallback.
Broader support, still modern compression. The middle path when AVIF is one step too far.
Phone photos headed for a website. Similar size to the original, and universally displayable.
Short answers specific to this page. The tool above settles most of them in a second.
Drop it in above. The meter reports the exact saving before you download anything.