Crop

Circle crop image Crop image

Optimize

Compress image Remove background Upscale image

Modify

Resize image

Convert

Other

Convert JPG to PDF

Loading your files…

Convert WebP to PNG

Convert WebP to PNG so Photoshop, Word, and older apps can open the file. Transparency kept.

or drop the image here

Quick answer

RoundCut converts WebP to PNG so the file opens everywhere desktop software expects. Convert one image and the browser re-encodes it as PNG on your own machine in under a second. Convert several at once and they go to our server to be processed together into one download, which is then removed within about 2 hours. PNG is the format that desktop applications actually open, since Photoshop in older versions, Word, PowerPoint, Preview, and most legacy tools on Windows and macOS still refuse WebP files. Transparency is preserved exactly as it was in the source, because both WebP and PNG carry an 8-bit transparency channel, so a logo on a clear background converts to a PNG with the same clear background, with no white fill and no edge artifacts. The output PNG is always larger than the source WebP. This is the expected cost of switching to a format that opens everywhere. No new quality loss is introduced by the conversion itself.

How to convert WebP to PNG

How to convert WebP to PNG

Drop a WebP file onto the upload zone, or click to pick a file from your device. The conversion starts the moment the file lands, with no Convert button to press. The result appears in under a second for most images. When it is ready, the Download button saves the PNG using the original filename with the extension changed to .png. To convert another image, drop the next file. Each conversion runs from scratch with no queue. The code works the same on desktop and mobile browsers. An animated WebP is processed as a single still frame, so only the first frame appears in the output PNG.

Transparent backgrounds stay transparent

Transparent backgrounds stay transparent

Both WebP and PNG support full transparency, meaning each area of your image can carry any opacity value from fully clear to fully solid. When the browser reads the WebP and re-encodes it as PNG, the transparency values are transferred intact. A logo on a clear background comes out as a PNG with the same clear background, with no white fill, no halo, and no artifacts at the edges. If the WebP has soft semi-transparent areas such as shadows or anti-aliased text, those precise opacity values survive the round trip. This is the key reason to convert to PNG rather than JPG when the image has a transparent background, since JPG has no transparency channel and would fill those areas with a solid colour.

WebP or PNG, which belongs where

WebP or PNG, which belongs where

Keep WebP when the image lives on a web page. WebP is roughly 25 to 35 percent smaller than PNG at the same visual quality, so pages load faster and bandwidth costs less. Switch to PNG when the file needs to open in something offline. Photoshop versions before late 2022 require a plugin to open WebP. Word, PowerPoint, most legacy Windows tools, and the majority of email clients still refuse WebP. PNG is the format that every app understands. If your final destination is a website, keep WebP. If it is a design file, a print job, an office document, or an email attachment, PNG is the safer choice.

Your output PNG will be larger than the WebP

Your output PNG will be larger than the WebP

PNG uses exact compression. WebP uses a more modern and efficient algorithm that achieves smaller files for the same image. Going from WebP to PNG always grows your file, roughly 26 percent larger for graphics and two to ten times larger for photographs. A large photographic WebP can easily become several times heavier as a PNG. This is the cost of switching to a format that opens everywhere, since the PNG is not lower quality, it just takes more space because it stores every detail without the modern compression WebP uses. If file size matters more than compatibility, keep your WebP instead of converting.

Where your WebP is processed

Where your WebP is processed

It comes down to how many files you convert at once. Convert a single WebP and the re-encode runs inside the browser tab on the platform image engine, with nothing uploaded and nothing logged about the file. Open the Network panel in the developer tools and watch while you convert one image, and you see zero outbound requests carrying it. Convert several WebP files together and they are sent to our server, which produces one combined download for you. That result is removed from our server within about 2 hours, and you can delete it yourself as soon as it is saved. Most other WebP to PNG converters upload every file you give them, single or not, and keep it on their machines. Here a single conversion stays in the tab, and a batch reaches our server only long enough to assemble your download.

What happens with animated WebP files

What happens with animated WebP files

