Why Your Transparent WebM Still Shows a Background

If you downloaded a transparent WebM and it still shows the original scene, black, or a flat colour when you open it, the transparency has probably not been lost. Most local players and many browser tabs do not composite the alpha channel of a VP9 WebM — they decode the colour and ignore the transparency, so you see whatever the encoder left in those pixels. The alpha data is still in the file.

The fastest way to know for certain is to put the file on top of something.

Alpha channel, codec, container

Three separate things get blamed for each other, so it is worth naming them.

The alpha channel is a fourth value per pixel, alongside red, green and blue, saying how opaque that pixel is. It is data inside the video stream.

The codec is what encodes those pixels. VP9 can carry alpha. H.264, the codec almost every MP4 uses, cannot — there is nowhere in the format to put it.

The container is the file wrapper: .webm, .mp4, .mov. It holds streams; it does not decide what those streams can contain.

This is why renaming a file does nothing. Changing clip.webm to clip.mp4 tells the operating system to expect a different wrapper around exactly the same VP9 stream. Nothing re-encodes, no transparency is added or removed, and most software will either refuse the file or ignore the extension entirely.

Check it in ninety seconds

In an editor. Drop a solid colour, image or clip on a lower layer, then put the WebM on the layer above. If your lower layer appears around the subject, the alpha is working. Pick a colour nothing in the clip contains — magenta is the traditional choice — so a wrong result is obvious rather than plausible.

In a browser. Put the file in a page with a coloured element behind it:

<div style="background: magenta">
  <video src="clip.webm" autoplay loop muted playsinline></video>
</div>

Magenta around the subject means the transparency is intact. A rectangle of original background means that browser is not compositing alpha, which is a fact about the browser.

What does not test anything. Double-clicking the file and looking at whatever player opens. That tells you what that player does with alpha, which may be nothing.

If the alpha really is gone

It is worth knowing what that looks like, so you can tell the two apart. A file that genuinely lost its transparency has a hard rectangular edge of flat colour filling the frame, identical in every tool you open it in, including the browser test above. A compositing gap looks different in different places — transparent in one editor, black in a player, checkerboarded in a third.

The usual cause of genuine loss is a re-encode somewhere in the chain. Passing a transparent WebM through a tool that outputs H.264 flattens it, and most tools do that silently because from their point of view nothing went wrong.

Why the file is WebM in the first place

The reason this question exists at all is that the format that carries transparency is not the format most people share. BGRemove exports VP9 in a WebM container because that is a widely supported combination that can actually hold an alpha channel. An MP4 could not: there is no standard place in H.264 for a fourth channel, so any tool handing you a transparent MP4 has either used an unusual codec or has flattened your subject onto a colour and called it transparent.

That trade is deliberate. A flattened export is smaller and opens anywhere, and it is also finished — you cannot change your mind about the background later. The transparent file is bigger and fussier to preview, and it is the one you can still do something with.

A soft edge is not a broken edge

While you are looking closely, one thing worth not misreading: a semi-transparent fringe around hair or motion blur is correct, not damage. Those pixels were genuinely part subject and part room in the recording, and the alpha channel stores that as a value between fully opaque and fully clear.

You will see it as a faint halo when the file sits over a background very different in brightness from the original — a subject filmed against a dark room and placed on white, for example. That is the original scene showing through the partly transparent pixels, doing exactly what they encode. If it bothers you in a particular composite, choosing a background closer in tone to the one you filmed against usually settles it.

About specific editors

Whether CapCut or Premiere Pro imports VP9 alpha correctly depends on the version, the platform and which codecs that build ships with, and those change between releases. We are not in a position to promise how third-party software behaves this month, so check the current documentation for the tool you use before you plan a workflow around it.

If your editor does not accept WebM alpha, you do not have to convert anything by hand. Open the finished clip in Change Background, put a colour, blur, image or video behind it, and export an MP4 — that composite is flat by definition, so every editor takes it. Keep the transparent WebM as well if the background is not settled yet.

The short version

Seeing a background does not mean the transparency failed. Test the file over a colour before you conclude anything, and remember that the extension is a label, not a conversion.

Add a background and export MP4 · Remove a video background · How BGRemove works