Image tool
WebP to JPG or PNG
Turn a WebP into a format that older software, email clients, and print workflows will still open.
1. Choose an image
Conversion happens in this tab. The file is never uploaded.
Choose a WebP, or drop one here
You can also paste an image with Ctrl or Command and V
WebP, JPG, or PNG
Choose a WebP to begin. Nothing is uploaded.
2. Result
The converted image will appear here.
—Estimated file size
Why does my WebP not open? Most desktop and mobile software has supported WebP for years, but older email clients, some print shop software, and a few document editors still do not. Converting to JPG is the fix that works nearly everywhere.
JPG or PNG?
Choose JPG
For photographs, scans, and anything going to a service that will not handle PNG. Much smaller files.
Choose PNG
When the image has text, sharp edges, or transparency that must survive. Larger files, no quality loss.
Check the file size
The panel measures the real JPG size at your chosen quality, so you can compare it against what you started with.
Converting WebP, and when it is the wrong move
WebP usually produces a smaller file than JPG or PNG at the same apparent quality, so converting away from it is a compatibility decision rather than a size one. Every current version of Chrome, Firefox and Edge reads it, and Safari has read it since version 14. The places that still do not are older iPhones that have not been updated, older Android WebView, a number of email clients, and most desktop publishing and print software. If your file is going to one of those, convert. If it is going to a browser, keep the WebP and change nothing.
The quality slider only affects the JPG
PNG is lossless, so there is nothing for a quality setting to trade away and the control is hidden rather than shown as something that does not work. The file size reported for a PNG is simply the size the PNG came out at.
Converting to PNG often makes the file bigger
PNG is an older format with a less efficient compression scheme. A well-compressed WebP converted to PNG frequently doubles in size. Do it because something cannot read WebP, never because you expect a smaller file.
Going to JPG discards transparency permanently
A JPG has no alpha channel, so a transparent area is filled with the background colour you choose and cannot be made transparent again afterwards. Match that colour to whatever the image will sit on, which is usually white for a page or document.
A PNG made from a lossy WebP is still lossy
Detail that a lossy WebP has already thrown away is not in the file and cannot be recovered. Converting it to PNG stops further loss; it does not restore anything.
Metadata does not survive the re-encode
The result is drawn to a fresh canvas, so the output is a new file. EXIF data, including any GPS coordinates, is not carried across from the original.
Choosing between the two formats
JPEG is the safe default. Every browser, phone, print service and application accepts it, and for photographs its compression is efficient enough that the quality loss is hard to see at normal viewing size.
PNG is lossless and supports transparency, which is why it suits screenshots, diagrams, logos, and any image with text or sharp edges. Photographs saved as PNG become very large for no visible benefit, because PNG is not designed to compress photographic detail efficiently.
The practical rule: photographs to JPEG, anything with flat colour or text or a transparent background to PNG. Converting a photograph from WebP to PNG will make the file larger than the WebP you started with, which is the expected result rather than a fault.
WebP itself is worth keeping if the destination supports it. Every current browser does, so converting to an older format is mainly for compatibility with software that has not caught up, not for a size saving.
Further reading: Read the full guide: WebP to JPG or PNG
Common questions
Do I need a WebP file to use this?
No. It accepts any image your browser can decode, which also makes it useful when a workflow needs a PNG as a JPG. Since the tool is named for WebP, it tells you when your input was something else and says it is converting anyway, rather than leaving you to assume it only took WebP.
Can I choose JPG or PNG?
Yes, and the quality control appears only for JPG. PNG is lossless and ignores the quality setting entirely, so exposing a slider for it would be misleading. Choose PNG when the image has transparency or sharp edges; choose JPG for a photograph.
Is my image uploaded?
No. The decode, the draw and the re-encode all happen in this tab. Your file is never written to and never leaves your device.
Will converting to JPG lose transparency?
It will. JPG has no alpha channel, so transparent areas are flattened to a solid colour. If your image relies on transparency, keep PNG as the target.
Does converting back to WebP save space?
Usually, because WebP compresses more efficiently than JPG for most photographs — often substantially. But the saving depends entirely on the source, and a graphic that is already small in PNG may come out larger. Nothing is guaranteed, so measure the result rather than assuming.