In a world without privacy, we create it.

Veldrinby CounterCustody
Download on the App StoreDownload on the App Store
Scan to download VELDRIN on the App Store.
TL;DRWant the short version? Click here.
The problem
Private files sit in a camera roll anyone can scroll, an album anyone can open, or a cloud you don't control.
The fix
Veldrin keeps them in a pattern-locked vault on your iPhone. No account, no vault list, and a red emergency button for when you're pressed to open it.
In short
Google says lossless WebP is about 26% smaller than PNG.

Why you need this

Choosing between formats is a small decision, and losing the original file is a big one. Whatever you convert, the master copy of the pictures you care about should sit somewhere safe and private. Veldrin keeps photos, videos and any file in an encrypted vault on your iPhone, with an encrypted local backup and restore, so a dead or lost phone is not the end of them. Keep the original safe. The app is ready.

Tool · 6 min read

PNG vs WebP: which one should you use

Use WebP for images on web pages, where smaller files load faster. Keep PNG when you need the widest compatibility, will edit the file again, or are handing it to software or a service you don't control.

How much smaller is WebP than PNG, measured

Google's WebP FAQ states that lossless WebP images are 26 percent smaller than PNGs, and MDN calls the same figure typical. The detail is in Google's lossless and alpha study: against PNG files optimized with a heavy tool, WebP lossless came out 23 percent smaller, and against plain libpng output it was 42 percent smaller. The study used about 12,000 PNG images from the web, so it describes web graphics on average, not your particular folder. Flat-color screenshots may save more, and files that are already well optimized may save less.

PNG and WebP compared feature by feature

PNGWebP
CompressionLossless onlyLossless or lossy, chosen when saving
TransparencyYesYes
AnimationNot in normal PNG (APNG exists separately)Yes
Typical size for the same pictureLargerSmaller; about 26% for lossless, per Google
Browser supportUniversalAll current major browsers; Safari 14 or later, and on a Mac, macOS Big Sur or later
Software supportNearly everythingWide, but older editors and print services may not read it

Reading the table: what each row means in practice

Compression is the row that decides most cases. PNG can only be lossless, so a photograph in PNG is large and a screenshot in PNG is fine. WebP lets you choose, which is why it covers both jobs. Transparency is a tie, so it's not a reason to pick either one. Animation matters only if you have animated images: plain PNG has none, and the separate APNG format isn't read everywhere. The size row is the reason web teams switch, and the browser row is the reason they keep fallbacks. The software row is the one people forget until a print shop or a colleague on older software can't open the file.

Which one suits which job

  • A product photo on a shop page: lossy WebP, with a JPEG or PNG fallback if you support old browsers.
  • A logo with a transparent background on a website: lossless WebP, or SVG if the logo is vector. Keep the PNG for everything else that touches it.
  • A screenshot for documentation: PNG if people will download and reuse it, lossless WebP if it only lives on a page.
  • An image you will hand to a client or a printer: PNG.
  • A folder of archived screenshots: lossless WebP saves space, provided you check that your viewers open it.

When WebP is the better choice

  • Web pages. Smaller files mean quicker loads, especially with many images. MDN recommends WebP or AVIF over PNG, JPEG and GIF for raster images where support allows.
  • Photos with transparency. PNG stores a photograph and its alpha channel at a heavy cost. Lossy WebP keeps transparency at a fraction of the size.
  • Storage. If you keep a large library of screenshots, lossless WebP saves space without changing a pixel.

When PNG is still the safer format

  • Sharing with people and tools you don't control. Forms, email programs, print shops and older software accept PNG.
  • Source files you will edit again. PNG is the safe interchange format between editors.
  • When the audience may use old browsers or systems. MDN suggests a PNG fallback inside a picture element for older browsers.
  • Small icons. The saving on a tiny file is a few bytes, which is rarely worth a compatibility question.

Lossless WebP versus lossy WebP

Lossless keeps every pixel and is the right choice when you're converting from PNG and want nothing to change. Lossy WebP discards detail the way JPEG does, and gives much smaller files for photographic content. Converting a PNG to lossy WebP is a one-way trade, so keep the PNG if you may need the original quality again. There is more on the general trade in compressing without losing quality.

Does converting PNG to WebP strip metadata?

Converting with a browser canvas, as the PNG to WebP converter does, writes a new file from pixels, and text chunks and similar fields in the PNG aren't carried across. Other converters may behave differently. If you need those fields kept, use a tool that says it keeps them, and check the result.

A practical way to decide for a whole site

Take five images that represent your site: a photograph, a logo, a screenshot, an illustration and something with a soft shadow. Convert each to lossless and to a lossy quality you'd accept, and write down the byte sizes. Add the totals. If lossy WebP saves most of the bytes on the photographs and lossless WebP saves a useful amount on the graphics, switch those categories and keep PNG masters. If the saving is small on your particular images, leave them alone, because a format change that gains little is still a compatibility decision. Keep every PNG master, since you can always make another WebP from it, but you can't make a lossless PNG from a lossy WebP.

Common mistakes when switching formats

  • Converting a lossy WebP back to PNG and expecting the quality to return.
  • Overwriting the PNG masters after converting.
  • Using one lossy quality for photographs and logos alike.
  • Assuming every program, email client and print service opens WebP.
  • Judging the result on a small preview instead of the real page.

Test it on your own file before deciding

The quickest way to decide is to try your own file. Run it through the converter, read the before and after sizes, and look at the pixel check, which reads the WebP back and compares it with the PNG. The script reads the file in this tab and never sends your picture anywhere, so the picture isn't uploaded. If you later need to reverse it, WebP to PNG does that, and what a WebP file is covers the format itself.

Questions people ask

Is WebP better than PNG?

For file size on the web, usually. For compatibility and for files you'll edit again, PNG is the safer choice, so the answer depends on where the image is going.

Does WebP support transparency?

Yes, in both its lossless and its lossy forms. That's one reason it can replace PNG for logos, cut-outs and photographs that need a transparent background, usually at a smaller file size.

Do I lose quality converting PNG to WebP?

Not if you choose lossless and the encoder really is lossless, which the converter's pixel check confirms. A lossy setting does lose detail, by design.

When should I keep the PNG?

When the file is going to software or a service you don't control, when you'll edit it again, or when a tiny saving isn't worth a compatibility risk.

Is WebP bad for SEO?

This page couldn't verify any such effect. Smaller images can make pages load faster, which is the usual reason to use WebP. Check Google Search's own image guidance for format requirements.

Can I turn a WebP back into a PNG later?

Yes. From a lossless WebP the PNG will have identical pixels, while from a lossy WebP the PNG keeps the loss that's already there.

How do I convert between the two formats?

Use PNG to WebP to make a WebP from a PNG, choosing Maximum quality or Lossy, and WebP to PNG to go back. Both run in your browser tab and check the result.

Sources

VELDRIN

Archive the lossless master beside the web copy in one vault

See Veldrin on the App Store