How to convert PNG to WebP on Mac (batch, offline, 2026)

You ran Lighthouse, or PageSpeed Insights, or your framework’s build report, and there it is again: “Serve images in next-gen formats.” The folder of PNGs behind your site — screenshots, product shots, diagrams, the hero image — is costing real bytes on every page load, and the fix it wants is WebP. Or the trigger is simpler: a CMS, a theme, or a marketplace now asks for WebP uploads, and everything you have is .png.

Either way you need to convert PNG to WebP on a Mac, and here you hit a genuinely odd gap in the platform: macOS reads WebP everywhere and writes it nowhere. Preview opens a WebP like any image — and offers no WebP in its Export menu. The Finder Quick Action that converts images by right-click outputs only JPEG, PNG, and HEIF. The built-in tools are a one-way street: fine for rescuing a WebP download back to PNG or JPG, useless for going the other direction.

So this guide covers the two routes that actually work — Google’s own free command-line encoder, and the drag-a-folder app route — both running entirely on your Mac, offline, with transparency surviving the trip.

In this guide8 sections

What converting PNG to WebP actually buys you

PNG is lossless and universally supported, which is why it’s the default output of every screenshot tool and design export on Earth. It’s also, by modern standards, heavy. WebP was designed at Google specifically to replace it (and JPG) on the web, and the wins are real:

• Lossless WebP is typically 25–35% smaller than the same PNG — identical pixels, smaller file. For graphics, icons, and screenshots this is close to free money.
• Lossy WebP is dramatically smaller again — a photographic PNG that weighs 2 MB routinely becomes a 150–300 KB WebP at a quality nobody can distinguish in a browser.
• Transparency survives. Unlike JPG, WebP carries a full alpha channel in both modes, so this is the rare size win that doesn’t cost you transparent backgrounds.
• Support is universal now. Every current browser — Safari included, since macOS Big Sur — renders WebP. The “but old Safari” objection expired years ago.

The one thing to keep straight is the fork inside WebP itself, because it decides everything about quality:

• Lossless mode — a perfect pixel-for-pixel copy, like PNG but better compressed. Right for logos, icons, UI screenshots, charts, anything with text or sharp edges.
• Lossy mode — JPG-style compression, tuned better. Right for photographs and anything photographic, where quality 75–85 is visually transparent at a fraction of the size.

Convert a screenshot with lossy WebP and text edges go slightly fuzzy; convert a photo with lossless WebP and you leave most of the savings on the table. Match the mode to the image and WebP is simply better than PNG for anything headed to a browser.

Skip the web converters — especially for this job

Search “png to webp” and the first page is upload-a-file converter sites. The usual objections apply — you’re uploading your files to a stranger’s server to do work your Mac does locally in milliseconds — but this job adds two more. First, the whole point is a folder, not a file: nobody converts one PNG for a website, and the free tiers cap batch counts precisely to sell you a subscription. Second, the images involved are often exactly the ones that shouldn’t travel: unreleased product shots, client work, screenshots of internal tools. Both methods below run fully offline — Wi-Fi off, nothing leaves the machine.

Method 1: cwebp (free, command line)

The reference encoder comes from Google itself, and Homebrew has it:

brew install webp

That installs cwebp (and its decoding sibling dwebp). One photographic PNG, lossy at quality 80:

cwebp -q 80 image.png -o image.webp

One graphic — logo, icon, screenshot — losslessly:

cwebp -lossless image.png -o image.webp

A whole folder, in a shell loop:

cd ~/Sites/assets
for f in *.png; do
  [ -e "$f" ] || continue
  cwebp -q 80 "$f" -o "${f%.*}.webp"
done

Transparency is preserved automatically in both modes — no flag needed. The quality scale runs 0–100; 75–85 is the sweet spot for photos, and going above 90 balloons the file for gains no browser viewer will see.

cwebp is the complete free answer if you live in Terminal: it’s the canonical encoder, it’s scriptable, and build pipelines the world over wrap exactly this binary. Its costs are the usual command-line ones — no preview, one mode per invocation (the loop above encodes your logo lossily unless you special-case it), and output files landing next to sources unless you manage paths yourself. For a build step, perfect. For “make this folder web-ready before lunch,” read on.

Method 2: Zumkor (drag the folder, pick WebP, done)

If WebP conversion is a recurring chore rather than a pipeline step — assets before every deploy, listings images, a screenshots folder that feeds documentation — this is the shape of job Zumkor is built around (it needs macOS 14 or later on an Apple silicon Mac — any M-series machine):

1. Open Zumkor and drag in the PNGs, or the whole folder — subfolders included if you tick “Look inside subfolders”.
2. Pick WebP as the output format.
3. (Optional) Pick a resize preset if the sources are oversized — “Web small” (1280 px) or “Web large” for hero-size — since a 5K screenshot doesn’t need 5K on a web page, and resizing saves more bytes than any format change.
4. Click Convert and choose the output folder. The WebP files land there — mirrored to the original folder layout if you want — and the source PNGs stay untouched.

