Importing a Bootstrap Page Into Figma: Grid, Breakpoints, and What to Check

Figma has no HTML file import. Capture a Bootstrap 5.3 page at one breakpoint, then check the grid, fonts and report. Two routes, step by step.

TUTORIALDEVELOPERPublished

You cannot open a Bootstrap HTML file in Figma the way you open a .fig file. Figma's imports guide lists images, vectors, videos, GIFs, .fig files and .sketch files, and it does not mention HTML. To get a Bootstrap page in as editable layers, you capture the rendered page, either with Figma's Chrome extension or with a plugin that reads a saved HTML file.

You'll need a Bootstrap 5.3 page you can open locally, Figma Design, and Chrome. Below: what the grid means for a capture, both capture routes, how to read the report, and what to clean up afterward. The result is a set of faithful, editable layers, not a pixel-exact clone. Some frames won't map cleanly. Plan to check them.

Know what you are capturing

A capture is a snapshot of one rendered layout. Bootstrap's layout shifts with the viewport, so your first decision is the width.

The grid is flexbox with six breakpoints

According to the Bootstrap 5.3 grid documentation, the grid is mobile-first and built on flexbox. It has 12 columns, six responsive tiers and a default gutter of 1.5rem, which is .75rem of padding on the left and right of each column. Rows wrap the columns and offset that padding with negative margins. Column widths are set in percentages.

Container widths decide your frame width

Bootstrap breakpoints are min-width media queries. A class such as .col-md-4 applies at md and every larger tier. That means a capture shows exactly one tier's layout: the one active at the viewport width you used. Here are the values from the docs:

TierMin viewport width.container max-width
xsunder 576pxauto
sm576px540px
md768px720px
lg992px960px
xl1200px1140px
xxl1400px1320px

Pick the tier you want to design for and set the browser window to a width inside it. For a desktop layout, 1200px or wider gives you the xl container at 1140px. If you need the mobile layout too, repeat the capture at a width under 576px and keep it as a separate frame.

Step 1, save the page as one file

If you take the plugin route in Option 2, you need the page as a single file. Here is the sequence:

  1. Open the Bootstrap page in Chrome at the width you chose above.
  2. Scroll the whole page once so lazy-loaded images and sections render.
  3. Save it as a single self-contained file. The walkthrough to export self-contained HTML from Chrome covers the exact steps.
  4. Open the saved file in a fresh tab and check that fonts, images and the Bootstrap CSS all load without the network.

If the saved copy looks different from the live page, the capture will look different too. Fix that before you go further.

Option 1, Figma's own capture

Figma's help page on turning webpages into editable design layers describes the Chrome extension route. The steps are short:

  1. Open the live or local page in Chrome.
  2. Scroll to the bottom of the page first. Figma says to do this before capturing, so scroll-triggered content is loaded.
  3. Capture the full page or a single element. Privileged pages such as chrome:// cannot be captured.
  4. Switch to Figma Design and paste. The most recent capture is on your clipboard.

According to the same page, frames come across with fills, stroke colors and weights, corner radius, padding, gap and layer opacity. Text keeps its color, font family, font size, font weight, line height and letter spacing. Figma also tries to bind existing color, number and string variables by matching the CSS variable name to each variable's code syntax. Color variables with opacity are not bound.

Check the stated limits before you rely on it. Captures arrive as plain Figma layers. They are not mapped to library components or styles, which Figma lists as roadmap work. Heavy JavaScript animation, <canvas> rendering and virtualized lists can capture imperfectly, so capture the specific section instead of the whole page. The page also calls the feature "in active development," and its statements about which plans include it are not fully consistent, so check the current wording before you plan around it.

Sections suit Bootstrap well. A navbar, a hero row and a card grid are often separate .container blocks, and each can become its own frame.

Option 2, import the saved file with UnHTML

The second route is a plugin. According to the UnHTML site, it converts a webpage into native, editable Figma layers: frames, text, images, vectors and auto layout built from the page's CSS. You give it one of these inputs:

  • A self-contained .html file, dragged onto the plugin's drop zone.
  • A Safari .webarchive file, imported the same way.
  • A scene.json from the open-source CLI, which suits live sites, remote assets and pages built by JavaScript.
  • A scene.json from the bookmarklet.

SVG becomes native vectors. WebP and AVIF images convert to PNG. By default the plugin makes no network requests; fetching remote assets is an opt-in toggle. As of 2026-10-30, the free tier runs the full importer with a cap of 500 layers per import, and Pro ($39, one time per editor) removes the cap. Pricing on that page is marked as launch pricing that may change.

