Why designers and app builders reach for PNG
WebP, introduced by Google in 2010, is very good at shrinking images so web pages load quickly, and every current browser shows it. But once an image leaves the browser — into a design file, a slide deck or an older editor — support gets patchy. Many older desktop apps, print shops, some upload forms and some Office versions still turn it away.
PNG is accepted almost everywhere, and it has two properties that matter for graphics: it is lossless, and it supports full transparency. That makes it the natural target for logos, stickers, icons, UI elements, diagrams and text-heavy screenshots — anything with crisp edges or a background that must stay see-through.
From .webp to .png in four steps
- Bring in the files. Drag WebP images onto the converter above, drop a folder of assets (subfolders included), or paste an image from the clipboard. Up to 500 files fit in one batch.
- Choose PNG as the output. There’s no quality slider for PNG, because nothing is compressed away.
- Optionally cap the size. Pick a maximum long edge of 4096, 2560, 1920 or 1280 px, or leave it at the original size, which is the default.
- Save the results. Download files one by one with their Save links, or grab everything with “Download all (ZIP).”
logo.webpbecomeslogo.png, and duplicate names get “ (2)”.
Lossless or lossy WebP: what the PNG can and can’t give back
WebP files come in two kinds, and which one you have decides what the PNG will look like.
| Your WebP is… | What the PNG contains | Often used for |
|---|---|---|
| Lossless WebP | The same image in a format more apps open, with no new compression loss | Icons, logos, UI assets and screenshots exported for the web |
| Lossy WebP | A faithful snapshot of the WebP as it is, including any blur or blockiness it already had | Photos and banners on most websites |
PNG doesn’t add loss, but it can’t remove it either: smeared edges or banding in a lossy WebP are preserved exactly. What you gain is that nothing further gets lost — you can edit and re-save the PNG as often as you like without it degrading, which isn’t true of WebP or JPG.
Bigger files are the price of lossless
Expect the PNG to be larger than the WebP, sometimes several times larger. WebP was designed to be compact; PNG was designed to keep every pixel exactly. How much bigger depends on the content:
- Flat graphics such as logos, icons and interface screenshots compress well in PNG, so the growth is usually modest.
- Photos and gradients contain fine variation that lossless compression can’t squeeze much, so the PNG can be dramatically larger.
If the image is a photo without transparency and it only needs to open somewhere, WebP to JPG gives you a much smaller file. If you want PNG but smaller, the resize option is the lever to pull: halving the width and height leaves a quarter of the pixels.
Transparency, animation frames and EXIF
Transparency is kept. Fully transparent backgrounds stay transparent, and partly transparent pixels — soft shadows, anti-aliased edges, glows — keep their partial opacity, so a sticker or logo still sits cleanly on whatever background you place it over.
Animated WebP becomes a single frame. The PNG output here is a still image, so an animated sticker or emoji gives you its first frame only.
Photo info goes into the PNG’s eXIf chunk. Most graphics don’t carry EXIF, but if a WebP does (date taken, camera, exposure, GPS location), it is kept by default in the standard eXIf chunk, which some older viewers ignore. You can remove only the GPS location, or untick “Keep photo info” to drop it all. The orientation tag is reset to normal because the pixels are already upright.
Colors are standard sRGB. Your browser’s decoder converts the WebP to sRGB, the color space most screens and viewers assume.
When PNG is the wrong target
- You need a small file for email or a web page. A photo saved as PNG can be unwieldy; JPG, or the original WebP, is a better fit.
- You need a logo that scales to any size. PNG is still made of pixels. Converting won’t create a vector file, and scaling a small image up won’t add detail.
- You want the animation. Only the first frame is converted; GIF and video output aren’t available.
- You want a document. To combine several images into one PDF, use JPG to PDF, which accepts WebP too.
- You have hundreds of files. A batch tops out at 500 files; run several in a row.
The converter works in recent Chrome, Edge and Firefox, and in Safari 16.4 or later on Mac, iPhone and iPad.
Check for yourself that nothing is uploaded
Your images are converted inside this browser tab and never sent anywhere. The page’s Content-Security-Policy allows network connections only to pd00.com and to an anonymous, cookieless page-view counter that never receives your images, so the browser itself blocks every other destination. Open DevTools → Network while converting to see it; our privacy page walks through the steps. After the page has loaded you can even go offline and keep converting.