CSS Overflow in Figma: Clip Content, Scrolling, and What Maps Where
CSS overflow in Figma explained: how hidden, clip, scroll and auto compare with Clip content and the Overflow dropdown, plus what to check after an import.
Introduction
CSS overflow has no single twin in Figma. Figma splits the job in two: Clip content hides what sticks out of a frame, and the Overflow dropdown in the Prototype tab decides whether a prototype can scroll. The closest CSS match for a clipped frame is overflow: clip or overflow: hidden, and the scroll part has no live counterpart in the Design tab.
Below: the five CSS values, the two Figma controls, and a mapping table. The mapping is our reading of both docs, not an equivalence Figma publishes. A short checklist for pages you bring into Figma from the web closes it out.
The CSS side: overflow keywords and scroll containers
The overflow property sets what happens to content that is larger than its box. According to MDN's overflow reference, there are five values worth knowing:
| Value | Clipped? | Scroll container? | Scroll bars |
|---|---|---|---|
visible | No | No | None |
hidden | Yes, at the padding box | Yes, when overflowing | None |
clip | Yes, at the overflow clip edge | No | None |
scroll | Yes, at the padding box | Always | Always shown |
auto | Yes, at the padding box | When overflowing | Only when overflowing |
visible is the default. Content spills outside the box and the box is not a scroll container.
A scroll container is simply a box the browser can scroll, and that changes what script and keyboard focus can do. visible and clip never create one. hidden and auto create one only when content overflows, and scroll always does. MDN also notes that every value except visible and clip creates a new block formatting context.
overlay is a non-standard legacy alias for auto. MDN discourages it in new code.
hidden vs clip: why the difference matters
Both hidden and clip cut off overflow and draw no scroll bars. The difference is whether the box can still scroll.
With hidden, the box is a scroll container, so scripts can still move it with scrollLeft or scrollTo(). Tabbing to a focusable element inside the clipped area can also scroll it into view. With clip, programmatic scrolling is not supported at all. MDN's guide to overflowing content advises using clip most of the time and hidden only when you need that scrollable behavior.
That advice comes with a caveat. MDN warns that with clip, a hidden focusable element can receive focus but will not scroll into view, which makes it unreachable for keyboard users. Use clip only when no interactive content can end up in the clipped area.
Two axes, one rule
You can set the axes separately with overflow-x and overflow-y, or with two keywords in overflow. The first value is x, the second is y. One rule trips people up: if one axis is auto, scroll or hidden and the other is visible, the visible axis computes to auto. So overflow: hidden visible behaves as overflow: hidden auto. Only clip can sit next to visible without being changed, so overflow: clip visible clips horizontally and lets content spill vertically.
Moving the clip edge
overflow-clip-margin shifts the clip edge outward for overflow: clip. It defaults to 0px. With overflow-clip-margin: 1em, content may extend 1em past the padding box before it is cut off.
The Figma side: Clip content and the Overflow dropdown
Figma lists Clip content among frame properties. In Figma's Frames article it is defined as hiding any objects in the frame that extend beyond the frame's bounds. You turn it on by selecting the frame, opening the Design tab, and checking Clip content in the Layout section.
Scrolling is a separate control. Per Figma's page on prototype scroll and overflow behavior, Overflow applies only to frames, including nested frames. You set it in the Prototype tab, in the Scroll behavior section. The dropdown has four options:
- No scrolling: content beyond the frame is not viewable.
- Horizontal: users scroll left and right.
- Vertical: users scroll up and down.
- Both directions: users move in any direction.
Scrolling only works when content extends past the frame. Otherwise Figma shows this error: "For scrolling to work on this frame, the content needs to be bigger than the frame."
Figma's Frames article does not describe how Clip content behaves on an auto layout frame or compare frames with groups. We do not state a rule for either here. Check it on your own file.
A mapping, labeled as inference
This table is our reading of the MDN and Figma pages above. Figma does not publish a CSS overflow equivalence, and the Design tab does not expose a scroll container or scroll bar visibility.
| CSS | Closest Figma setting | What has no counterpart |
|---|---|---|
overflow: visible | Clip content off | Nothing lost |
overflow: clip | Clip content on, Overflow set to No scrolling | The clip margin from overflow-clip-margin |
overflow: hidden | Clip content on | Script scrolling and focus scrolling |
overflow: auto | Clip content on, Overflow set to Vertical, Horizontal or Both directions | Scroll bars shown only when overflowing |
overflow: scroll | Clip content on, Overflow set to a scroll direction | Scroll bars that are always visible |
overflow-x and overflow-y | Horizontal or Vertical in the Overflow dropdown | Mixed clip and scroll per axis |
Two cautions. First, Figma's Overflow dropdown belongs to prototyping, so it describes how a prototype behaves, not how the frame is drawn on the canvas. Second, the help pages do not say whether Figma's scrolling matches auto or scroll for scroll bar visibility. Treat that row as unconfirmed.
Fixed and sticky layers
Inside a frame that scrolls, each layer has one Scroll position: Scroll with parent, Fixed, or Sticky. Fixed layers stay put while the rest scrolls, like a status bar or a bottom menu. In auto layout frames, a layer can only be Fixed if it has absolute positioning.
Sticky works only in frames with vertical scrolling. The layer scrolls normally, then fixes when its top edge reaches the top of its parent frame. A sticky layer nested inside another layer stays within that direct parent's bounds. These options sit close to CSS position: fixed and position: sticky, which is covered in CSS position in Figma.
What to check after an import
As of 2026, treat overflow on an imported web page as something to verify, not assume. Pages from UnHTML or any other importer land as frames, and this list applies to all of them:
- Cut-off content. Select the frame and look at Clip content in the Layout section. If content is missing, it may be clipped by design, or it may sit outside a parent frame that clips.
- Scrolling. A box that scrolled in the browser will not scroll in a prototype until you set Overflow on its frame. Pick the direction yourself.
- Content size. If you see the "content needs to be bigger than the frame" error, the layers inside do not extend past the frame edge.
- Fixed headers. Check whether a header that was
position: fixedorstickyneeds a Scroll position set. - Layout fallbacks. Read the import report for layers that fell back to absolute positioning. Our flexbox to auto layout map explains when that happens, and what survives an import covers borders and radii that interact with clipping.
Conclusion
Figma gives you two switches where CSS has one property. Clip content hides what overflows a frame. The Overflow dropdown makes a prototype scroll. overflow: clip and hidden both map to the first switch, auto and scroll also need the second, and some CSS details, such as scroll bars and script scrolling, have no equivalent. Set both switches on purpose and test the result.
Frequently Asked Questions
Does overflow: hidden become Clip content in Figma?
Clip content is the closest Figma setting, since it hides anything beyond the frame's bounds. Figma has no scroll container concept in the Design tab, so the "can still scroll programmatically" part of hidden has no equivalent.
What is the difference between overflow: hidden and overflow: clip?
Both cut off overflowing content and show no scroll bars. hidden makes the box a scroll container, so it can still be scrolled by script or by focusing a hidden element. clip does not, and forbids programmatic scrolling.
Why does Figma say the content needs to be bigger than the frame?
Figma's Overflow scrolling only works when content extends past the frame's bounds. If it does not, the Prototype tab shows an error saying the content needs to be bigger than the frame.
Will a scrollable CSS box scroll inside the Figma file?
Not by default. Clip content hides the overflow, and scrolling is a separate prototype setting you choose per frame. Check the import report and set the Overflow dropdown yourself where you want a prototype to scroll.
Questions
- Does overflow: hidden become Clip content in Figma?
- Clip content is the closest Figma setting, since it hides anything beyond the frame's bounds. Figma has no scroll container concept in the Design tab, so the "can still scroll programmatically" part of `hidden` has no equivalent.
- What is the difference between overflow: hidden and overflow: clip?
- Both cut off overflowing content and show no scroll bars. `hidden` makes the box a scroll container, so it can still be scrolled by script or by focusing a hidden element. `clip` does not, and forbids programmatic scrolling.
- Why does Figma say the content needs to be bigger than the frame?
- Figma's Overflow scrolling only works when content extends past the frame's bounds. If it does not, the Prototype tab shows an error saying the content needs to be bigger than the frame.
- Will a scrollable CSS box scroll inside the Figma file?
- Not by default. Clip content hides the overflow, and scrolling is a separate prototype setting you choose per frame. Check the import report and set the Overflow dropdown yourself where you want a prototype to scroll.