Animated WebP files contain multiple image frames. This tool processes the first frame only and outputs a single still PNG. The PNG format supports animation through the APNG extension, but this tool does not produce APNG files. If you need to preserve every frame of your animated WebP, a dedicated GIF or APNG conversion tool is the right choice. For extracting a single representative frame, such as a thumbnail or a preview image, the first frame is typically the most useful output and the right default behaviour.

How it works

  1. Drop or pick your WebP

    Drag a WebP file onto the upload area or click to open a file picker. Transparency in the WebP will be preserved in the output. Converting one file runs on your machine, while dropping several at once sends them to our server to process together.

  2. Wait for the automatic conversion

    The browser writes the PNG the moment the file loads. Most images at screen resolution finish in under a second with no button to press.

  3. Note the output size

    The PNG will be noticeably larger than the source WebP. A large photographic WebP can grow to several times its original size as PNG. This is expected and not an error.

  4. Download the PNG

    Click Download to save the file. The original filename is kept with the extension changed to .png. Transparent areas remain transparent. To convert another file, drop the next WebP.

Related tools you might also need

Convert in the other direction, or explore other formats for your image.

PNG to WebP — shrink your PNG for the web WebP to JPG — drop transparency for email and print All converters — see every format pair

Frequently asked questions

Why can't Photoshop or Word open my WebP file?

WebP is a modern web format, and a lot of desktop software still ignores it. Photoshop only added native WebP support in late 2022, so older versions need a plugin. Word, PowerPoint, Preview on older macOS versions, and most legacy Windows tools simply refuse the format. Converting to PNG is the universal solution. Every application that handles images at all will open a PNG, making it the right choice when compatibility with desktop software matters.

Does this converter preserve transparency?

Yes, it is. Converting to PNG is the only right move if your image has a clear or semi-clear background and you need it to stay that way. JPG fills all clear areas with a flat colour, so the transparency simply disappears. PNG keeps it intact because the format carries the same transparency information that WebP stores. The practical test is straightforward: if a cut-out product photo, a logo, or any graphic with a clear background looked fine in the WebP, it will look identical in the output PNG. The opacity values are transferred exactly, with no edge halos and no pre-multiplied artifacts at soft edges like shadows.

Why is the PNG file larger than the WebP?

PNG is exact and WebP is more compressed. PNG stores every detail exactly, using a compression method from the 1990s. WebP uses modern prediction techniques that fit the same image into less space. Going from WebP to PNG always grows your file, about 26 percent for graphics and often two to ten times for photographs. A large WebP photo can become several times heavier as a PNG. This is expected, the price of a format that opens everywhere.

Does converting WebP to PNG lose quality?

The conversion itself introduces no new quality loss. PNG stores detail exactly, so the appearance decoded from the WebP is written faithfully. However, if your original WebP was saved in compressed mode, which most web WebP files are, those existing compression artifacts are already in the image and cannot be removed by converting to PNG. The PNG looks identical to how the WebP appeared on screen, not better. No quality is added, further quality loss is simply stopped.

Is it safe to convert WebP to PNG here?

It depends on how many files you convert. A single WebP is converted right on your machine, so that file is never uploaded. You can confirm it by opening the Network panel in the browser developer tools and watching during the conversion, where no outbound image request appears. When you convert several at once, they go to our server to be processed together, and that result is removed within about 2 hours, with the option to delete it yourself once you have downloaded it. If your image is sensitive, converting it one at a time keeps it on your machine.

What happens to animated WebP files?

Only the first frame is converted. This tool outputs a single still PNG, not an animated APNG, even when the source WebP contains multiple frames. If you need to preserve every frame, a dedicated GIF or APNG conversion tool is the appropriate choice. For most use cases, where you just need a static thumbnail or a preview from an animated WebP, the first frame is the right output.

The details

Notes from the team on craft, formats, and the small decisions behind a good result.

