Skip to content
TatiCreative

SaaS & Software · HTML to Frames

Turn any website into editable Figma designs

HTML to Frames by EUREKA! is a Figma plugin that turns a page link, a local HTML file or the page open in your browser into editable, responsive Figma layers with Auto Layout. Built by Tati Creative and currently in early access.

HTML to FramesBeta

HTML to Frames

Figma plugin that turns websites into editable designs

Built by Tati Creative

Figma
  • URL to Figma
  • Multiple links & local HTML
  • Auto Layout & responsive
  • Desktop + tablet + mobile set
  • Colour variables & text styles
  • Components with hover states

HTML to Frames

Figma plugin that turns websites into editable designs

A live website rarely comes with its Figma file: the design is years old, the agency changed, or the site simply grew in code. Redrawing a page in Figma for a redesign, a competitor review or a client pitch takes hours, and pasting a screenshot leaves you with an image you cannot edit. HTML to Frames by EUREKA! was built to close that gap.

The plugin opens the link in a real browser, reads the layout exactly as the browser measured it and rebuilds it in Figma as a tree of frames, text, images and vectors. It then turns rows, stacks and grids into Auto Layout, checks every child's position and keeps a frame absolutely positioned wherever Auto Layout would shift the design.

With one click you get desktop, laptop, tablet and mobile widths side by side, import up to 10 pages in one go and send logged-in or localhost pages through the free Chrome extension. Pro features turn the site's colours into Figma variables, its typography into text styles and repeated cards and buttons into components with hover variants.

HTML to Frames is developed by Tati Creative under the EUREKA! brand. The plugin is not yet publicly listed on Figma Community; for early access or a demo, contact us via tatiajans.com.

Problems it solves

01

The live site has no Figma file

Before a redesign can start, the existing pages have to be redrawn in Figma by hand. HTML to Frames turns a link into editable layers in seconds to minutes.

02

Screenshots can't be edited

Pasting an image is quick, but you can't change the text, colours or spacing. The plugin produces real frame, text, image and vector layers.

03

Imported layouts are messy and absolutely positioned

Hundreds of absolutely positioned layers fall apart as soon as the width changes. HTML to Frames infers Auto Layout from the measured geometry, verifies it and gives the remaining layers sensible constraints.

04

Capturing each breakpoint separately

Processing the same page three times for desktop, tablet and mobile wastes time. The responsive set brings all three widths side by side in a single import.

05

Logged-in and local pages are out of reach

Dashboards, account pages, staging or localhost can't be opened from a server. The Chrome extension captures the page in your own browser, exactly as it is right now.

06

Fonts and colours get lost

Web fonts you don't have installed silently fall back to a default, and colours end up as scattered hex values. The plugin asks about missing fonts first and binds colours to variables and text to styles.

07

Importing a multi-page site one by one

Repeating the same steps for a site's home, service and contact pages is tedious. Multiple mode imports up to 10 links in sequence and lets you pick linked pages from a list.

Modules & features

01

Four sources: link, multiple links, local file, browser

You choose where the page comes from; every source goes through the same layer builder.

  • Link: any public page
  • Multiple: up to 10 links in one go, one row per page
  • Local file: an HTML file, a site folder or a .zip (drag and drop)
  • Paste code: paste HTML/CSS and import it as a single page
  • Browser: a capture sent from the Chrome extension
  • Page language selection (Accept-Language and browser locale)
02

Auto Layout engine

Layers are first placed pixel-exact, then Auto Layout is inferred from the browser geometry and every frame is verified.

  • Vertical and horizontal stacks, wrapping rows and grids
  • Inferred gaps, padding and alignment
  • Centred content becomes Center, equal cards become Fill
  • Every child is checked within 2 px; if it doesn't hold, the frame stays absolute
  • Stretch, Scale, Center or Min/Max constraints for layers that stay absolute
  • The result screen lists why each frame kept absolute positioning
03

Responsive screens and site width