Everything runs on-device and offline, the queue takes up to 2,000 files, and conversions keep running with the window closed. Transparency carries through automatically. It reads more than PNG, too — the same drag converts the JPGs, HEICs, and TIFFs mixed into the same asset folder to WebP in one pass, instead of one loop per extension.

For hands-off pipelines there’s a headless option: Zumkor’s “Convert Files” action in Apple’s Shortcuts app runs in the background, so a folder-watch automation can turn every PNG that lands in an assets folder into a WebP without the app ever opening a window.

Zumkor is free for 7 days, full-featured; after that it’s a one-time $19.99 purchase — buy once, keep it forever, no subscription. The honest trade-off: for a scripted build step, cwebp is free and exactly right. Zumkor earns its slot when the batch is ad-hoc, the folder is deep, the formats are mixed, and you’d rather pick “WebP” once than maintain a shell loop with a lossless special case.

WebP or AVIF? (Since you’re already here)

Lighthouse’s “next-gen formats” hint covers two formats, and Zumkor writes both. AVIF compresses photographs even harder than WebP — often 20–40% smaller again — at the cost of slower encoding and marginally younger browser support (universal in current browsers, missing in truly old ones). A reasonable 2026 policy:

• Graphics, icons, screenshots, anything transparent: lossless WebP. AVIF’s wins are photographic; WebP lossless is the safe, small, sharp choice here.
• Photographs where every byte counts — hero images, galleries: AVIF, via Zumkor’s “AVIF web” preset. (Coming from AVIF instead, because some tool won’t open it? That direction has its own guide.)
• Can’t decide: WebP. It’s the format with a decade of universal support and no surprises.

Whichever you pick, keep the PNG originals somewhere. Lossy conversions are one-way — regenerating a WebP at a different quality from the source PNG costs nothing, but resurrecting a PNG from a lossy WebP just gives you a big file of the same lossy pixels.

Getting the output right

• Resize before you admire the compression. The biggest byte-saver isn’t WebP — it’s not shipping a 4000-pixel screenshot into a 800-pixel layout. Resize to roughly the largest size the page displays (retina = 2× the CSS pixels), then let WebP compress it.
• Lossless for text, lossy for photos. The single decision that matters. Fuzzy text in a converted screenshot means it went through lossy mode; a suspiciously large photo means it went through lossless.
• Check transparency on a dark background. Alpha survives conversion in every tool here, but verify the source actually had it — a PNG exported flattened stays flattened, and no format change brings the transparency back.
• Strip metadata on the way out. Screenshots and exports can carry more than you’d expect. Zumkor can strip personal data as part of the conversion — the same machinery as removing EXIF from photos — which is worth flipping on for anything public.
• Don’t re-convert WebP to WebP. Tuning quality? Go back to the PNG original each time. Stacking lossy passes compounds the damage exactly like re-saving a JPG.

Bottom line

• One-way street, remember: macOS opens WebP everywhere but exports it nowhere — Preview, Quick Actions, and the built-ins can’t make one.
• Build pipeline or Terminal-comfortable: brew install webp, then cwebp -q 80 in.png -o out.webp for photos, -lossless for graphics, a loop for folders. Free and canonical.
• A folder (or a habit), mixed formats, no scripts: Zumkor — drag the folder, pick WebP (and a resize preset if the sources are huge), convert offline in one pass. Free for 7 days, then one-time $19.99.
• Before any of it: resize to the size the page actually displays, and keep the PNG originals — lossy conversions are one-way.

The PNGs aren’t wrong — they’re just paying a size tax every time a browser downloads one. Twenty minutes and one folder-drag ends it, without a single image leaving your Mac.

FAQ

Can Preview export WebP on a Mac?

No. Preview opens WebP files fine, but its Export menu has no WebP option, and the Finder Quick Action converts only to JPEG, PNG, and HEIF. macOS reads WebP everywhere but ships nothing that writes it. To create WebP files you need a third-party tool: Google’s free cwebp command-line encoder via Homebrew, or a converter app like Zumkor for drag-and-drop batches.

Does converting PNG to WebP keep transparency?

Yes. WebP supports a full alpha channel in both its lossy and lossless modes, so logos, icons, and cut-outs come through with their transparent backgrounds intact — unlike a conversion to JPG, which flattens transparency to white. Just convert and check the result over a dark background; no special flag or setting is needed in either cwebp or Zumkor.

Should I convert my PNGs losslessly or lossy to WebP?

Match the mode to the image. Graphics — logos, icons, UI screenshots, anything with flat color and sharp edges — should use lossless WebP, which typically still lands well under the PNG’s size with pixel-identical output. Photographic images should use lossy WebP at quality 75–85, where the savings are dramatic and the difference is invisible at web sizes. When in doubt, try lossless first and switch to lossy if the file is still too big.