Why WebP is not universally supported in desktop apps
WebP was released by Google in 2010, but adoption by desktop software lagged far behind browser support. Browsers adopted WebP early because they control their own rendering engines and Google actively optimized Chrome's WebP support as a competitive advantage. Desktop applications take longer to adopt a new image format because each application maintains its own image decoding stack, and supporting a new format requires testing against a long tail of edge cases. Adobe Photoshop, used by the majority of professional photographers and designers, did not ship native WebP support until version 23.2 in late 2022. Microsoft Office applications still handle WebP inconsistently across platforms as of 2026. Print RIP software and most legacy archiving tools never adopted WebP at all. The practical consequence is that a file that displays perfectly in a browser may be refused entirely by the software the user needs, and converting to PNG is the reliable workaround.
How WebP achieves its compression advantage over PNG
PNG uses a general-purpose exact compression method from 1996. It applies a set of reversible line filters before compression and encodes the result with a standard stream. This is effective but designed before video codec research produced better techniques. WebP lossy mode uses a block-based transform derived from VP8 video compression, applying intra-frame prediction and a frequency transform to large block units. WebP exact mode uses spatial prediction, colour transformation, and a coding stage that is structurally more efficient than PNG's approach for typical image content. Google's published benchmarks show exact WebP about 26 percent smaller than PNG on a standard set of test images, and compressed WebP with transparency about three times smaller than PNG at comparable visual quality. The PNG-to-WebP direction exploits these gains, the WebP-to-PNG direction reverses them, hence the larger output.
Measured file size growth examples
Measured on Chrome 148, Linux desktop, using the platform PNG encode path applied to decoded WebP inputs. A small vector-style graphic at a compact size, saved as WebP at quality 80, decodes and re-encodes as PNG in roughly 15 to 25 ms with a typical file size growth of 20 to 30 percent. A photographic WebP at a typical screen resolution decodes and re-encodes to PNG in under 100 ms with a typical growth of three to five times. A large photographic WebP at a high display resolution encodes to PNG in about 1.2 seconds with growth of five to ten times depending on scene complexity. These numbers reflect the difference in compression efficiency between the two formats and scale with overall image dimensions.
Alpha transparency in the round trip
The transparency channel in WebP and PNG uses the same value range, where zero means fully clear and the maximum value means fully solid. When the browser decodes a WebP with transparency, it produces an image buffer where the transparency component reflects the original data. When that buffer is re-encoded as PNG, the PNG encoder writes the transparency values into the PNG's transparency channel directly. No compositing step occurs, no background colour is applied, and no pre-multiplication side effects change the values. The result is a faithful transfer of the transparency channel, where every area's opacity in the PNG matches what the WebP stored. For images with fine anti-aliasing at edges, each intermediate opacity value survives the round trip intact. This fidelity is what makes PNG the right choice over JPG when the destination application needs to display the image on multiple backgrounds.
EXIF and metadata behavior
The re-encode pipeline strips EXIF, IPTC, and XMP metadata from the PNG output. WebP files can carry EXIF data embedded in their metadata chunk, and that data is lost when the browser decodes and re-encodes the image. ICC color profiles follow a different path, where Chrome and Safari preserve the sRGB ICC profile tag in the PNG output after decoding WebP, and Firefox strips all metadata including the ICC profile. The practical consequence is sRGB-safe output across all browsers, but any wide-gamut profile embedded in the source WebP does not survive in Firefox. For professional photographic workflows that rely on ICC-tagged round trips, use a metadata-aware conversion tool. For standard web image handling, metadata removal is typically acceptable and has the small benefit of slightly reducing output file size.
Privacy verification in practice
The claim that a single file is processed without uploading can be checked without any special tools. Open your browser, navigate to the webp-to-png page, then open the developer tools. Switch to the Network tab, clear any existing requests, and run a conversion by dropping a WebP file. Filter the request list by Fetch, XHR, or All. The list shows zero outbound requests containing image data during the encode. The only network requests present are the initial page load assets and standard analytics pings, which record page views and performance data only, with no image content. Every major remote WebP to PNG converter generates at minimum an upload POST and a download GET per conversion, both logged on the server. The local-first architecture means those log entries do not exist, which is the meaningful difference for users converting files that carry sensitive content.