Why choose PNG instead of JPG?
PNG is useful when a destination requires it or transparent edges and crisp interface graphics matter.
Image WORKBENCH / FREE BROWSER TOOL
Convert WebP to PNG
Make a PNG copy of a WebP image for a workflow that needs PNG, with transparent edges preserved when supported by the source.
No signup · File contents stay on this device Files are processed on this device
Drop your files here
JPG, PNG, WebP, AVIF or HEIC images · files stay on your device
or paste an image with Ctrl / Cmd + VUp to 30 files · 20 MiB per file · 80 MiB total
Sequential processing keeps memory use lower.
Processing happens in your browser. File contents are not uploaded. Close the tab to release active files; temporary handoffs use local browser storage. · Privacy details
IMAGE → DOCUMENT WORKFLOW
Sample checks you can repeat
Measured with the listed sample and settings; these may differ from this page’s starting preset. Timings are individual processing-function runs in the stated environment and exclude page loading. Library caches may be warm. These small-file checks do not establish performance or compatibility for every document.
| Sample | Settings | Observed output | Environment |
|---|---|---|---|
| sample-graphic.webp (1400 × 900; 16,850 bytes) ↗ | PNG; quality 88%; background transparent | approximately 73.9 KB; 1400 × 900 · 0.04 sec | Chrome · Apple M2 / macOS · 15 Oct 2026 · local test |
Specific tasks
Using this tool
How to use webp to png
- Select the WebP image and leave PNG selected as the output.
- Keep its dimensions if you only need a format change.
- Convert and inspect transparency, edge detail, and the actual file size of the PNG.
Before you start
What to keep in mind
- A PNG can be much larger than a WebP without adding any detail.
- Animated WebP files are rejected. Export one still image before converting it to PNG.
- PNG does not reverse quality loss already present in the WebP.
- Use at most 30 images, 20 MiB per file and 80 MiB total input. Combined output is also limited to 80 MiB; completed files remain available when a later result exceeds that limit. Each image must stay within 24 million pixels and 12,000 pixels on either side.
Use PNG for a compatibility requirement
Some editors and submission forms still ask for PNG. Convert once from the best source and retain the WebP in case you need its smaller web version.
Check transparency on a contrasting background
A transparent edge can look correct against white but show a fringe on dark pages. Check against the background where the image will be used.
Keep a transparent product image usable
A still WebP product cutout can display correctly in a browser but be rejected by a document editor expecting PNG. This page starts with PNG output and a transparent background so the operation addresses that compatibility problem without intentionally flattening the cutout onto white. The decoded width and height are retained for an ordinary format conversion; use the separate resizer when the receiving layout needs a different rectangle.
Try the supplied transparent graphic and examine its outside edges on contrasting backgrounds. An alpha channel can carry partially transparent antialiased pixels, so a pale fringe may have existed in the source even when the background looked clear on a white page. The PNG preserves the decoded image; it cannot recreate an earlier uncompressed master or reverse artifacts already present in a lossy WebP. PNG files can become substantially larger than their WebP sources. If a form also imposes a byte limit, move the result to the compressor and verify that any reduced dimensions still meet the form’s requirements. Keep the smaller WebP for workflows that already support it.
Distinguish preserved pixels from preserved file features
PNG output uses the decoded WebP dimensions without a resize operation. The browser creates a new PNG rather than copying the WebP container, so camera fields, embedded color information and other container features should not be assumed to survive. The quality control does not tune PNG in the way it tunes JPEG. Lowering that control is therefore not a reliable way to shrink this export.
If the resulting PNG is too large for an editor or form, first check whether that destination accepts the original WebP. Otherwise choose a separate size-reduction step and inspect its reported dimensions. A successful format change establishes that a PNG was encoded; acceptance by the receiving application is a separate check.
Common questions
About webp to png
Will the PNG be smaller?
Often not. The purpose is format compatibility; compare the real size after conversion.
Will converting restore the original artwork?
No. The new image contains the pixels that can be decoded from this WebP, not an earlier master.
Where is the image converted?
Its contents are decoded and encoded in this browser. The website and any required decoder files load normally, but your chosen image is not uploaded to a conversion API. Initial preparation can require an internet connection.
Can I continue with another image operation?
Yes. After conversion, use the next-step actions to pass successful result files to another compatible tool through temporary local browser storage. Download a copy if you need a lasting artifact.