WEBP
PNG
PNG
ЗАГРУЗИТЬ
ФАЙЛ
Ожидание файла...
Превью
Ожидание файла...
Tool guide
PNG is what you reach for when transparency and crisp edges matter: Figma icons, a logo sitting over a coloured block, an interface screenshot in a deck, or assets for software that has never heard of WebP. Drop in a .webp, the browser decodes it and re-encodes the pixels as PNG with the alpha channel preserved, so a cut-out stays a cut-out. PNG encoding is lossless, so no fresh compression artefacts are added on top of the source.
Yes, and that is the main reason to pick PNG. Both formats carry an alpha channel, so transparent pixels come through unchanged and a cut-out logo stays free of any backdrop. Send the same file to JPG instead and the transparency collapses into a white fill, because JPEG has no alpha at all.
No, the algorithms simply differ. PNG is lossless and stores every pixel exactly; your WebP was almost certainly lossy. On a photograph the PNG can be several times heavier. On flat graphics, screenshots and few-colour icons, PNG is often the smaller of the two.
No new loss is introduced. PNG is lossless and writes exactly the pixels the browser produced when it decoded the WebP. Whatever detail the original WebP already threw away is gone for good — conversion cannot bring it back — but it does not add fresh artefacts either.
The upload field is filtered to image/webp, so a file with another extension will not be selectable. Sometimes an image is saved as .jpg while actually containing WebP data, or the other way round. Check the real format with the format detector and pick the matching converter. A truncated or corrupt download is the other common cause — the browser simply cannot decode it.
No, the page handles one file at a time; the input is not marked multiple. For a handful of images just repeat the loop — pick a file, press DOWNLOAD, press RESET. That is quick for ten pictures, but for hundreds a local batch converter is the sensible tool.
Everything happens inside the tab: the file is opened through the browser file API, drawn onto a canvas and read back out as PNG. Nothing is sent to the IT Market server and no copy is kept on our side. You can disconnect from the network after the page loads and watch the conversion still work.
Browsers do, but the exceptions start right after: several office suites, older Photoshop builds, print drivers, some CMS platforms and document upload forms still reject WebP. PNG has been understood almost everywhere for over twenty years, which makes it the safe format for handing graphics to someone else.
Before: icon-32.webp — 4 KB, 32×32, alpha around the corners of a rounded square.
After: icon-32.png — 32×32, rounded corners still transparent. About 2-3 KB: on small flat graphics PNG often beats WebP outright.
Before: dashboard.webp, 1920×1080, captured by a browser extension. PowerPoint refuses to place it.
After: dashboard.png, 1920×1080, no second round of lossy compression: UI text stays sharp and the file drags straight onto the slide.
Before: product.webp — a cut-out product with a transparent backdrop, taken from a marketplace listing.
After: product.png: the object with no background, ready to sit on any banner colour. The same file sent to JPG would have come back on white.
Your rating and feedback help decide what to improve next.