Straight vs Premultiplied Alpha: Why Transparent Video Has Dark Edges

Straight and premultiplied alpha describe different relationships between a pixel's color and transparency. If a transparent video is interpreted using the wrong relationship or matte color, its partially transparent edges can show a dark or colored fringe. Do not assume every black outline is an alpha-mode problem: source contamination, an imperfect cutout, effects, resizing and playback can create similar symptoms. Preserve the master, compare it on light and dark backgrounds, check the importing application's alpha interpretation, and change one setting at a time. Confirm the corrected export and published page separately; a transparent file is not automatically a clean edge or a universally compatible website delivery.

The handoff problem behind the technical terms

A designer exports a cutout that looks convincing over the editor's checkerboard. A developer places it beside a pale headline and notices a black rim around the subject. Repeating the export with another filename may change nothing, because the problem could be in the source colors, how the file is interpreted, or the later website presentation.

The useful question is not simply “Does this video have alpha?” It is “Does the receiving workflow understand this asset's edge colors, and does the final presentation preserve the intended appearance?” Those questions belong at different stages of the handoff and need different checks.

This guide is written by the AlphaPublish Editorial Team. AlphaPublish has a commercial interest in transparent-video website delivery. The explanation is based on official documentation checked on October 10, 2026; it is not a benchmark, a completed real-device test or a claim that we inspected your file. The examples below are illustrative diagnostic situations, not measured before-and-after results.

What straight and premultiplied alpha mean

An alpha channel represents transparency. Partially transparent edge pixels matter because an antialiased outline, soft hair or motion blur is not simply a row of completely opaque pixels beside completely empty ones. Adobe's alpha-channel documentation explains the role of that transparency information. Its presence alone does not establish edge quality.

With straight alpha, the color information is stored independently of transparency. With premultiplied alpha, edge color information is already affected by transparency and the relevant matte treatment. The receiver needs to interpret that representation correctly rather than apply a convenient label regardless of how the file was created.

Adobe's footage-interpretation documentation describes straight and premultiplied alpha and the importance of the matte color when interpreting premultiplied footage. Incorrect interpretation can create unwanted edge coloration. This is a reason to check the handoff, not a rule that straight always looks better or that every premultiplied file is defective.

You do not need to guess from the filename. Ask for the export application's settings, intended alpha treatment and any matte color. If those details are missing, record the uncertainty and make reversible interpretation comparisons on a copy. A single attractive preview over one background is not enough to identify the correct representation.

A black fringe is different from a black rectangle

Before adjusting interpretation, describe the symptom precisely. A narrow dark outline following the subject is different from the entire video's rectangular background appearing black. A file that looks black in a generic player is also different from a file that has no transparency information at all.

The Jitter transparent-export help notes that playback software can display transparent video differently. This supports a limited conclusion: an opaque-looking preview in one player is not sufficient evidence that an export lost its alpha. It does not establish that every player or browser supports the delivered format.

If the question is whether an ordinary export retained transparency, start with our MP4 transparency guide. If the concern is playback support rather than the edge itself, use the compatibility guidance. This article focuses on interpretation and edge handoff, not a universal diagnosis for every black area.

Step 1: Preserve the source and identify the receiving stage

Keep the editor project, the transparent master and the delivered website file separately. Record which application created the master and which application imported it. A “final” file may have passed through another tool that changed its encoding or interpretation; do not assume it is identical to the designer's export.

Choose representative frames before making changes. Include a stable outline, a soft or translucent detail and a moment with movement if the asset contains one. Use the same frames throughout the investigation. Comparing a static frame from one version with a blurred frame from another can create a misleading improvement.

Next, identify the first stage that shows the unwanted edge. Is it already visible in the original composition? Does it appear only after export and reimport? Does it appear after delivery preparation? Or does it appear only on the published page? That sequence helps assign the issue to the source creator, receiving editor or website owner.

Do not replace the public asset while you are still experimenting. Keep a private test or local preview with clear version labels. A reversible diagnosis makes it easier to find the actual cause and avoids changing a working production handoff into a series of untracked exports.

Step 2: Compare light, dark and intended backgrounds

Review the same frames over a plain light background, a plain dark background and the real page background. Checkerboard is a useful editing aid, but its alternating squares can distract from a narrow rim. A result that looks acceptable over charcoal may reveal contamination beside a white section.

Inspect at the intended displayed size and at a larger size for diagnosis. The enlarged view helps locate the defect; the intended size determines whether it is distracting in the actual composition. Do not judge a website asset only at extreme magnification, and do not hide an obvious issue by testing it only as a tiny thumbnail.

Keep the background, display dimensions and viewing stage unchanged when comparing versions. If the frame becomes cleaner after changing both the alpha setting and the scale, the comparison does not tell you which change mattered. Use a short comparison note rather than relying on memory.

Also examine movement. A fringe might be inconspicuous in one still but obvious around a moving arm or soft blur. Conversely, a softened edge can be intentional. The goal is to preserve the subject's intended detail, not to make every outline unnaturally hard because it is easier to inspect.

Step 3: Check interpretation instead of guessing a favorite mode

In an importing application that exposes alpha interpretation, confirm the currently selected setting and the source export information. In After Effects, the official footage-interpretation reference is the appropriate place to check the relevant controls for your version. This guide does not certify a particular installed release or prescribe identical menus across editing applications.

