WebP to JPG & PNG Converter
Turn that .webp download into a file your software will open.
The .webp is decoded on your device, not uploadedOpen a .webp download and save it as PNG or JPG
or drag & drop them here, or paste one from your clipboard (Ctrl+V). Drop as many as you like — no file cap, no size cap.
PNG · JPG · WebP · GIF · AVIF
JPEG has no alpha channel. If the source image has transparency, those areas are filled with this colour (white by default) and the result says so. Nobody should discover their logo went out on a black background.
Lossless keeps every pixel (quality 1 — the only lossless lever a browser encoder exposes). It is a real alternative to PNG, but on noisy images it can come out larger than the original: the table below reports the actual bytes, never a promise.
Results
Choose your images and every file shows up here with its original size, its new size and the real difference — including when the output is bigger.
How it works
Everything runs in your browser: images are never uploaded, there is no account, no queue and no daily limit. Re-encoding also drops the original EXIF metadata, location included.
About this WebP to JPG and PNG converter
Drop in the .webp file you just downloaded and get back an ordinary PNG or JPG that any program will open. Your browser’s own decoder reads the file, the pixels are drawn to a canvas and re-encoded here in the page — nothing is uploaded. Before you choose an output, the page checks whether the file really carries transparency and recommends accordingly: PNG when there are see-through pixels worth protecting, JPG when there are none and you would rather have a small file. Several files at once are fine, and AVIF, the other download that refuses to open, is accepted as input too.
Why was the download a .webp at all? Because WebP is an image format Google published to replace JPEG, PNG and GIF at a smaller size, and Google’s own figures are that lossy WebP runs 25–34% smaller than comparable JPEG while lossless WebP is about 26% smaller than PNG. Site owners serve it because performance tooling tells them to: Chrome’s Lighthouse audit says outright that AVIF and WebP “have superior compression and quality characteristics compared to their older JPEG and PNG counterparts”. Your browser accepted it, saved exactly what the server sent, and only afterwards did you discover that the app you wanted to use it in has never heard of the format. The file is not broken.
One thing the upload converters rarely admit: converting cannot undo compression. Writing a PNG from a decoded WebP is lossless with respect to the pixels the decoder hands over — but if that WebP was lossy, the loss already happened when the site encoded it, and PNG cannot restore detail that is no longer in the file. Saving as JPG is a step further down, because JPEG is lossy as well: you are stacking a second generation of loss on the first, and existing artefacts get re-compressed as real detail. Practical rule: PNG if the image goes back into an editor, JPG at high quality if it goes straight into a document — then stop converting it.
The transparency question is what really decides your output. WebP carries an alpha channel in both its lossy and lossless modes; JPEG never has. So if your file has transparent pixels and you save it as JPG, something has to fill them, and the browser’s canvas default is black — which is how a logo ends up sitting on a black rectangle. This page detects the alpha channel, recommends PNG when it finds one, and if you want JPG anyway it asks you to pick the flatten colour (white is the usual answer) instead of deciding for you.
Four limits, stated plainly. An animated WebP converts as its first frame only — a still PNG or JPG has nowhere to put the rest. A PNG made from a lossy WebP is normally several times bigger, because PNG stores every pixel losslessly while the WebP discarded information to get small; each file’s real size is shown before and after, so you can see it. Re-encoding through a canvas drops EXIF, so camera and location metadata do not survive (usually welcome, occasionally not). And a very large image can exceed the browser’s canvas limits, which gets you a clear error, not a blank picture.
Which apps open .webp without converting anything
Converting is the fix when an app cannot read the format. It is not the fix when the app can and you did not know. Before you convert a whole folder, it is worth checking this list — the table below is built from each vendor’s own documentation, not from forum lore, and the quickest check of all is to drag the .webp onto a browser tab: it will render, because every current browser decodes WebP.
| Where you are stuck | Can it read .webp? | What the source says |
|---|---|---|
| Any current browser | Yes | caniuse records WebP at about 96% of global browser usage: Chrome from 32, Firefox from 65, Edge from 18, iOS Safari from 14. MDN adds that on macOS, WebP in Safari needs Safari 14 or later and Big Sur or newer. |
| Windows Explorer, Photos, Paint | Yes, with Microsoft’s own extension | Microsoft publishes a free WebP Image Extension in the Microsoft Store, described as enabling you to view WebP images in Windows File Explorer, Photos and other Windows apps. On recent Windows it is often already installed. |
| Photoshop | Yes, from 23.2 (February 2022) | Google’s WebPShop project states that Photoshop 23.2 and newer supports WebP natively, and that the plug-in is still useful because “some features such as preview at encoding and animations are missing in Photoshop 23.2”. An animated WebP opens as its first frame on a single layer. |
| Word, Excel, PowerPoint, Outlook | Microsoft 365 desktop: yes. Older perpetual Office: no | Microsoft announced WebP image support for Office files in a Microsoft 365 Insider post in August 2021. Users on older non-subscription releases still report Insert > Pictures refusing a .webp — that is the classic reason to convert to PNG. |
| macOS Preview | Not documented | Apple’s Preview user guide lists its supported formats as HEIC, JPEG, JPEG 2000, OpenEXR, PDF, PNG and TIFF. WebP is not on that list, so if Preview will not cooperate, open the file in Safari instead. |
| Premiere Pro and most video editors | No | Adobe’s supported-file-formats page for Premiere Pro does not list WebP among importable still images. Convert to PNG if the graphic needs transparency, JPG if it does not. |
A word on browser extensions, since they dominate the search results next to pages like this one. An extension that rewrites “Save image as…” so downloads land as PNG solves a slightly different problem: it changes what happens next time, on that browser, on that machine, and it needs permission to see the images you look at. A page like this one converts the files you already have, on any browser, with no install and no permissions. Neither is a substitute for the other, and it is worth knowing which of the two you were actually looking for.
What WebP is, and what a conversion can and cannot recover
WebP is a single container with two quite different compression modes inside it. Lossy WebP borrows predictive coding from the VP8 video codec; lossless WebP works by substituting repeating data. Both modes support an alpha channel, which is the trait that lets one format cover JPEG’s job and PNG’s job at once, and both support animation — MDN describes the ANIM and ANMF chunks that hold frames, and looping. Google’s figures for the gains are 25–34% smaller than comparable JPEG for lossy, 26% smaller than PNG for lossless, transparency in lossless at “just 22% additional bytes”, and lossy files with transparency typically 3× smaller than PNG.
| WebP | PNG | JPEG | |
|---|---|---|---|
| Lossy compression | Yes (VP8 predictive coding) | No | Yes |
| Lossless compression | Yes, as a separate encoder mode | Yes, always | No |
| Transparency (alpha) | Yes, in both modes | Yes | No — never had it |
| Animation | Yes (ANIM / ANMF frames) | No (that is APNG) | No |
| Maximum dimensions | 16,383 × 16,383 px | Effectively unlimited | 65,535 × 65,535 px |
| Opens in older desktop software | Patchy — hence this page | Everywhere | Everywhere |
Read that table in one direction and the conversion advice writes itself. Going from WebP to PNG you keep transparency and add no new loss, and you pay for it in bytes: PNG has no lossy mode at all, so a photograph that arrived as a 90 KB lossy WebP can leave as a PNG several times that size. Going from WebP to JPEG you get the small, universally accepted file, and you pay for it twice — once in the transparency you had to flatten, once in a second generation of lossy compression. Nothing about either direction makes the picture sharper than the file you were given.
Two facts that reliably surprise people. The first is that “convert to PNG to keep the quality” is only half true: the PNG is a faithful copy of the decoded WebP, and the decoded WebP already lost whatever the site’s encoder decided to drop. Quality is set at encode time by whoever published the image, and no downstream converter — this one, an upload site, or a paid desktop app — can reverse that. The second is that a WebP is not automatically smaller than everything else. It is smaller than the JPEG or PNG the same encoder would have produced from the same source, which is a different claim, and on hard cases such as noise-heavy pixel data the ordering can flip. That is why the size of each file is shown here before and after, rather than promising a saving.
FAQ
Why did the image download as a .webp?
Because that is what the site is serving. WebP is Google’s replacement for JPEG, PNG and GIF, and performance tools actively recommend it — Chrome’s Lighthouse audit for modern image formats names AVIF and WebP as having better compression than JPEG and PNG. Browsers advertise WebP support in their request, so the server sends WebP and the browser saves the bytes it received. Right-clicking “Save image as…” does not convert anything; it writes the file the site already sent you.
Does converting WebP to PNG improve the quality?
No, and this is the most common misunderstanding on the subject. If the WebP was lossy, the detail was thrown away by whoever encoded it; PNG simply stores the decoded result faithfully at a much larger size. You get a file more software will accept, not a better image. Converting to JPG is actively worse for quality, because JPEG adds a second round of lossy compression on top — use a high quality setting and avoid re-saving repeatedly.
Can I convert a lot of files in one go?
Yes. Drop or select as many as you like and they are converted one after another, each with its own download. There is no per-file cap and no batch limit to sell you, because there is no server paying for the work — the encoding happens on your own machine. The real constraints are your device’s memory and patience: a hundred small graphics finish quickly, a hundred 24-megapixel photos will take a while and use a lot of RAM.