COMPARISON
LilLabr and html.to.design,
compared plainly.
Both tools capture a rendered webpage from a browser extension and build it as editable layers in Figma. They differ in routes, formats, accounts and limits. This page sets them side by side from published documentation, without a fidelity verdict either way.
How this comparison was written.
LilLabr’s own documentation names html.to.design as a product with the same browser-to-editable-Figma workflow, and its benchmark brief uses html.to.design as the comparator, so the comparison is between two products that solve the same problem. Each row below is either a published html.to.design statement or a documented LilLabr behavior, as of LilLabr 1.0.6. Where html.to.design’s public pages did not cover a topic, the row says so rather than guessing.
Side by side.
| Topic | LilLabr | html.to.design |
|---|---|---|
| Where the capture happens | In the Chrome extension’s panel, from the tab you are looking at. | In its browser extension; its install guide lists Chrome, Edge, Brave, Opera, Arc and other Chromium browsers. |
| Other ways in | None. A page has to be open in Chrome. Local file:// pages work once you turn on Allow access to file URLs for LilLabr on chrome://extensions; chrome:// pages and the Chrome Web Store cannot be captured. An AI assistant that asks for a capture gets it from your Chrome too. | A public URL entered in the plugin, pasted HTML and CSS, and uploaded .html, .htm or .zip files. Its documentation also describes an MCP route whose tools include import-url and import-html. |
| Routes into Figma | Clipboard paste into a Design file; a downloaded .labr file opened in the LilLabr Import plugin’s Import a file tab; with Save captures on, synced captures listed in the plugin’s Captures tab after a one-time setup code. | Direct transfer to its plugin while signed in to Figma; a local .h2d file dropped into the plugin. Its store listing also describes clipboard copy and a .make file for Figma Make. |
| Account | No LilLabr account is needed to capture or import. A Google sign-in in the panel is optional and is needed only for the hosted AI connector link. You need a Figma account for Figma itself. | Free tier without signup or card, per its pricing page. |
| Import allowance and price | No import credits and nothing to buy inside the extension or plugin. | Free: up to 10 imports every 30 days per its pricing page; another of its pages says 12 per month. PRO: $12 per user per month billed annually or $18 monthly, advertised as unlimited with a 1,000-imports-per-month fair-use limit. |
| Viewports and themes | One capture per width and theme. Resize Chrome and capture again; each becomes its own frame. Mobile view guide. | Multiple desktop, tablet and mobile sizes and light or dark theme variants can be chosen in one import. |
| Auto layout | An option in the plugin’s Import options. Any frame that would move a child by more than 0.5px is put back to fixed positions. Details. | An option applied during import. |
| Fonts | Not embedded. In the plugin, a family on Figma’s font list (installed or a Google Font) loads; others fall back to Inter, then Roboto, with the substitution logged. On paste, text is measured with Fontsource copies of Google Fonts and a family not on Fontsource falls back to Inter. The plugin’s file view lists missing fonts; there is no mapping dialog. | Missing fonts can be mapped to installed alternatives or downloaded through the plugin, per its font documentation. |
| Prototype output | None. Layers only. | Advertises linked pages imported into a prototype flow, overflow and sticky scroll behavior, and hover states as component variants. |
| Images | Captured bytes embedded as PNG, JPEG or WebP. | High-resolution image replacement is a PRO feature. |
| Many pages at once | With Save captures on, capture pages in order as a flow, then Import all N pages from the plugin’s Captures tab, laid out left to right. The panel’s Recent tab can also Download all N pages as one .labr file for the plugin’s Import a file tab. | Bulk import and a re-import shortcut are PRO features. |
| Embedded frames | Captured as editable layers inside the frame’s box, including cross-origin embeds. | Not covered by the documentation consulted. |
| Form fields | Values shown; passwords and identified card fields masked; populated fields inside embedded frames masked. | Not covered by the documentation consulted. |
| File format | .labr, a documented plain ZIP you can open with any unzip tool. What is inside. | .h2d. Its internal format is not covered by the documentation consulted. |
| Keeping a capture local | Turn Save captures off in Settings before capturing; paste and file import then stay off LilLabr’s service. Paste may fetch fonts from jsDelivr; Figma receives what you paste. | Its private-page documentation recommends the local .h2d download when captured data must stay off its servers. |
| AI assistants | Two links. The local server lillabr-mcp, on npm, for assistants on your computer; nothing is uploaded. A hosted connector link for Claude on the web, desktop and phone, ChatGPT on the web (on plans that allow custom connectors with full tool access), Codex and Claude Code; captures go through LilLabr’s cloud, and creating the link needs a Google sign-in. WebMCP tools for browsers that support them. How they work. | An MCP route with import-url and import-html tools, set up from its plugin’s MCP tab while signed in, per its documentation. |
Reasons you might pick html.to.design.
- You want to import from a public URL, pasted code or an HTML file without opening the page in a browser.
- You want several viewports and both themes from one import.
- You want prototype flows, scroll behavior and hover variants generated for you.
- You want a dialog to map missing fonts, or high-resolution image replacement.
- You use a Chromium browser other than Chrome.
Reasons you might pick LilLabr.
- You do not want an account or an import allowance in the way of a quick capture. Capturing never needs a sign-in.
- You mostly paste. A capture lands on the clipboard and goes straight into a Design file without running a plugin.
- You want a capture format you can inspect yourself, and an import that fails rather than substituting placeholders for images or SVGs that could not be captured (an embedded frame that never loaded is the one disclosed grey placeholder).
- You capture signed-in app screens and embedded widgets and want them as layers, with form values masked where identified. Private pages.
- You want an AI assistant to capture pages in your Chrome: on your own computer with the local lillabr-mcp server, or from Claude or ChatGPT on the web through the hosted connector link.
What this comparison does not say.
It does not say which tool produces the more faithful import. No side-by-side fidelity result is published here. LilLabr’s own records include a single html.to.design control import of one public page, and that pilot is not a same-state comparison. LilLabr does not promise pixel-perfect output. html.to.design’s pages promise accurate editable imports without publishing a quantitative measure, and its troubleshooting pages describe cases that need manual preparation before capture. The verified LilLabr evidence on this site is one controlled sample, shown in the redesign guide, with its remaining cleanup described.
Try the step-by-step guide on an owned sample page, or install LilLabr from the Chrome Web Store and judge the result on a page of your own.