Convert PNG to WebP Online
Re-encode PNG as WebP — batch a whole folder at once, entirely in your browser, so files never upload and it works offline. WebP keeps transparency (unlike JPG) and is typically 50–80% smaller than the source PNG at the quality you pick, which means faster page loads and better Core Web Vitals. Supported in every major browser since 2020.
Drop PNG / JPG files here
Multiple files allowed
Why WebP instead of JPG or PNG?
- vs PNG: 50–80% smaller for photographs; 20–40% smaller for icons / UI; transparency preserved either way.
- vs JPG: 25–35% smaller at the same visual quality, AND supports transparency.
- Browser support: universal on Chrome, Firefox, Edge, Safari 14+ (Sep 2020), Opera, Samsung Internet. Only ancient browsers struggle.
What quality should I pick?
- 0.95 — near-lossless. Use for archive or when artefacts would be obvious.
- 0.85 — default. Visually identical to source for photos and most UI.
- 0.75 — strong web default. Smaller, no visible damage on photos.
- 0.6 — aggressive. Acceptable for thumbnails or background images.
When to use
- Replacing PNG/JPG on a website. Wrap in
<picture>if you still care about Safari < 14. - Mobile app assets. Smaller bundles, faster CDN loads.
- Bulk re-encoding image archive. Storage savings without losing alpha.
FAQ
Is WebP better than PNG for websites?
For most images, yes — a smaller payload means a faster Largest Contentful Paint and better Core Web Vitals, with transparency still intact. Keep PNG (or use quality 1) only where you need pixel-exact, lossless output. Wrap in <picture> if you still support very old browsers.
Will it preserve transparency?
Yes — WebP supports alpha. Drop a PNG with transparent regions and the WebP keeps them.
Lossy vs. true lossless?
Quality < 1 produces lossy WebP (smaller). Quality 1 is the browser's near-lossless mode. The browser's encoder doesn't expose a separate "true lossless" mode — for that, use cwebp -lossless on the desktop.
Will the WebP open in social-share previews?
Twitter, Slack, Discord, Telegram render WebP fine. LinkedIn and some older preview services still want JPG/PNG — test your specific share path.
What about animated PNGs (APNG)?
Not converted to animated WebP here. Only the first frame is encoded.