Convert PNG masters to WEBP for the live site
WEBP carries transparency like PNG and usually ships fewer kilobytes to the browser when you publish the same graphic.
Why sites ask for WEBP after design export
PNG is a safe master format for logos, icons, and UI art. On a live page it often costs more bandwidth than WEBP for the same look. Performance budgets and Core Web Vitals push teams toward lighter encodings without redrawing every asset.
PNG to WEBP is the step after design export: keep a PNG master in the design system, publish WEBP to visitors. Lighthouse and similar recipes flag oversized PNGs in the network waterfall. Converting heroes and icons is ordinary front-end hygiene, not a special campaign.
Marketing sites with many product cutouts feel the weight first. A gallery of PNG transparencies can dominate the request list even when the HTML is lean. Converting that gallery once often moves the needle more than shaving a few lines of script.
Email templates and older desktop apps may still need PNG. Keep both: WEBP on the website, PNG for channels that reject WEBP. Deleting the master PNG after one conversion is how a redesign weekend starts with missing logos.
Transparency stays available when you need it
Unlike JPG, WEBP can keep an alpha channel. Logos, icons, and product cutouts that need a clear backdrop can stay clear after conversion. Spot-check edges on a dark and a light preview. Soft gradients against alpha are the places compression shows first.
Some CDNs recompress WEBP again. Start from a high-quality export so a second pass still looks acceptable. Thin one-pixel strokes on UI chrome need a higher quality setting or a second look at 200 percent zoom.
Photos with no transparency can also become WEBP and often shrink further than a PNG photo ever would. For photographs without alpha, JPG or WEBP are both reasonable; pick based on what your CMS and CDN already optimize well.
If a partner’s brand kit still ships only PNG, convert for your site and leave their kit alone. Do not send them a WEBP and assume every internal tool opens it.
How to convert PNG to WEBP here
Upload the PNG. Choose WEBP output. Start the job, keep the tab open, and download the WEBP when it is ready. Batch UI kits when a folder of PNG icons should become WEBP for a release.
Keep original filenames where possible so template references change only the extension. A find-and-replace from .png to .webp in templates is safer when names match. Document which pages already use WEBP so a future redesign does not reintroduce heavy PNGs by habit.
Measure the byte drop on one representative hero image before you convert an entire design system. The savings on that one file tells you whether the pass is worth scheduling for the full set. Wire the WEBP into templates with a PNG fallback only where analytics show an ancient browser share that still matters for your audience.
Confirm the CMS media library shows the new WEBP URL in the page source after publish so caches are not still serving the old PNG path. Purge CDN caches when the filename stays the same but the bytes changed.
Lossy versus near-lossless choices
When the tool exposes quality, higher settings protect fine lines and cost more bytes. Lower settings shrink harder and can shimmer on thin strokes. Photos tolerate more compression. One-pixel UI chrome needs a higher setting.
Sprites and icon sheets convert well when every tile shares one palette mood. Spot-check the busiest tile, not only the quietest. A single noisy icon can force you to raise quality for the whole sheet.
Near-lossless modes, when offered, favor graphics that must stay crisp. Lossy modes favor photographs and soft gradients. Match the mode to the content instead of applying one slider to every file in the folder.
If two exports look identical at normal zoom but one is half the size, ship the smaller file. Visual parity at the size visitors actually see beats theoretical lossless purity for a marketing hero.
Compatibility on the receiving end
Modern browsers open WEBP. Some older mail clients and desktop apps still prefer PNG or JPG. Keep a PNG fallback when you email a single asset to a mixed audience. For CMS uploads, confirm the platform accepts WEBP before you delete the PNG.
If a partner’s email template blocks WEBP, send PNG for that channel and keep WEBP on the site. Print vendors and some slide tools still expect PNG or JPG. Convert back with WEBP to PNG when you need an editable raster again.
App stores and some ad networks publish their own allowed type lists. Read the current list. Last year’s “WEBP everywhere” advice can still fail a network that lagged on support.
Automated visual regression tests should compare WEBP against the approved look after you switch formats. A one-pixel fringe change on a logo is easy to miss in a casual glance and easy to catch in a diff.
Free use, masters, and cleanup
PNG to WEBP is free on Vidzilla within the tools quota for image jobs. Processed files are removed after download. Archive the PNG master. Deploy the WEBP copy.
Do not treat WEBP as the only file in source control if designers still edit PNG. Masters belong in the design repo; WEBP belongs in the build or media library. Mixing those roles causes someone to edit a lossy file and wonder why edges look soft.
Ordinary icons convert without an account. Huge sprite sheets take longer; leave the tab open and confirm free disk space. Spot-check after download before you delete anything from the design folder.
When a redesign reintroduces PNG heroes by habit, run the conversion pass again and update the checklist. The format choice is a process, not a one-time miracle.
Related format choices on the same site
Use PNG to JPG when alpha is not needed and a partner only accepts JPG. Use WEBP to PNG when you must return to a widely editable raster. Use SVG to PNG when the master is vector and you need a bitmap before WEBP.
Compressors that shrink an existing WEBP or PNG without changing type are useful after the format is already correct. Conversion and compression are different steps. Do the format change first when the page still serves PNG that should be WEBP.
Retina assets often ship as two widths. Convert both, or generate WEBP from each PNG master you already maintain. Skipping the 2x set leaves sharp displays downloading a soft upscale.
Favicons and tiny UI glyphs sometimes gain little from WEBP if they are already a few hundred bytes. Spend the conversion time on heroes, product shots, and large transparent cutouts first.
Questions about PNG to WEBP
Does WEBP keep transparency from PNG?
Yes. Alpha can survive the conversion. Verify edges on dark and light backgrounds after download.
Why not just compress the PNG?
WEBP often beats PNG on size for the same visual. Compression alone on PNG may not match that gain for web delivery.
Will every app open WEBP?
Modern browsers do. Some older desktop and mail apps do not. Keep a PNG when the recipient or channel is unknown.
Is WEBP good for photographs as well as logos?
Yes. Photos convert well. Watch quality on skin tones and fine detail, and keep a master if you will edit again.
Is PNG to WEBP free?
Yes, within Vidzilla’s tools quota for image jobs. Ordinary icons and heroes convert without an account.
Do you keep my image files?
No. Processed files are removed after the download is ready. Keep PNG masters in your own archive.