Questions about
website to Figma.

Basics.

Is LilLabr free? Do I need an account?

Capturing and importing need no LilLabr account. There are no import credits and nothing to buy inside the extension or the plugin. LilLabr 1.0.6 can offer a Google sign-in; it is optional, keeps your progress across browsers and is needed only to set up Claude or ChatGPT through the hosted AI connector link. You need a Figma account for Figma itself, and Figma handles pasted or imported layers under its own terms.

What does LilLabr do?

It captures a rendered webpage, a visible screen or one element from Chrome and brings supported text, images, vectors, fills, strokes and layout into Figma as editable layers. How website capture works.

Which browsers does it work in?

Desktop Chrome, through the LilLabr extension on the Chrome Web Store. Other browsers are not tested, and Chrome on Android and iOS does not run extensions.

Does it work with FigJam or Figma Slides?

The guides, the paste route and the plugin are written for Figma Design files. Other Figma editors are not covered.

Do I need the Figma plugin?

Not for the paste route: a successful capture puts a Figma-compatible payload on the clipboard, and you paste into a Design file. The LilLabr Import plugin is for .labr files, on its Import a file tab, and for synced captures, on its Captures tab.

Does paste use an official Figma API?

No. It writes a Figma-compatible clipboard payload through an MIT-licensed library, so a Figma clipboard-format change can break paste. The .labr file route does not depend on it.

What is the box on the first capture step?

In LilLabr 1.0.6 the panel asks you to tick I agree to the Privacy Policy and Terms before your first capture. Capture full page stays disabled until you do, and no capture of any kind starts before it. In a new installation, agreeing also turns Save captures on and starts usage analytics. An installation updated from an earlier version counts as having agreed. The Terms of Use.

Capturing.

What can I capture?

What is on screen (Capture screen), the whole loaded page (Capture full page, the panel’s main button) or one element (Pick element). Screen is the recommended default for web apps, dashboards and feeds. The step-by-step guide.

Which pages cannot be captured?

Chrome’s own chrome:// pages and the Chrome Web Store, because Chrome blocks extensions there. Local file:// pages work once you enable Allow access to file URLs for the extension.

Can I upload an HTML file or paste HTML code?

No. LilLabr reads the rendered page in Chrome. Save the code as an .html file, open it in Chrome and capture it. What HTML to Figma means here.

Can it convert a screenshot I already have?

No. A screenshot is pixels; LilLabr needs the live page. Screenshots compared with editable layers.

Can I capture a page I am logged in to?

Yes. The capture reads the tab in your own Chrome, so your session stays in Chrome and LilLabr never asks for your password. Password fields and identified card fields are masked in the capture; visible text is captured as text. With Save captures on (the default after you agree in a new installation) the capture, including visible page text and form values, uploads to the developer-operated service, where the operator can read it; turn Save captures off in Settings first to keep it on this computer. Private pages.

Can I capture the mobile layout?

Narrow the Chrome window to a phone width and capture; the frame keeps that viewport size. Mobile view guide.

Can I capture a whole site at once?

Page by page. With Save captures on, capture pages in order and import the whole flow from the plugin’s Captures tab, laid out left to right; New flow in the panel starts the next one. The local MCP server can capture up to ten addresses in one flow for an AI assistant.

What are the keyboard shortcuts?

Option+Shift+S starts the element picker and Option+Shift+P captures the screen. Chrome writes them as Alt+Shift+S and Alt+Shift+P; same keys. Change them at chrome://extensions/shortcuts.

Into Figma.

Why do fonts look different after import?

Font files are not embedded. On the paste route, Figma measures text with Fontsource copies of Google Fonts fetched from jsDelivr, and a family that is not on Fontsource falls back to Inter. On a .labr import, the plugin loads the same family from Figma’s font list when it is installed or is a Google Font, otherwise falls back to Inter, then Roboto, and logs the substitution. How to put the original back.

Do I get auto layout?

Where it fits. Flex rows and columns, one-dimensional grids and simple stacks carry hints; the plugin applies auto layout and reverts any frame that would move a child by more than 0.5px. Details.

What is a .labr file?

LilLabr’s capture archive: a plain ZIP with a manifest, the editable scene and its images. Download it from the panel with Download capture, open it on the plugin’s Import a file tab, or unzip it yourself. What is inside.

My paste arrived as plain text.