If the source was exported with premultiplied treatment, identify the relevant matte color instead of selecting black automatically. If the source was created as straight, do not apply a premultiplied interpretation merely because a tutorial recommends it. The choice must match the asset and receiving workflow.

When the handoff information is uncertain, compare candidate interpretations reversibly while retaining the master. Look at the whole subject over the controlled backgrounds. A change that hides a dark rim but creates an excessive bright edge elsewhere is not a clean resolution.

Stop changing interpretation if the defect is already baked into opaque source pixels or the alpha shape itself. Interpretation is not a substitute for correcting a poor segmentation, a colored background reflected into the subject, or an effect that intentionally adds an outline. Those problems may need a source edit, another export or a different visual treatment.

Step 4: Separate color contamination from the cutout shape

Ask whether the wanted boundary exists in the source. If part of the subject was removed, switching alpha modes cannot be assumed to reconstruct it. If unwanted background remains opaque, interpretation alone does not turn it into a properly shaped matte. If a shadow was part of the original design, removing it may damage the intended composition.

Where the shape is acceptable but its edge colors look wrong, investigate the export and interpretation handoff. Where the shape itself is wrong, return to the source cutout. This distinction keeps a website developer from applying presentation tricks to a problem that belongs in the design file.

Avoid using CSS blend modes as a universal substitute for transparency repair. A treatment that hides black against one background can alter subject colors or fail on another section. If you deliberately choose such a treatment, document it as a design decision and test that exact presentation; do not describe it as proof that the alpha asset is correct.

Do not repeatedly encode the same damaged deliverable while hoping the outline disappears. Ask for the least-processed suitable master and the known export settings. Keep only the changes that improve the controlled comparison without sacrificing required detail or creating a new dependency on one background color.

Step 5: Recheck the delivery file and published page separately

Once the master is interpretable and its edges meet the design requirement, create the intended delivery and reopen it through the receiving workflow. A corrected editor preview is not the final file. Record the actual output, not only the export preset's name.

Our transparent WebM guide covers that delivery format, while the ProRes 4444 guide explains a different master and handoff context. Neither extension by itself proves the file's interpretation or makes it suitable for every browser. Preserve the distinction between master, delivery and player.

On the page, check the actual asset URL, presentation size, backgrounds, poster and playing state. If only the page introduces the defect, review its styling and the delivered version before modifying the master again. Confirm that the page is not still displaying an earlier asset or a mismatched poster.

Build an acceptance list for the browsers and devices that matter to your audience. Record the versions and date when those tests are actually performed. This article provides a method; it does not supply completed Safari, iPhone or Android results, and it does not promise that one setting is compatible forever.

A compact source-to-website handoff note

Give the receiving person enough information to repeat the accepted result:

• Source application and relevant version, plus the editable project's location.
• Master filename, dimensions and export settings.
• Intended alpha treatment and matte color, if applicable and known.
• Approved light, dark and actual-background reference frames.
• Delivery file and poster versions, with the intended display size.
• Which page and playback paths were checked, and which remain unverified.
• The person responsible for correcting the source versus replacing the published delivery.

Do not fill unknown fields with a confident guess. “Exporter did not supply alpha interpretation” is more useful than an incorrect instruction that every future editor follows. Keep the note alongside the assets, so replacement work does not depend on reconstructing a chat conversation.

Where AlphaPublish fits—and where it does not

AlphaPublish's current public workflow includes transparent-video creation and importing an existing alpha master, followed by website-delivery review. That does not mean arbitrary files are supported, every edge is automatically repaired, or an import check establishes visual quality on your website. Review the current tool's accepted inputs and inspect the actual result.

Use AlphaPublish for the website-delivery job that its current public workflow describes, after the source and interpretation are suitable. If the master needs a cutout repair or a project-level interpretation adjustment, an appropriate editing or compositing application is the better starting point. We do not rank those tools by unmeasured quality or claim that hosting repairs missing detail.

For publishing and replacement responsibilities, see the transparent-video hosting guide. Treat the source edge, delivered format, player behavior and public-page presentation as separate acceptance checks. A stable embed can simplify maintenance, but it is not a certificate that all four layers are correct.

Frequently asked questions

Is straight alpha always better than premultiplied alpha?

No. The receiving workflow needs to interpret the representation it actually receives. Selecting a preferred label regardless of the source can create another mismatch. Preserve the export information and compare the result over more than one background.

Does a black outline mean the file has no alpha?

No. A narrow fringe can occur around partially transparent pixels even when transparency exists. A fully opaque rectangle raises a different investigation involving the file and display path. Describe the symptom before choosing a remedy.

Will changing the matte color fix every halo?

No. It may be relevant to interpreting an appropriate premultiplied source, but source contamination, segmentation mistakes and added effects are different problems. Do not keep adjusting a matte setting when the wanted boundary is missing from the source.

Can a website player fix the original cutout?

Do not assume so. Playback and compositing should display the intended asset, not reconstruct source detail. Correct the source or interpretation where the defect first appears, then validate the delivered asset and final page independently.

What should I ask a designer before publishing?

Ask for the suitable master, export settings, known alpha treatment and approved light/dark reference frames. Agree on the intended display size and who owns revisions. If a field is unknown, flag it explicitly instead of inventing a format or compatibility guarantee.

The practical rule

Match interpretation to the asset, diagnose the first failing stage, and keep comparisons reversible. Clean-looking alpha in an editor, clean edges in a delivered file, and correct website playback are related goals—but they are not interchangeable evidence. Confirm each one before replacing the public asset.