CSS Blend Modes in Figma: Opacity, Blend Modes, and Filters Mapped
CSS opacity, mix-blend-mode, filter and backdrop-filter each have a Figma counterpart.
Opacity: layer opacity, fill opacity, and CSS opacity
CSS opacity maps to layer opacity in Figma. A semi-transparent color inside a fill, such as rgb(255 255 255 / 30%), maps to the fill's own opacity. On a flat background the two look alike. Add a blur or a blend mode and they part ways.
Layer opacity fades the whole layer, children included. Fill opacity fades only the paint. In CSS the same split exists: opacity: 0.5 fades the element and everything inside it, while an alpha color fades only that one paint.
CSS adds a side effect. According to MDN's backdrop-filter page, an element with an opacity value below 1 becomes a backdrop root, which limits how far a descendant's backdrop effect can reach. Figma has no such concept on the canvas, so an imported tree can look right in Figma and still behave differently when the CSS is rebuilt.
Opacity also shows up inside gradients, where each stop carries its own alpha. That case is covered in CSS gradients in Figma.
Blend modes, one per layer, fill or effect
CSS has two blend properties, and Figma has three places to set a blend mode.
| CSS property | What it blends | Figma scope |
|---|---|---|
mix-blend-mode | The element with the content behind it | The layer (Appearance section) |
background-blend-mode | An element's own background layers with each other | A fill or stroke (color picker) |
| No CSS property | Shadow or noise against what is below | Drop shadow, inner shadow, noise |
MDN defines mix-blend-mode as how an element's content blends with its backdrop, the content rendered behind it within the same stacking context. To blend an element's own backgrounds with each other, you use background-blend-mode instead.
Figma's help center states that each layer, fill, or effect can only have one blend mode. It also says blend modes can't be applied to fills that use color styles, so apply the mode to the layer or to the style instead. The effects that accept a blend mode are inner shadows, drop shadows, and noise.
Here's where that bites. A CSS element that stacks background-blend-mode: multiply over a gradient and an image has one mode listed per background layer. In Figma, you set the mode on each fill separately.
Blend mode names: the 16 CSS keywords
MDN's <blend-mode> type lists 16 keywords. Figma uses the same names with spaces and capitals.
| CSS keyword | Figma name |
|---|---|
normal | Normal |
multiply | Multiply |
screen | Screen |
overlay | Overlay |
darken | Darken |
lighten | Lighten |
color-dodge | Color dodge |
color-burn | Color burn |
hard-light | Hard light |
soft-light | Soft light |
difference | Difference |
exclusion | Exclusion |
hue | Hue |
saturation | Saturation |
color | Color |
luminosity | Luminosity |
The names line up one to one. Figma's list goes further. It also has Plus darker, Plus lighter, and Pass through. MDN's <blend-mode> type does not document plus-darker or plus-lighter, so there is no documented CSS keyword to map those two to. Treat them as Figma-only unless your browser targets say otherwise.
Two more details help when you compare results. MDN describes overlay as hard-light with the layers swapped, and says exclusion is similar to difference with less contrast. It also notes that changes between blend modes are not interpolated, so a CSS transition between two modes switches immediately.
Pass through and isolation
Pass through is the default blend mode for Figma layers. It has no visible effect by itself. It lets blend modes on child layers, or on the fills and effects of a layer, interact with the content below. Normal is the default for fills and effects, and Figma says Pass through can't be applied to fills or effects.
Setting a parent layer to Normal does the opposite: it stops the children's blend modes from reaching content below the parent.
CSS gets the same result from stacking contexts. mix-blend-mode blends within the same stacking context, and MDN's examples show that wrapping blended elements in a container with isolation: isolate confines the blending to that group. Without isolation, the container's background is part of the backdrop.
.group {
isolation: isolate;
}
.group .badge {
mix-blend-mode: multiply;
}
Treat this as a conceptual match, not an identical algorithm. Figma's Pass through and Normal on a parent and CSS's isolation: isolate both decide how far a blend reaches, but Figma documents the rule in terms of layers and CSS documents it in terms of stacking contexts.
Filters and effects
CSS filter changes the element itself. Figma's closest counterpart is the layer blur. CSS backdrop-filter changes what is behind the element, and Figma's counterpart is the background blur.
| CSS | Figma effect | Limit in Figma |
|---|---|---|
filter: blur(5px) | Layer blur | One layer blur per layer |
backdrop-filter: blur(10px) | Background blur | One background blur per layer |
filter: drop-shadow(...) | Drop shadow | Up to eight per layer |
box-shadow: inset ... | Inner shadow | Up to eight per layer |
Figma's effects documentation lists seven effect types: glass, drop shadow, inner shadow, layer blur, background blur, noise, and texture. A layer can hold one layer blur, one background blur, one glass effect, and one texture effect, plus up to two noise effects.
CSS is looser. The filter property accepts blur(), brightness(), contrast(), drop-shadow(), grayscale(), hue-rotate(), invert(), opacity(), saturate(), and sepia(), applied in the order you declare them, plus url() for an SVG filter. Figma has no named effect for most of those functions. If a page uses grayscale() or sepia() on an image, do not assume an editable Figma equivalent exists; check the import report for what fell back.
The shadow functions differ too. MDN says drop-shadow() follows the contours of the image and, unlike box-shadow, does not allow the inset keyword or a spread value. The property-by-property shadow map is in CSS box-shadow to Figma effect.
Background blur: why it shows nothing
A background blur that does nothing is the most common surprise, and it has two separate causes.
In Figma, the fill opacity has to sit between .10 and 99.99%. The effects documentation is direct about it: if you set a fill opacity to 100%, you won't be able to see the background blur at all. Check fill opacity, not only layer opacity. Figma also says you cannot combine a background blur and a glass effect on the same object.
In CSS, MDN says the element or its background needs to be transparent or partially transparent for the effect to be visible. A translucent background paired with the blur is the usual pattern:
.panel {
background-color: rgb(255 255 255 / 30%);
backdrop-filter: blur(10px);
}
The second CSS cause is the backdrop root. MDN lists the elements that set a boundary for backdrop-filter: the root element, and any element with a filter other than none, an opacity below 1, a mask, mask-image, mask-border or clip-path other than none, a backdrop-filter other than none, or a mix-blend-mode other than normal. MDN gives an example: a parent with opacity: 0.9 becomes a backdrop root, so a child's backdrop-filter only blurs the content between that parent and the child, not the content behind the parent.
MDN marks backdrop-filter as Baseline 2024, working across the latest devices and browsers since September 2024. Older browsers may not support it.
Checking the result
Opacity, blend modes, and blurs can look right in a screenshot and still be wrong in the layer tree. After any import, check three things:
- Blend modes sit on the right scope: layer, fill, or effect.
- A blur sits on the layer you expect, and its fill opacity is below 100%.
- Nothing relies on a CSS filter function that has no named Figma effect.
UnHTML produces editable layers, not a pixel-exact clone, and the import report lists what falls back. Read that report for anything in this article's property families instead of assuming a match. A wider view of what carries over is in what survives an import.
Frequently Asked Questions
Which CSS property matches a Figma layer blend mode?
mix-blend-mode. It blends an element with the content behind it in the same stacking context. A blend mode on a Figma fill matches background-blend-mode, which blends an element's own background layers.
Why does my Figma background blur show nothing?
Fill opacity is probably 100%. Figma needs the fill opacity between .10 and 99.99% for the blur to be visible. CSS backdrop-filter has the same kind of rule: the element or its background must be at least partly transparent.
Does CSS have Plus darker and Plus lighter?
MDN's <blend-mode> type lists 16 keywords and does not document plus-darker or plus-lighter. Figma lists both, so expect no direct keyword match.
Can I stack two layer blurs on one Figma layer?
No. Figma allows one layer blur and one background blur per layer. CSS filter can chain several functions in the order you declare them.
Questions
- Which CSS property matches a Figma layer blend mode?
- `mix-blend-mode`. It blends an element with the content behind it in the same stacking context. A blend mode on a Figma fill matches `background-blend-mode`, which blends an element's own background layers.
- Why does my Figma background blur show nothing?
- Fill opacity is probably 100%. Figma needs the fill opacity between .10 and 99.99% for the blur to be visible. CSS `backdrop-filter` has the same kind of rule: the element or its background must be at least partly transparent.
- Does CSS have Plus darker and Plus lighter?
- MDN's `<blend-mode>` type lists 16 keywords and does not document `plus-darker` or `plus-lighter`. Figma lists both, so expect no direct keyword match.
- Can I stack two layer blurs on one Figma layer?
- No. Figma allows one layer blur and one background blur per layer. CSS `filter` can chain several functions in the order you declare them.