Crop

Circle crop image Crop image

Optimize

Compress image Remove background Upscale image

Modify

Resize image

Convert

Other

Convert JPG to PDF

WebP to PNG for Apps That Still Need PNG

Make a stubborn WebP open in Photoshop, Word, and older apps by turning it into a PNG.

or drop the image here

Quick answer

Araluma turns a WebP into a PNG so the file lands in software that still refuses WebP. Hand it one and the browser rebuilds it as a PNG on your own device in under a second, so that single file never goes anywhere. Hand it several at once and they ride to our server, which works through them together into one download, then clears that download within about 2 hours. PNG is the format desktop software will actually accept, since older Photoshop builds, Word, PowerPoint, Preview, and a long list of legacy Windows and macOS tools still turn WebP away. Transparency carries over pixel for pixel, because both WebP and PNG hold an 8-bit alpha channel, so a logo or product cut-out on a clear background lands as a PNG with the same clear background, no white fill, no fringed edges. The PNG always weighs more than the source WebP, where a 3 MB WebP photo tends to balloon to about 14 MB as PNG and plain graphics swell around 26 percent. That is the fair price of a format that opens everywhere. The conversion itself adds no fresh quality loss.

How to convert WebP to PNG

How to convert WebP to PNG

Pull a WebP into the drop area or click to browse for one. Work begins the second it lands, with no Convert button anywhere, and for most images the PNG is ready in under a second. A Download button then saves it under the source name with a .png ending. To do another, drop the next file, and each one runs fresh with nothing queued behind it. The same path serves phones and desktops alike. Feed it an animated WebP and it keeps only the opening frame, since the PNG it writes here is a single still rather than a moving sequence.

Transparent backgrounds stay transparent

Transparent backgrounds stay transparent

Both WebP and PNG carry 8-bit alpha, so every pixel can hold any opacity from fully clear to fully solid. As the browser reads the WebP and rewrites it as PNG, those alpha values move across whole. A logo on a clear background lands as a PNG with the very same clear background, no white fill, no halo, no pre-multiplied edge mess. Where the WebP had soft partial edges, drop-shadows or anti-aliased lettering, those exact opacity levels survive the trip pixel by pixel. This is the core reason to head for PNG rather than JPG when the picture has a clear background, since JPG owns no alpha and would have to paint those pixels a solid color.

WebP or PNG, which belongs where

WebP or PNG, which belongs where

Picture headed for a browser? Leave it as WebP, which carries about a quarter to a third less weight than PNG for the same look, trimming load time and bandwidth bills. Picture headed somewhere offline? That is when PNG earns its place. A Photoshop older than late 2022 wants a plugin before it will touch WebP, and Word, PowerPoint, the older Windows utilities, and most email programs simply will not take it. A PNG, by contrast, opens in essentially anything. So the rule of thumb runs like this, website means WebP stays, while a design file, a print run, an office doc, or an email attachment means PNG is the dependable choice.

Your output PNG will be larger than the WebP

Your output PNG will be larger than the WebP

PNG runs on lossless DEFLATE compression, while WebP uses a newer, tighter algorithm that fits the same picture into fewer bytes. So going from WebP to PNG always adds weight, around 26 percent for graphics and anywhere from two to ten times for photographs. A 3 MB WebP photo can comfortably balloon into a 14 MB PNG. That is the toll for a format that opens anywhere, and it does not mean the PNG looks worse, it just claims more disk because it records every pixel without the modern squeeze WebP applies. When small size outranks broad compatibility for you, the better move is to keep the WebP rather than convert it.

Where the WebP actually gets converted

Where the WebP actually gets converted

It comes down to how many you convert at once. Convert a single WebP and the rebuild runs in the tab on the browser's own image engine, with nothing uploaded and nothing about the file logged. Pop open DevTools, keep the Network panel up as you convert that one image, and you tally zero outbound requests carrying it. Convert a few WebP files together and they ride up to our server, which sends back one combined download. That result is cleared from our server inside roughly 2 hours, and you can wipe it yourself the moment it is saved. Most other WebP to PNG sites ship every file off, single or not, and keep it on their machines. Here one conversion stays in the browser, and a batch reaches our server only long enough to put your download together.