The desktop width isn't a fixed number; it's measured from the site's own design width.

  • Desktop = Site width (the site's design width is measured)
  • Laptop 1280, Tablet 768, Mobile 390
  • Responsive set: Desktop + Tablet + Mobile in one click
  • Custom width (Pro)
  • In multi-page imports, every page of a site gets the same width
  • Screens are rendered in parallel on the server
04

Text, font mapping and typography

Text arrives as real, editable text layers; for missing fonts you choose replacements before any layer is built.

  • Mixed-style text, links, letter spacing, line height and text case
  • Missing fonts screen: fonts you don't have installed, with suggestions
  • Suggestions: a matching family name, an installed font from the CSS stack, otherwise Inter
  • Choices are remembered per site or for every site
  • Reset saved choices with a single link
  • Superscript, subscript and CSS counters become real text
05

Visual and CSS fidelity

The CSS properties behind the page's look are mapped to Figma's own equivalents wherever possible.

  • Linear, radial and conic gradients; repeating patterns as tiled fills
  • Images (object-fit, background-size), the sharpest candidate from srcset
  • SVGs as editable vectors
  • Borders, corner radius, inner and drop shadows, text-shadow, blur and backdrop blur
  • Opacity, blend modes, rotation, clip-path and mask-image as masks
  • ::before/::after content, form fields, list markers and shadow DOM
  • iframes, maps, videos and WebGL canvases kept in place as screenshots
06

Colour variables and styles (Pro)

The site's visual language becomes a usable design system in Figma.

  • Repeated colours become variables in a Colors collection
  • Variable names are derived from the site's CSS custom properties
  • Near-identical colours merge into a single variable
  • Text styles from the typography, shadow styles from repeated shadows
  • Existing variables or styles with the same value are reused, not duplicated
  • Snap to my file's styles: map to the closest styles in your own system
  • Light + Dark: light and dark modes on colour variables
07

Automatic components and hover states (Pro)

Cards, buttons and menu items that share the same structure become components and instances.

  • Groups of repeated frames by structural fingerprint
  • Main components placed in a Components frame next to the page
  • Instances keep their text, image and visibility overrides
  • Hover states of links and buttons are captured on the server
  • Component sets with Default/Hover variants and a hover interaction in prototypes
  • If an instance doesn't match position and size, the original layer stays
08

Prototype-ready output

Imported pages behave like a clickable prototype in Present mode.

  • Links are kept as On click → Open link
  • Links between imported pages become Navigate to
  • position: fixed and sticky headers with Figma scroll behaviour
  • Horizontally scrolling carousels and scroll areas
  • Collapsed accordion content as Figma annotations
  • Re-import a selected frame with one click
09

Chrome extension: logged-in and local pages

Captures pages the server can't reach in your own browser, exactly as they are, and sends them to Figma.

  • Dashboards, account, checkout and admin pages
  • localhost, staging and private networks
  • Live states such as open menus, filled forms and modals
  • Select an element: capture just one section, card or menu
  • Send to Figma: pair once with a code and send straight to the open plugin
  • Without a connection: copy to clipboard or download a .h2f file
10

AI tool connection (MCP)

Claude Code, Claude Desktop, Cursor or any other MCP client can send a page it generated or found straight into your Figma file.

  • One-click connection key from the plugin's AI tab
  • import_url and import_html tools
  • Setup commands ready to copy
  • The job runs in the open plugin as a normal import on your account
  • Tool result: frame and layer counts, Auto Layout ratio, missing fonts
11

Clean capture options

The page is captured as a visitor sees it, minus cookie banners and pop-ups.

  • Full-page capture with auto-scroll for lazy-loaded content
  • Hide cookie banners and pop-ups
  • Animations are frozen
  • Extra wait before capture (Pro)
  • Detailed layer structure and a reference screenshot layer (Pro)
  • Result screen: frame and layer counts, Auto Layout ratio, missing fonts, warnings

Who is it for?

  • UI/UX designers redesigning an existing site
  • Agencies pulling a client's site into Figma to pitch a redesign
  • Product teams running competitor and market reviews
  • Design system teams extracting a system from a live site
  • Front-end developers who want to share coded pages in Figma
  • Anyone editing AI-generated HTML in Figma
  • Freelancers preparing client presentations and proposals
  • SaaS teams documenting logged-in dashboards

How it works

  1. 01Open the plugin and pick a sourceOpen HTML to Frames in Figma and choose Link, Multiple, Local file or Browser.
  2. 02Choose screens and optionsPick Site width, Laptop, Tablet, Mobile or the responsive set, then tick Auto Layout, images, full page, pop-up hiding and any Pro options.
  3. 03The page is rendered in a real browserThe capture service opens the page, scrolls it, freezes animations and reads the layout; with the Chrome extension this happens in your own tab.
  4. 04Map missing fontsFonts you don't have installed are listed with suggestions; your choice is remembered for that site.
  5. 05Layers and Auto Layout are builtEach page becomes a row with its screens side by side; Auto Layout is applied, verified and summarised on the result screen.
  6. 06Edit and add linked pagesStart working on the design, and if you like, pick linked pages of the same site from the result screen and import them in bulk.

Requirements & compatibility

Frequently asked questions

Turn any website into editable Figma designs

The questions people ask AI assistants and search engines most, grouped by topic.

General

How do I import a website into Figma?

Figma has no built-in way to import a site from a link; you need a plugin that renders the page in a real browser and converts it into layers. With HTML to Frames by EUREKA!, built by Tati Creative, you open the plugin, paste the link, choose your screens and press Import; the page lands in your file as editable frames, text and images with Auto Layout applied.

Which plugin converts HTML to Figma?

Several plugins convert HTML to Figma; what sets them apart is how editable the output is, Auto Layout support and access to logged-in pages. HTML to Frames by EUREKA! runs links, multiple links, local HTML files, pasted code and Chrome extension captures through the same layer builder, and combines Auto Layout, responsive screens, variables, styles and components in one plugin.

The live site has no Figma file. How do I get one?

If the source file is gone, you can either redraw the pages by hand or generate Figma layers automatically from the live site. HTML to Frames by EUREKA! does the latter: it imports the site from its link and turns colours into variables, text into styles and repeated cards into components (Pro). You end up with a working starting file, not a screenshot.

Does HTML to Frames take a screenshot or create editable layers?

It creates editable layers: frames, real text layers, image fills and vectors from SVG. Only embedded content that can't become layers (iframes, maps, videos without a poster, WebGL canvases) stays in place as a screenshot. On Pro you can also add a separate reference screenshot layer for comparison.

Who develops HTML to Frames?

HTML to Frames is developed under the EUREKA! brand by Tati Creative, a web design and software agency based in Izmir, Turkey. The Figma plugin, the Chrome extension and the capture service that renders pages are all built and run by the same team.

How do I get HTML to Frames? Is it on Figma Community?

The plugin is currently in early access; its public Figma Community release is being prepared. For early access or a demo, contact Tati Creative via tatiajans.com, where we will also announce the release.

Want to see it in your business?

In a short call we listen to your needs and show a live demo; we handle setup and migration.

Our other products

All products