Media Queries and Responsive Pages: What a Single Import Captures
A single responsive design Figma import captures one viewport width. See how width media queries are decided and why you import once per breakpoint.
Introduction
A responsive design Figma import captures your page at one viewport width, not at every breakpoint. If you want the 390px layout and the 1440px layout, you import twice. The reason sits in how CSS works: a width media query is either true or false at a given width, so one render shows one set of rules.
Plenty of designers expect "the responsive version" to arrive as a single frame. It won't. This article covers how a width query is decided, which width the importer takes, why you import once per breakpoint, and what Figma offers afterward. One caveat up front: UnHTML's public page does not describe how it handles media queries or breakpoints. So this article treats the chosen width as the input and explains what a width query does at that width. It does not claim anything the product page does not say.
How a width media query is decided
The query is true or false at one width
A width media query applies its styles only while the viewport matches the condition. MDN's example says @media (max-width: 1250px) applies styles only if the browser's viewport width is equal to or narrower than 1250px. At 1251px the same rule is false and its styles do not apply. No in-between state exists.
According to MDN's guide to using media queries, a query is true when the media type matches and every media feature expression is true. A comma separated list works as OR, and combines conditions, and not negates a query.
Range syntax and boundaries
Modern CSS lets you write the same condition in range form. These three are equivalent:
@media (max-width: 1250px) { /* ... */ }
@media (width <= 1250px) { /* ... */ }
@media (1250px >= width) { /* ... */ }
The <= and >= operators are inclusive. The < and > operators exclude the boundary value, so (width < 1250px) is false at exactly 1250px. A band is written either as (min-width: 30em) and (max-width: 50em) or as (30em <= width <= 50em).
Why that matters for an import
An import renders the page once. At that render the viewport has one width, and each width query is either true or false. The result is one set of matching rules: one stacking order, one set of hidden elements, one set of font sizes. The rules for other widths are still in the stylesheet, but they do not apply to that render.
Pick the width before you import
The first decision is the width. UnHTML offers a choice in its workflow: "Choose Desktop 1440, Mobile 390, or type a custom width." The pricing section lists "Desktop, Mobile & custom viewports" under Pro. As of November 2026, the Free tier feature list on that page does not mention viewports, so check the pricing page for what your tier includes.
The page says layout is mapped "from the page's own CSS" and from real flex and grid. Combined with how width queries work, the practical rule is simple: the width you choose decides which of your breakpoint rules are true during the import.
Three habits help:
- Pick a width inside the band you want, not on its edge. If your stylesheet switches layout at 768px, importing at exactly 768px can land on either side, depending on whether the rule is
max-width: 768pxorwidth < 768px. - For a named breakpoint, open the stylesheet first and read the exact value and the operator.
- Use the presets (1440 and 390) when you want the common desktop and phone starting points, and a custom width for a tablet or a breakpoint of your own.
Import once per breakpoint
Treat each width as its own import. Name the resulting frames by width, for example "Home 1440" and "Home 390", so nobody mistakes one for the other.
What differs between runs is whatever your width queries change: a sidebar that stacks under the content, a navigation that collapses, a hero that shrinks its type. MDN documents that width queries change which rules apply. Whether a given element looks different at your two widths depends on your stylesheet. Compare the frames; don't assume.
Each import also produces its own report. The product page describes it as covering "What was substituted, which frames reverted to absolute, which images were skipped," and says it is laid out after every run. Read it per width. A grid that maps cleanly at 1440 may fall back to absolute positioning at 390, and the report is where that shows up. The page also states a cap of "500 layers per import", so each width gets its own budget rather than sharing one.
If your page uses a framework with named breakpoints, the same logic applies. The article on importing a Bootstrap page covers what to check when the grid classes change at set widths.
What the product page does not state is whether one import yields a single top level frame or how any rule outside the chosen width is treated. Verify that on your own page: import once, open the layers panel, and see what you got.
What Figma gives you instead of media queries
Figma has no stylesheet to evaluate. After the import, responsive behavior is something you build. The main tool is constraints.
According to Figma's help article on constraints, constraints control how a layer responds when its parent frame is resized, set on each axis. Horizontal options are Left, Right, Left and right, Center and Scale. Vertical options are Top, Bottom, Top and bottom, Center and Scale. Scale keeps a layer's size and position as a percentage of the frame: a 70px layer in a 100px frame becomes 140px when the frame is 200px wide.
There are limits. Constraints cannot be applied to layers outside frames, to groups, or to layers in an auto layout frame. Figma's article does not mention CSS media queries, and it does not describe constraints as a replacement for them. A constraint resizes a layer smoothly. A media query swaps a whole set of rules at a threshold. Different mechanisms.
For a path that stays inside Figma, see making an imported page responsive with Figma variables.
Conclusion
A single import is a snapshot at one width. Plan one import per breakpoint you care about, pick widths inside each band rather than on an edge, and read the import report for each one. Then use constraints, auto layout and variables in Figma to decide how the layouts behave between those widths.
Frequently Asked Questions
Does one import include every breakpoint of a responsive page?
Not as separate layouts. A width media query is true only while the viewport matches it, so a page rendered at one width shows one set of rules. Import once per width you need. UnHTML's public page lists Desktop 1440, Mobile 390 and custom viewports, and does not describe a combined multi-breakpoint result.
Which width should I import first?
Start with the width your design review begins from. Desktop 1440 and Mobile 390 are the two presets UnHTML lists. A custom width fits a breakpoint of your own, such as the value in a min-width rule.
What happens at the exact breakpoint value?
It depends on how the rule is written. MDN notes that max-width: 768px and width <= 768px are inclusive, while width < 768px excludes the boundary. Importing at exactly 768px can therefore land on either side, so check which operator your stylesheet uses.
Do Figma constraints replace media queries?
No. Figma constraints control how a layer responds when its parent frame resizes. They do not apply to layers inside an auto layout frame, and Figma's help article does not mention CSS media queries.
Questions
- Does one import include every breakpoint of a responsive page?
- Not as separate layouts. A width media query is true only while the viewport matches it, so a page rendered at one width shows one set of rules. Import once per width you need. UnHTML's public page lists Desktop 1440, Mobile 390 and custom viewports, and does not describe a combined multi-breakpoint result.
- Which width should I import first?
- Start with the width your design review begins from. Desktop 1440 and Mobile 390 are the two presets UnHTML lists. A custom width fits a breakpoint of your own, such as the value in a `min-width` rule.
- What happens at the exact breakpoint value?
- It depends on how the rule is written. MDN notes that `max-width: 768px` and `width <= 768px` are inclusive, while `width < 768px` excludes the boundary. Importing at exactly 768px can therefore land on either side, so check which operator your stylesheet uses.
- Do Figma constraints replace media queries?
- No. Figma constraints control how a layer responds when its parent frame resizes. They do not apply to layers inside an auto layout frame, and Figma's help article does not mention CSS media queries.