Web pages in.
Editable Figma layers out.
Capture any page, from localhost to production, and import it as real auto layout bound to your tokens. Design in code, then hand off in Figma.
Capture any website.
Private pages included.
Add to ChromeWebhooks that
just arrive.
Reliable delivery, retries and observability for every event your product sends.
POST /v1/events
{ "type": "invoice.paid",
"retries": 5, "region": "eu" }Total balance
$48,290.40
+12.4% this month
Recent
Notes that
think with you.
Draft brief, align with design, book review.
Capture any website. Pages on localhost, staging links or live sites become frames on your canvas, one per viewport, ready to edit.
How capture worksSend pages straight from your browser.
No export step.
Local bridge between the extension and FigmaTotal balance
$48,290.40
+12.4% this month
Recent
Works with your stack. Capture from your browser, from the command line or through the local bridge. Lovable, v0, Cursor and plain HTML all work, because Peel reads the rendered page.
Local bridgelocalhost:4455 · Figma plugin connected
$ node tools/peel.js http://localhost:3000/shop --widths 1440,390 --themes light,dark --bridge http://localhost:4455
Opening page localhost:3000/shop
debugger attached · 4 captures queued
Capturing 1440 light
510 layers · 346 frames · 112 text
Sending to the bridge
154 of 174 colour variables matched
Import ready · 4 frames placed side by side.
Real layers, bound to your system.
Not a flat screenshot.
Auto layoutWebhooks that
just arrive.
Reliable delivery, retries and observability for every event your product sends.
POST /v1/events
{ "type": "invoice.paid",
"retries": 5, "region": "eu" }See how an import is layered. Every frame keeps the structure of the page: auto layout containers, real text, shapes and images, with colours and type bound to your variables and styles.
Auto layoutEverything it converts.
Down to the details.
All featuresCapture anything that renders.
No setup per tool. If it loads in your browser, whether it is local, staged, AI-generated or behind a login, Peel can capture it.
How capture workslocalhost:3000/dashboardLocalhostpr-482-acme.vercel.appPreview URLapp.acme.com/settingsBehind loginmy-app.lovable.appAI-built appfile:///site/index.htmlStatic HTMLstaging.acme.dev/pricingStagingKnow exactly what landed
Every import comes with a report, so you see what was built and what still needs a decision before design review.
Questions, answered
More in the help center.
Do my pages leave my computer?
No. Captures are files on your machine, and the optional bridge only talks to localhost. Private, local and logged-in pages work because the capture happens in your own browser.
Why does my browser show a debugging bar?
Resizing the page and forcing light or dark mode use the browser's DevTools protocol, so your browser shows its debugging bar while a capture runs. It goes away when the capture ends.
Does it work with Lovable, v0 or Cursor projects?
If it renders in your browser, Peel can capture it. That includes localhost, preview branches and anything behind a login.
What happens to fonts I do not have?
Figma needs the font installed. If it is missing, text falls back to Inter and the import report tells you which fonts were swapped.
Does it keep my design tokens?
Yes. Colours, spacing, radius and text styles bind to the variables and styles already in your Figma file, and anything that does not match is listed in the import report.
Does it create auto layout?
Yes. Flex and grid containers become auto layout frames with gap, padding and alignment, so the result resizes the way the page does.
Which browsers are supported?
The extension is built for Chrome and other Chromium-based browsers. Edge, Brave, Opera and Arc should work too, but we have only tested Chrome so far. The Figma plugin runs in the Figma desktop app and in the browser. Firefox and Safari are not supported yet.