How to convert WebP images to PNG on Mac

Before you start: system, permissions, and output folder

This guide uses the direct-download version of DropShift for Apple Silicon (M-series) Macs running macOS 14 or later. Download your source files to your Mac and leave enough disk space for a separate output file.

Drag files into the DropShift window and choose an action; this does not require Accessibility permission. To open the format wheel while dragging in Finder, enable Quick Drag in Settings and grant Accessibility permission, then hold Shift during the drag. Hold Shift + Option during the drag to switch to editing tools.

Results are saved beside the source by default, or in the output folder you choose in Settings. New files do not overwrite originals; an available filename is used when a name already exists. If the source folder is not writable, choose a writable output folder when prompted.

Convert a still WebP to PNG

1. Confirm that you saved an image file

   Inspect the source in a viewer that supports WebP, checking dimensions, content, and transparent areas. Some downloads save a web page or error response; a .webp extension alone does not make the contents a WebP image.

2. Drop the image and choose PNG

   Drag one or more WebP images into the DropShift window, then choose PNG. With Quick Drag enabled, drag an image in Finder, hold Shift, move to PNG on the image format wheel, and release.

3. Find the separate PNG file

   The .png is saved in the source folder or your configured output directory. The WebP remains, and an available filename is used if a PNG with the same name already exists.

4. Check transparency and import behavior

   Open the PNG in the destination editor and check pixel dimensions, edges, and color. Inspect transparent edges over both dark and light backgrounds. A viewer displaying a white background does not by itself mean the alpha channel is gone.

PNG suits transparent assets but may be larger

PNG supports an alpha channel and suits still assets with transparent areas. JPEG does not support transparency, so choose PNG for transparent icons or interface assets rather than converting to JPEG first.

PNG compresses decoded pixels losslessly, but it cannot restore detail already lost in a lossy WebP. Conversion does not automatically increase resolution or sharpen a blurry image.

WebP is often used for web delivery, and a PNG version may be substantially larger. If your website or editor already supports WebP and you do not need further editing, keeping the original may be more suitable.

This workflow produces a single still image. Animated WebP is read at its first frame only. Keep the source and use an animation-capable exporter if you need motion, frame timing, or the full animation.

Common WebP conversion problems

• The image cannot be read: confirm the download is complete and contains WebP data that the system can decode. Recognizing an extension does not guarantee a damaged or unusually encoded file can be processed.
• Transparency appears white: inspect the PNG in an editor that displays transparency, then confirm the original WebP actually has an alpha channel. Some assets have white pixels baked into the background.
• The result no longer moves: exporting only the first frame is a limitation of this workflow. Renaming the file or converting it again will not restore the animation.
• Need PNG to WebP instead? Current image output formats are JPEG, PNG, and HEIC. WebP is a recognized input format; this guide does not imply WebP export support.