How to Convert WebP to JPG or PNG
WebP is the better format in almost every way — smaller files, comparable or better quality, wide browser support. So it's a little counterintuitive that one of the most common things people search for is how to go the other direction: turning a WebP file back into a JPG or PNG. Turns out "better" doesn't always mean "accepted everywhere."
Why you'd need to convert WebP backward
A few genuinely common situations:
- Older software chokes on it. Plenty of versions of Microsoft Word, some photo viewers, and older image editors either don't open WebP at all or handle it awkwardly.
- A platform or form only accepts JPG/PNG. Some marketplaces, print services, government forms, and older CMS upload fields explicitly reject WebP — you'll get a rejected upload or a generic error with no explanation.
- Someone else needs to open it and isn't tech-savvy. If you're sending a photo to someone whose phone or app doesn't render WebP cleanly, JPG is the safer bet.
- You're pasting into a document or slide deck that expects standard image formats and displays WebP as a broken icon.
- A design or print workflow expects PNG specifically — for transparency, for a specific color pipeline, or because that's just what the tool requires.
None of these mean WebP was the wrong choice originally — they just mean the format needs to match whatever is on the receiving end.
JPG or PNG — which one when you convert back
Quick rule of thumb:
- JPG for photos and anything without transparency. Smaller files, universally supported.
- PNG if the original WebP has a transparent background, or if it's a screenshot, logo, or graphic with flat colors and sharp text — JPG's compression tends to blur that kind of content.
WebP supports transparency (like PNG), so if you convert a transparent WebP to JPG, you'll lose the transparency — it gets filled in with a solid background instead. If that matters, convert to PNG.
Will you lose quality doing this?
Worth being honest about: if the WebP was saved with lossy compression (the default, and almost always the case for photos), it already went through one round of quality loss. Converting it to JPG is a second lossy pass — a small amount of additional degradation is unavoidable in the strictest sense. In practice, if you keep the JPG quality setting reasonably high (80+), the difference is not something you'll notice at normal viewing size. It only becomes visible if you convert back and forth repeatedly, or set the quality very low.
If the WebP was saved lossless — less common, but it happens with graphics and screenshots — converting to PNG keeps you lossless the whole way through, with no quality loss at all.
How to actually do it
img-compress converts WebP to JPG or PNG directly in your browser — drop the file, pick the output format, download. Nothing gets uploaded anywhere, and if you've got a batch of files to convert (not just one), you can process all of them and download the whole set as a ZIP in one go. We cover the broader tradeoffs between formats, including where AVIF fits in, in WebP vs JPG vs PNG vs AVIF.