What happens with animated WebP files

What happens with animated WebP files

An animated WebP holds several frames stacked together. This tool reads only the first and writes out a single still PNG. PNG can carry animation through its APNG extension, but Araluma does not produce APNG files here. If you need every frame of an animated WebP kept, a dedicated GIF or APNG converter is the tool for that. When all you want is one representative frame, a thumbnail or a preview, the opening frame is usually the most useful pick and the sensible default.

How it works

  1. Hand over a WebP

    Whatever transparency sits inside is kept. To begin, let a file fall into the drop zone or browse for one on disk. Convert one and it never goes online, drop several and they ride up to our server to be handled together.

  2. Sit back

    You do nothing more. Most pictures become a PNG roughly as quick as your finger lifts, with no Convert step and no spinner along the way.

  3. Mind the growth

    The PNG will outweigh the WebP by a wide margin. Picture something near 14 MB out of a 3 MB photo, which is the format working as intended.

  4. Keep your PNG

    One tap on Download writes it out, old name, fresh .png ending. Clear stays clear. Another waiting? Toss the next WebP onto the page.

Frequently asked questions

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

It is a young web format that a lot of desktop programs never learned to read. Photoshop waited until late 2022 to handle it natively, so anything older leans on a plugin. Word, PowerPoint, Preview on the older macOS releases, and a heap of legacy Windows utilities just say no. PNG is the cure, because effectively every image-aware app on the planet opens one. When the goal is getting the file into desktop software, that universal reach is exactly what makes PNG the answer.

Does this converter preserve transparency?

It does. An 8-bit alpha lives in both formats, so a fully clear pixel stays clear, a half-clear one holds its precise opacity, and nothing paints a white box or a fringe behind your cut-out. Hand it a logo floating on a clear background and you get a PNG floating on that same clear background, exact down to the pixel. JPG cannot manage this, which is the whole reason PNG, not JPG, is where a transparent image belongs, since JPG would drop a solid color into every clear spot.

Why is the PNG file larger than the WebP?

One is lossless and the other is packed tighter. PNG keeps every pixel exactly with a 1990s algorithm, while WebP uses newer prediction to squeeze the same picture into far less space. Reverse that and the file has to grow, around a quarter larger for graphics and often several times over for photographs. A 3 MB WebP photo can reach 14 MB once it is a PNG. None of that is a fault, it is simply what you pay for a file that opens anywhere.

Does converting WebP to PNG lose quality?

The conversion adds no new loss. PNG is lossless, so the pixels decoded from the WebP are written byte for byte. That said, if the WebP was saved lossy, as most web WebP files are, those compression marks already sit in the pixels and converting to PNG cannot lift them out. The PNG matches how the WebP looked on screen, not better. Nothing is gained, the slide is simply stopped where it stood.

Is it safe to convert WebP to PNG here?

It hinges on how many you convert. A single WebP is rebuilt right in the browser, so that file is never uploaded, and you can verify it by opening DevTools and watching the Network panel mid-conversion, where no outbound image request shows up. Convert several at once and they ride to our server to be handled together, then that result is cleared within roughly 2 hours, and you can remove it yourself once you have saved it. If the picture is sensitive, a document, a personal photo, or work material, converting it one at a time keeps it on your device.

What happens to animated WebP files?

Only the opening frame is converted. Araluma writes a single still PNG, not an animated APNG, even when the WebP holds many frames. If keeping every frame matters, a dedicated GIF or APNG converter is the right tool. For most needs, where you just want a static thumbnail or a preview pulled from an animated WebP, that first frame is the output you want.

The details

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

