Back to Blog

PNG, WebP, AVIF, TIFF, and SVG: Which Format for Transparency

A practical comparison of every image format that supports transparency, when each one is the right choice, and the compatibility traps that turn a good cutout into a white box.

September 4, 202610 min readTechnology

By Ahmet C. Toplutaş · Last updated September 4, 2026 · Editorial standards

Once you have a clean cutout, the next decision is what to save it as, and the answer is genuinely different depending on where the file is going. A format that is ideal for a website hero image is the wrong choice for a print handoff, and the format your design tool defaults to is often neither. This is a practical comparison of the five formats that actually support transparency, with the specific cases where each one wins.

First, the thing that trips everyone up

JPEG does not support transparency. It never has and it never will, because the format has no alpha channel in its specification. Any transparent region in a JPEG is flattened to a solid colour, almost always white, at the moment of saving. This sounds obvious written down, and yet it remains the single most common cause of a cutout arriving with a white box around it, because JPEG is the default export in a lot of software and the preview thumbnail often still looks correct.

If you take one thing from this article: check the file extension of your export before you check anything else.

PNG: the safe default

PNG is lossless and supports a full 8-bit alpha channel, meaning 256 levels of transparency per pixel, which is enough for convincing soft edges on hair and shadows. Support is universal; there is no meaningful platform, CMS, marketplace, or application released in the last two decades that cannot open a PNG with transparency.

The cost is file size. Lossless compression on a photograph is not very effective, so a full-resolution transparent product shot can easily reach several megabytes. There is also a subtlety worth knowing: PNG-8 uses a 256-colour palette and only supports binary transparency, so a photographic cutout saved as PNG-8 gets a hard, jagged outline. When an export dialog offers a choice, photographs need the 24-bit option with alpha, sometimes labelled PNG-32.

Use PNG when: you are handing a file to someone else, uploading to a platform whose format support you have not verified, or keeping a master copy you will convert from later.

WebP: the right answer for the web

WebP supports alpha in both its lossy and lossless modes, and that lossy-with-transparency combination is the interesting part, because no other widely supported format offers it. It means you can compress a transparent photograph the way you would compress a JPEG while keeping the alpha channel intact, which typically produces files 25 to 35 percent smaller than the equivalent PNG at visually identical quality.

Browser support has been complete for years across Chrome, Firefox, Safari, and Edge. The gaps are outside the browser: some older design tools, a few marketplace uploaders, and most print workflows still do not accept it. That makes WebP excellent for serving images and poor for handing files to people.

Use WebP when: the file is being served on a website and page weight matters. Generate it as a build step from a PNG master rather than making it your working format.

AVIF: smallest files, newest format

AVIF compresses harder than WebP, often meaningfully so on photographic content, and it supports alpha along with a wider colour gamut and higher bit depth. For a large transparent hero image it can be the difference between 400 KB and 150 KB.

Two caveats keep it from being an automatic choice. Encoding is slow compared to the alternatives, which matters if you are processing hundreds of images in a build pipeline. And support outside browsers is still patchy enough that AVIF should be treated purely as a delivery format, served with a WebP or PNG fallback rather than used as anything you store or share.

Use AVIF when: you control the serving layer, can provide a fallback, and are optimising a page where image weight is the bottleneck.

TIFF: the print and archive format

TIFF supports alpha channels, 16 bits per channel, CMYK colour, and embedded colour profiles. None of that matters for web work, and all of it matters for print. If a cutout is going into a printed catalogue, a packaging layout, or anything a production house will handle, TIFF is what they will ask for, and sending a PNG instead usually means someone converts it and the colour management decisions get made by accident.

Files are large, sometimes very large. TIFF is not a delivery format and should never appear on a website.

Use TIFF when: the destination is print, or you are archiving a master that needs to survive colour-managed workflows.

SVG: only if the artwork is genuinely vector

SVG is inherently transparent wherever nothing is drawn, and it scales infinitely without quality loss, which makes it the correct format for logos, icons, and illustrations that were drawn as shapes. It is the wrong format for a photograph, and this confusion is common enough to be worth stating directly: exporting a photo as SVG does not vectorise it. It wraps the same raster pixels inside an SVG container, producing a file that is larger than the PNG it came from and scales exactly as badly.

Use SVG when: the source artwork is vector. If your cutout came out of a background remover, it is not.

A decision shortcut

  • Master file you keep: PNG-24, or TIFF if print is in the picture.
  • Sending to a client, teammate, or marketplace: PNG.
  • Serving on your own website: AVIF with a WebP fallback, generated from the PNG master.
  • Logo or icon drawn as shapes: SVG.
  • Anywhere at all: not JPEG.

Two conversion habits worth adopting

First, convert from the master rather than from a previous conversion. Every lossy step compounds, and a WebP made from an AVIF made from a JPEG carries all three sets of artifacts. Keep the PNG that came out of your background remover and treat every other file as disposable output.

Second, verify alpha survived the conversion rather than assuming it did. Some command-line conversions and a surprising number of online converters silently flatten transparency onto white. Opening the converted file on a coloured background takes two seconds and catches this before it reaches production.

Quick recap

PNG is the format to keep and to send, WebP and AVIF are the formats to serve, TIFF is the format for print, SVG is only for genuine vector artwork, and JPEG is never an option when transparency matters. Holding a single PNG master and generating everything else from it keeps the decision simple and means a format mistake is always recoverable.

Ready to try it yourself?

Remove backgrounds from your images for free - no sign-up needed.

Try nobackground Free

Related posts