Figma changed its clipboard format. Press Download capture and import the .labr file on the plugin’s Import a file tab. More fixes.

Why was my import refused?

An image, icon or background failed to load during capture. LilLabr records it and refuses to import that capture rather than substitute a placeholder. Capture again once the page has loaded.

Can it export Figma to HTML?

No. LilLabr goes one way, from a rendered page into Figma.

Will the import be pixel-perfect?

LilLabr does not promise that. One controlled sample on this site shows editable output with header wrapping still to tidy. Complex layouts can need cleanup. The verified example.

Privacy and data.

Does a capture leave my computer?

It depends on the route. With Save captures off before capture, paste and .labr file import stay off LilLabr’s sync service. The paste route may fetch fonts from jsDelivr, image re-fetches go to the page’s own hosts, Figma receives what you paste, and your clipboard history may keep a copy. With Save captures on, each future capture and a thumbnail upload to the developer-operated service, whose operator can read them. The optional AI connector link is a separate path through LilLabr’s cloud. The privacy policy.

Is Save captures on by default?

In a new installation, agreeing to the Privacy Policy and Terms on the first capture step turns Save captures on, for that capture and future captures. An installation updated from an earlier version keeps the choice it had, so an explicit Off choice stays Off. In a new installation that first capture is saved by the agreement; after it, turn Save captures off in Settings before capturing anything you want to keep local. The privacy policy also calls this switch Cloud sync.

How long are synced captures kept?

Seven days, the newest 50 per workspace, and archives over 50 MB are never uploaded. Remove a page from the panel’s Recent tab, or use Delete synced page or Delete synced flow in the plugin; turning Save captures off or disconnecting does not delete uploaded copies.

How long does Chrome keep my latest capture?

Up to 24 hours in the extension’s local storage so you can copy or download it again. Forget latest capture in Settings removes it sooner, together with the capture’s picture. Pictures of your 24 newest captures stay on this computer for up to 7 days.

Does LilLabr track me?

Usage analytics is on by default in LilLabr 1.0.6, and neither the panel nor the plugin has a switch for it. In a new installation it starts when you agree to the Privacy Policy and Terms on the first capture step; an installation updated from an earlier version keeps the choice it had. To object, write to the contact address in the privacy policy. When on, it sends limited feature actions and outcomes to PostHog with a random installation id, never page content, addresses, titles, codes or tokens.

What is masked in a capture?

Passwords, identified card fields, and populated fields inside embedded frames. Visible text is captured as text, and unmarked top-level card fields may be captured. Since 1.0.6 the thumbnail is drawn from the capture itself, so it masks those fields too; the only screenshot left is the viewport preview an AI assistant asks for. Capture is not a complete redaction system.

AI assistants.

Can Claude, Cursor or ChatGPT use LilLabr?

Yes, in two ways. The local MCP server, lillabr-mcp, is published on npm and works with apps that run a local program: Claude Desktop, Claude Code, Cursor, Codex and the ChatGPT desktop app. You pair once with a six-digit code shown in the panel and allow each website; nothing is uploaded. LilLabr 1.0.6 adds a hosted AI connector link for apps that cannot run a local program: Claude on the web, desktop and phone, and ChatGPT on the web on plans that allow custom connectors; Codex and Claude Code can use it too. It needs a Google sign-in, and captures pass through LilLabr’s cloud. How it works.

What are the WebMCP tools?

Five tools the extension registers for an agent running inside the browser, while a LilLabr panel is open for any tab: status, screen, full page, element and save. They need a browser with WebMCP on and an agent that reads page tools, which is not ordinary Chrome today. Who can use them.

Does an AI capture upload anything?

Not through the local link. Captures made for a local assistant are saved on your computer, never put on your clipboard, never uploaded by LilLabr even with Save captures on, and never replace your latest capture. What the assistant reads goes to the AI app you connected. The AI connector link is different: a capture the app asks for goes through LilLabr’s cloud, encrypted with a key from the link but not end-to-end encrypted, and is readable for an hour after the app last reads it, a day at most. Anyone who has the link can ask for captures, and each website still needs your Allow in Chrome. While Save captures is on, a connector capture is also saved like your own. If you want nothing in the cloud, use the local link.

Something else?

Browse all guides, read the comparison with html.to.design, or email support. The plugin is on Figma Community.