Frame

Frames can define dimensions, clipping, constraints, grids, auto layout and prototype behavior. They are commonly used to represent screens and reusable interface regions. In practical terms, Frame belongs to the structure and interaction layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Frame as if it also meant Auto Layout. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Use frames when you need layout behavior or a defined coordinate space rather than grouping objects only for selection.

In day-to-day work, Frame matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

A Figma frame can represent a screen or component boundary and can contain constraints, grids, clipping and Auto Layout. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.