The 500-layer cap matters for Bootstrap. A long landing page with a navbar, several card grids, a footer and icon-heavy rows can pass 500 layers quickly. If you hit the cap, import the page one section at a time, the same way you would with the Chrome extension.

What the Bootstrap grid becomes in Figma

A Bootstrap .row is a flex container, so it is the natural candidate for auto layout. The plugin builds auto layout from the page's real CSS, and it states that a frame which cannot reproduce its captured geometry falls back to absolute positioning on its own. Our flexbox to auto layout map lists which flex properties carry over.

For a Bootstrap page, check these three things by hand after every import:

  1. Row and column frames. Select a .row frame and look at its layout settings in the right panel. If it reverted to absolute, the columns will not reflow when you resize them.
  2. Gutters. Bootstrap makes a 1.5rem gutter from column padding and negative row margins. In Figma, that spacing may appear as padding on each column frame or as the gap on the row. Either is fine, but make it consistent before you build components.
  3. Column widths. Bootstrap sets widths in percentages. In Figma they become fixed or fill widths, and a .col-md-4 at 1140px will sit at the width it had in the capture.

None of this is a defect in the page. It's the cost of turning a responsive layout into one static snapshot.

Read the import report

The plugin produces a report of every font substituted, every frame reverted to absolute, and every image skipped. Read it before you edit anything.

  • Fonts. Missing fonts are swapped, with Inter as the default. Any font that is not installed on your machine is a candidate for substitution. See how missing fonts get replaced and logged.
  • Absolute frames. Each reverted frame is a place where auto layout did not survive. Fix the ones in shared components first.
  • Skipped images. Re-add them manually from the original assets.

Icons need a quick check as well. Inline SVG, such as copied Bootstrap Icons markup, becomes native vectors. An icon font depends on the font loading, so a substituted font changes the glyphs.

After the import, clean up

The imported frames are plain layers. The real work starts here. Rename the top frame with its breakpoint, for example "Home / xl 1200". Delete wrapper frames that exist only because of nesting in the DOM. Then repeat the capture at your other widths and keep each as its own frame.

If your site uses utility classes instead of Bootstrap's component classes, the same steps apply, and the notes on importing a Tailwind site cover how to keep a spacing scale. When you are ready to try the plugin route yourself, UnHTML has the free tier described above.

Conclusion

Figma does not import HTML files, so a Bootstrap page comes in through a capture. Choose the breakpoint first, because Bootstrap's min-width media queries mean each capture is one layout. Capture a section at a time, read the report, and check the row frames, gutters and fonts by hand. You get editable layers that follow the page closely, and you finish the job in Figma.

Frequently Asked Questions

Can Figma import a Bootstrap HTML file directly?

Figma's imports guide lists images, vectors, videos, GIFs, .fig and .sketch files, and does not mention HTML. For a page, the route is a capture: Figma's Chrome extension, or a plugin that reads a saved HTML file.

Which breakpoint should I capture a Bootstrap page at?

Capture one width for each breakpoint you care about. Bootstrap uses min-width queries (576, 768, 992, 1200 and 1400px), so a capture shows only the layout active at the viewport width you used.

Will the 12-column grid become auto layout?

Flex rows can map to auto layout, but a frame that cannot reproduce its captured geometry falls back to absolute positioning. Check the grid by hand and treat the result as editable layers, not a pixel-exact clone.

What happens to Bootstrap Icons?

Inline SVG becomes native vectors in UnHTML. Icon fonts depend on the font loading, so a substituted font can change the glyphs. Check the import report for substitutions.

Questions

Can Figma import a Bootstrap HTML file directly?
Figma's imports guide lists images, vectors, videos, GIFs, .fig and .sketch files, and does not mention HTML. For a page, the route is a capture: Figma's Chrome extension, or a plugin that reads a saved HTML file.
Which breakpoint should I capture a Bootstrap page at?
Capture one width for each breakpoint you care about. Bootstrap uses min-width queries (576, 768, 992, 1200 and 1400px), so a capture shows only the layout active at the viewport width you used.
Will the 12-column grid become auto layout?
Flex rows can map to auto layout, but a frame that cannot reproduce its captured geometry falls back to absolute positioning. Check the grid by hand and treat the result as editable layers, not a pixel-exact clone.
What happens to Bootstrap Icons?
Inline SVG becomes native vectors in UnHTML. Icon fonts depend on the font loading, so a substituted font can change the glyphs. Check the import report for substitutions.