LilLabr Import,
the Figma plugin.

When you need the plugin, and when you do not.

You may never need the plugin. A successful capture in Chrome puts a Figma-compatible payload on the clipboard, and pasting into a Design file is the fastest route. The plugin earns its place in four situations:

• Paste lands as plain text. That means Figma changed its clipboard format. The file route does not depend on it.
• You want a file. A .labr archive can be kept, sent to a colleague or imported later, with no network needed to read it.
• Your page has rich inline SVG. An inline SVG that uses gradients, clip paths, masks, filters or text pastes as one image; the file import keeps it as editable vectors.
• You use Save captures. Synced captures and multi-page flows are listed and imported from the plugin’s Captures tab.

Install it from Figma Community.

Get LilLabr Import from the official Figma Community listing (listed as LilLabr - Website to Figma), then run it from the Plugins menu inside a Design file. The plugin window has four tabs: Captures, Import a file, Settings and Contact. The plugin and the Chrome extension are separate installs that are updated separately; the plugin’s Contact tab links to the extension, and the panel’s Figma card links back with Open Figma plugin.

Import a .labr file.

1. In Chrome, choose Download capture under Latest capture. What the file contains.
2. In the plugin, open the Import a file tab, then choose Choose .labr file or drop the file anywhere on the plugin window. Only .labr archives are accepted; a JSON file is refused.
3. Read the file view: title, source address, capture mode, viewport size, layer and font counts, and any fonts that are missing on this computer.
4. If the archive holds several captures, pick one. Check Import options, then choose Import into Figma.
5. Watch progress in the work area; the tabs stay locked until it ends. Cancel import stops the build and requests cleanup of the current page.

A successful single-page import is one frame named after the page, selected and zoomed to. If a page of a flow fails, the pages that already completed stay, and any cleanup the plugin could not finish is reported rather than claimed. A capture whose asset ledger records a failed asset is refused before anything is built; capture the page again once it has fully loaded. If the plugin still refuses it, the asset was blocked, oversized, empty or unsupported, and the capture report under Latest capture is the place to say so.

The two import options.

Synced captures and flows.

With Save captures on in Chrome, each future usable capture uploads its full .labr archive and a thumbnail to the developer-operated LilLabr service, whose operator can read them. To list them in Figma, open the panel’s Capture tab and, under Finish setup, press Show setup code on the Figma card (once Figma is connected: Settings, Figma, Manage, Get a new setup code). The setup code has eight characters in the form ABCD-EFGH, works once and expires in ten minutes. Paste it into the code field of the plugin’s Captures tab. The plugin connects on receipt, keeps the connection across restarts, and lists uploaded captures grouped into flows; the panel’s Figma card turns Connected by itself, or asks you to press I see it in Figma where the sync service cannot say. Pairing does not turn Save captures on if you had set it off.

Choose Import all N pages to build a whole flow, laid out left to right in capture order, or Import page on one capture. Each synced archive is downloaded and checked against its recorded checksum before the same reader that handles a local file opens it. Synced captures expire after seven days, the service keeps the newest 50 per workspace, and archives over 50 MB are never uploaded. In the menu on a card, Delete synced page or Delete synced flow removes cloud copies after confirmation; saved files and layers already in Figma stay. On the panel’s Recent tab, Remove deletes one page from your saved captures so the plugin stops listing it, and Download all N pages saves the flow as one .labr file that the Import a file tab opens with a list of its pages. Turning Save captures off or disconnecting does not delete uploaded copies. The privacy policy has the full retention and deletion details.

After the import.

• Fonts. The plugin loads the capture’s family when it is installed or is a Google Font Figma can load. Otherwise it tries the family’s Regular style, then the closest weight of Inter, then Roboto, and lists each substitution in its log. Restoring the original font.
• Nothing goes back up. The plugin never uploads your existing Figma layers, and opening a local file does not contact the sync service.
• Optional review request. After five successful imports (a file, a synced page, or each page of a flow, counted once each) the plugin may show a short review card: on the Import a file tab, or on the Captures tab while the plugin is paired. Later dismisses it for 30 days; it may ask again at 15, 30, 50 and 100 imports. It confirms only that you opened the listing, never whether you posted a review.
• Usage analytics is on unless you turned it off in an earlier version of the plugin. There is no switch; the Settings tab has one line about it with a link to the privacy policy, which says how to object. It never includes capture content.

Trouble importing? Read the troubleshooting guide or contact support.