CSS Masks and clip-path in Figma: Support and Fallbacks on Import

How CSS clip-path and mask map to Figma's vector, alpha and luminance masks, where browser support stands in 2026, and which fallbacks still matter.

REFERENCEDESIGNERPublished

A clip-path in CSS is a hard-edged cut, and a CSS mask is an alpha or luminance filter. In Figma, the closest match to a clip-path is a vector mask, and the closest match to a mask is an alpha or luminance mask. Browser support is no longer the hard part: both properties are Baseline widely available. The part that still needs your eyes is scope and stacking order after a page lands in Figma.

Below, the two CSS properties sit beside Figma's three mask types. You also get current browser support as of 2026-11-15 and the fallbacks that still earn their place. UnHTML aims for faithful, editable layers, not a pixel-exact clone, and its import report lists what fell back. This article makes no claim about how UnHTML converts any specific mask. Treat the mapping below as a reading aid built from the CSS and Figma docs.

clip-path and mask in the CSS

clip-path: a hard-edged region

MDN describes clip-path as creating a clipping region that sets what part of an element is shown. Parts inside the region are shown and parts outside are hidden. The edge has no partial transparency.

The region comes from one of three kinds of value:

  • A url() that points at an SVG <clipPath> element.
  • A basic shape: inset(), circle(), ellipse(), polygon(), path(), rect(), shape() or xywh().
  • A geometry box such as padding-box or content-box, alone or paired with a shape.

If you set no geometry box, the border-box is the reference box, and percentages refer to that reference box. Two details matter when you read an imported page. A path() does not scale with its element, while shape() accepts percentages and custom properties, which MDN calls more robust. And any value other than none creates a new stacking context, the same way opacity below 1 does.

mask: alpha or luminance of an image

The mask shorthand hides an element, fully or partly, using a mask layer. It is shorthand for the mask-* properties. A layer can be a url(), a gradient, or another image source, and omitted parts reset to initial values: mask-mode: match-source, mask-size: auto, mask-repeat: repeat, mask-clip: border-box and mask-composite: add.

mask-mode takes alpha, luminance or match-source. In alpha masking, opaque areas of the mask reveal the element and transparent areas hide it. In luminance masking, light opaque areas reveal it, and dark or transparent areas hide it. mask-composite decides how several layers combine: add, subtract, intersect or exclude.

When the mask source is an SVG file, the shape inside it is real vector data. How SVG on a page becomes native Figma vectors covers that side.

How masks and clips line up with Figma

Figma's three mask types

Figma's masks article lists three types. Any layer can act as the mask. You place it behind the layers it masks, then choose More options > Use as mask.

  • Alpha is the default. The mask is applied based on its opacity, so blurs, shadows and semi-transparent strokes change the result.
  • Vector ignores transparency. Figma treats the mask as fully opaque, and if any area has opacity above zero percent, its outlines become the mask.
  • Luminance uses brightness. The brighter the area, the more is revealed, and a black #000000 mask reveals nothing.

A property-to-mask table

CSSClosest Figma maskWhat to check
clip-path with a basic shape or url()VectorOutline only, so edges are hard in both
mask-mode: alphaAlphaGradient or image transparency drives the reveal
mask-mode: luminanceLuminanceDark areas hide, light areas reveal
mask-composite with several layersNo single setting in the docsRebuild by hand if layers combine

The last row is the honest gap. Neither source describes a Figma setting for subtract, intersect or exclude, so a stacked mask on the live page can need manual work.

Scope rules to check

A Figma mask works on the siblings above it. It stops at another mask, at the mask's parent frame or group, and at a frame or component with Clip content turned on. A mask is a sibling of what it masks, not a parent, so moving or resizing one does not move the other. If an imported mask seems to miss a layer, check order and nesting first. CSS overflow and Figma's Clip content explains the other clipping mechanism that can interfere.

Browser support today

As of 2026-11-15, MDN marks clip-path as Baseline widely available, in every major browser since January 2020. It marks the unprefixed mask shorthand as widely available since December 2023, with a note that some parts may vary.

Can I use's CSS masks table puts global support at about 97.4 percent: 94.42 percent full plus 2.98 percent partial. Chrome and Edge are fully supported from version 120, Safari from 15.4 and Firefox from 53. Earlier versions are marked partial, and the page does not say what is missing in each case. Opera Mini has no support in any version.

For a design import, that means the page you captured almost certainly drew its masks as intended in the browser you captured from. Good support is a reason to trust the capture. It is not a reason to skip the check afterward.

Fallbacks that still matter

  • Newer clip-path values. shape() and xywh() are newer functions. Check the MDN compatibility table for them before you depend on them. Wrapping them in an @supports rule is common practice, though neither source above prescribes it.
  • Make the unclipped version readable. A clip only hides. If the clip is dropped, the text and image should still make sense.
  • Watch the stacking context. Because a non-none clip-path creates one, a clipped element can change which layer sits on top. Stacking contexts and Figma layer order walks through that mapping.
  • Prefer shape() for resizing elements. A path() keeps its fixed coordinates when the element changes size.

A worked reading example

Say a hero image uses clip-path: polygon(50% 0%, 100% 50%, 50% 100%, 0% 50%). That is a diamond. Nothing partial happens at the edge: pixels are either inside the diamond or gone. In Figma terms, you expect a vector shape sitting below the image in the same group, set to Use as mask, with the type left as vector or alpha. Both give a hard edge when the shape is a solid fill.

Now say a card uses mask-image: linear-gradient(black, transparent) to fade its bottom edge. The edge is soft, so a vector mask would be wrong: it would treat any nonzero opacity as fully opaque. The alpha type is the one that keeps the fade, because the reveal follows opacity. If the gradient ran from white to black instead and the CSS set mask-mode: luminance, the luminance type would be the match.

Two checks settle most doubts. First, does the edge look hard or soft on the live page? Hard points to a vector mask, soft points to alpha or luminance. Second, is the mask above or below the layers it should affect in the layer list? Because a Figma mask only reaches the siblings above it, a mask sitting in the wrong place can look like it did nothing.

Checking the imported result in Figma

Turn on View > Mask outlines and Figma outlines every mask in green. Check each mask's type against what the CSS intended. Then compare the frame with the live page at the same width.

Masking in Figma is non-destructive: no portion of the masked layers is modified or deleted, and removing a mask makes hidden areas reappear. So a wrong mask is cheap to fix. Expect some masks, especially stacked mask-composite layers, to need a manual rebuild. If you are importing a page for the first time, UnHTML lists those fallbacks in its import report so you know where to look.

Conclusion

Treat clip-path as a vector mask and mask as an alpha or luminance mask, and verify the scope and order of each one in Figma. Support in browsers is settled for both properties, so the checks that pay off are mask type, sibling order and stacking.

Questions

Is clip-path safe to use without a fallback?
For the common shapes, yes. MDN lists clip-path as Baseline widely available, in every major browser since January 2020. Check the MDN compatibility table for newer values such as shape() and xywh() before relying on them.
Does the unprefixed CSS mask property work in current browsers?
Yes. MDN marks mask as Baseline widely available since December 2023, and Can I use shows full support from Chrome and Edge 120, Safari 15.4 and Firefox 53, with earlier versions partial.
Which Figma mask type matches CSS clip-path?
Figma's vector mask is the closest: it ignores transparency and uses the shape outline, which is what a hard clip does. Alpha and luminance masks correspond to mask-mode alpha and luminance.
What should I check in Figma after importing a page that uses masks?
Turn on View > Mask outlines to see the boundaries, confirm the mask type matches the intent, and check the layer order, since a Figma mask only affects the siblings above it.