Fix a failed capture
or Figma import.

Capture problems.

“Lil Labr can’t capture this page.”

The panel says this under the page title on Chrome’s own chrome:// pages and on the Chrome Web Store, and its capture buttons are disabled there: Chrome does not let extensions run on those pages. Open an ordinary http or https page. For a local file:// page, open the LilLabr card at chrome://extensions, choose Details and turn on Allow access to file URLs.

Capture full page is disabled.

In a new install, the first capture step has the box I agree to the Privacy Policy and Terms; its link opens a short summary with links to the Privacy Policy and the Terms of Use. No capture starts until the box is ticked: the buttons, the shortcuts, the picker and an AI assistant all wait for it. Tick it, then press Capture full page. An install updated from a version before 1.0.6 counts as having agreed.

The panel is gone.

The LilLabr toolbar icon opens the panel for the tab you click it on, beside the page in Chrome’s side panel, and closes it there. Another tab has no panel until you click the icon on that tab; Chrome hides the panel while another tab is in front and shows it again when you come back. Closing the tab ends its panel.

The shortcut does nothing.

Open chrome://extensions/shortcuts and check that Option+Shift+S and Option+Shift+P, written as Alt+Shift+S and Alt+Shift+P, are assigned to LilLabr and not taken by another extension. Same keys on every platform. In a new install, a shortcut does not start a capture until the Privacy Policy and Terms box is ticked in the panel.

The picker selected the wrong thing.

Press ↑ to grow the selection to the parent, ↓ to go back down, Tab to jump to the next focusable element, and Esc to cancel. While the picker is open, P captures the whole loaded page and V the visible screen.

Content is missing from a full-page capture.

Lists and feeds that render only what is on screen cannot be forced to render everything. Use Capture screen for the state you can see, and capture a long list screen by screen. The thumbnail on Latest capture is drawn from the capture itself, so what the capture missed is missing from it too; press it to see the whole capture. More on app screens.

The capture is slow.

Full-page capture scrolls the document and eligible inner scrollers so lazy content can load, and it fetches every image the page declared. Heavy pages take longer; the panel shows progress while LilLabr works. Try Capture screen or Pick element for a smaller capture.

The capture finished with warnings.

Read them. A missing font means text will fall back in Figma. A blocked or failed asset means paste and file import are refused for this capture; wait for the page to finish loading and capture again. To tell us what went wrong, press Something didn’t come through? under Latest capture: tick what is missing and add a note if you like. The panel shows exactly what the report holds; it never holds page text, form values or the page title. Send it from the panel when it offers Send report; otherwise download the report and email it to support.

Paste problems.

The paste arrived as plain text.

Figma changed its clipboard format. The paste route writes a Figma-compatible payload through an MIT-licensed library, not an official Figma API, so this can happen after a Figma update. Choose Download capture on Latest capture and open the file in the Import a file tab of LilLabr Import; that route does not depend on the clipboard.

Nothing pastes, or something else pastes.

Another copy replaced the clipboard. Open Latest capture in the panel and choose Copy to Figma to copy the cached capture again, then paste into a Figma Design file with the canvas focused. The cache lasts up to 24 hours.

Copy to Figma is unavailable.

The capture recorded a failed asset, so the Figma-compatible payload was not prepared. Capture again after the page’s images have loaded.

An icon pasted as an image instead of a vector.

On the paste route, an inline SVG that uses gradients, clip paths, masks, filters or text arrives as one image. The .labr file route keeps it as editable vectors.

Text looks different.

Fonts are not embedded. Why fonts change and how to put them back.

File import problems.

The plugin refused the file.

The capture’s asset ledger records an image, icon or background that failed during capture, and the current plugin fails closed rather than importing a placeholder. Capture the page again once everything has loaded. Archives made before the ledger existed have no completeness guarantee.

The import was cancelled or rolled back.

Cancel import stops the build and cleans up the page it was building; a page that failed is cleaned up the same way, and pages of a flow that had already completed stay. If the plugin reports that cleanup was incomplete, follow its Undo or delete instructions rather than assuming the page is clean.

The chooser does not accept the file.

The plugin’s Import a file tab accepts .labr archives only, through Choose .labr file or a drop onto the plugin window. Raw .json scenes from older versions are refused; they are not the current format. A file over the reader’s 256 MiB safety limit is refused.

Frames came in without auto layout.

That is the 0.5px rule at work: a frame whose auto layout would move a child by more than 0.5px is put back to fixed positions so it stays true to the page. What converts and how to finish it.

Sync and pairing problems.

The setup code did not work.

A setup code has eight characters in the form ABCD-EFGH, works once and expires in ten minutes. For a fresh one, open the panel’s Capture tab: under Finish setup, press Show setup code on the Figma card, or Get a new code once one has expired. Once Figma is connected, use Settings > Figma > Manage > Get a new setup code. Paste the complete code into the code field of the plugin’s Captures tab. The Figma card says Connected by itself; if it asks instead, press I see it in Figma once the plugin shows it is connected. Pairing while Save captures is off keeps it off; it does not resume uploads.

The capture is not listed in the plugin.

Check Save captures in the panel’s Settings. Turning it on does not upload an earlier capture; Send latest capture under Settings > Figma > Manage sends the latest one that was not. Open Latest capture and look for Try again; a failed upload keeps the local archive. Archives over 50 MB are never uploaded, synced captures expire after seven days, and a page removed on the panel’s Recent tab is no longer listed. In the plugin, Reload captures asks for the list again when the card offers it. Otherwise choose Download capture and import the file.

You want to stop syncing or remove copies.

Turn Save captures off in Settings to stop future uploads. On the panel’s Recent tab, Remove deletes one page of the current flow from your saved captures, after asking. In the paired plugin, open the menu on a synced page or flow and choose Delete synced page or Delete synced flow, then confirm. Turning Save captures off or disconnecting does not delete copies already uploaded. Removing your data.

Still stuck?

Email support with your Chrome extension version, the Figma plugin version if relevant, and what you saw; Contact at the bottom of the panel opens the same support page. Start without a private capture or pairing token. Do not send a .labr file or a screenshot of a private page unless you have reviewed it and chosen to share it. For the AI assistant links, the MCP server page explains pairing and which websites an assistant may capture.