Why WebP is not universally supported in desktop apps
Google put out WebP back in 2010, yet desktop software trailed browsers by a wide margin in picking it up. Browsers took to it early because they own their rendering engines and Google leaned on Chrome's WebP support as a competitive edge. Desktop apps move slower on any new image format, since each one carries its own decoding stack and a fresh format means testing against a long tail of awkward cases. Adobe Photoshop, the daily tool of most professional photographers and designers, only shipped native WebP support in version 23.2 late in 2022. Microsoft Office programs still treat WebP unevenly across platforms as of 2026. Print RIP software and the bulk of legacy archiving tools never took it up at all. The upshot is that a file looking flawless in a browser can be flatly refused by the very program the user needs, and converting to PNG is the dependable way around it.
How WebP achieves its compression advantage over PNG
Under PNG sits DEFLATE, a lossless workhorse dating to 1996. It first sweeps reversible filters across each scanline, then pipes the result through a zlib stream, solid work, but from an era before video-codec and machine-learning research sharpened the craft. WebP brings two newer tricks. In lossy mode it pulls a block-based transform out of VP8 video, running intra-frame prediction and a cosine transform over 16x16 macroblocks. In lossless mode it weaves spatial prediction together with a color transform and an LZ77 stage that simply packs typical image data tighter than DEFLATE manages. Google's own measurements land lossless WebP roughly 26 percent below PNG on a standard set, and lossy WebP with alpha near a third of PNG at the same visual quality. Heading PNG to WebP banks those savings, so heading WebP back to PNG returns them, and the file swells.
Measured file size growth examples
These come from Chrome 148 on a Linux desktop, writing PNG over WebP inputs the browser had decoded. Take a small vector-style graphic at 400x300 stored as WebP quality 80, and it rewrites to PNG in something like 15 to 25 ms while gaining a fifth to a third in size. A photographic WebP at 1024x768, call it 100 to 200 KB, rewrites to PNG inside 100 ms and puffs up three to five times over. Push to a hefty photographic WebP at 3840x2160, roughly 1 to 3 MB, and the PNG takes about 1.2 seconds to write while growing five to ten times depending on how busy the frame is. At the far end, a 3 MB WebP photo can land near 14 MB as a PNG. Each figure reflects how much tighter WebP packs the same pixels, and the growth rises in step with the pixel count.
Alpha transparency in the round trip
WebP and PNG share the same 8-bit alpha range, where 0 means fully transparent and 255 means fully opaque. When the browser decodes a WebP that carries alpha, it builds a pixel buffer of RGBA values whose A component mirrors the original alpha. Re-encoding that buffer as PNG writes those A values straight into the PNG's own alpha channel. No compositing happens, no background color is laid down, and no pre-multiplication quietly shifts the pixels. The outcome is a lossless handover of the alpha, where each pixel's opacity in the PNG equals what the WebP held. On images with delicate anti-aliasing at the edges, every in-between value, say a pixel at 40 percent opacity along a letter's edge, comes through the trip whole. That fidelity is what tips the choice to PNG over JPG whenever the receiving app has to show the image against more than one background.
EXIF and metadata behavior
Rebuilding the picture wipes its EXIF, IPTC, and XMP fields off the resulting PNG. A WebP can stash EXIF inside a metadata chunk, and that chunk vanishes once the browser decodes and rewrites the file. Color profiles follow their own path. Chrome and Safari hold the sRGB profile tag on the PNG after reading the WebP, whereas Firefox sweeps everything away, the ICC profile with it. That leaves an output every browser reads as sRGB-safe, yet a wide-gamut profile tucked inside the source WebP will not make it through Firefox. If your photo pipeline lives on ICC-tagged round trips, pick a converter that minds metadata on purpose. For ordinary web work, losing those fields is usually welcome and shaves a touch off the file besides.
Privacy verification in practice
You can check the single-image path with nothing but the browser. Open DevTools with F12 or the right-click menu, switch to the Network tab, clear whatever is listed, and convert one WebP by dropping it. Filter by Fetch, XHR, or All. Nothing carrying image data appears during the encode, because a lone conversion runs entirely on your device. The only requests are the initial page assets and ordinary analytics pings, which log page views and Core Web Vitals only, never your image. The batch path is different by design, where convert several files at once and they are sent to our server to be processed together, so the Network panel will show that upload. That batch download is cleared from our server within roughly 2 hours, and you can delete it yourself as soon as you save it. So one file is verifiably on-device, and a batch is on our server only long enough to build the download you take away.