Any web UI becomes editable Figma layers.Icons stay vectors.

I got tired of rebuilding interfaces in Figma that already existed on the web. Mimic reads the page's DOM and reconstructs it as real Figma layers — named, nested, ungroupable, resizable. Every inline SVG icon arrives as an editable vector node, not a flattened image.

Free for your first 10 exports. No account needed to try it.

https://any-web-app.com/dashboard
Group / Sidebar
Group / Stat card
Group / Toolbar
Group / Chart
Group / Activity
Group / Icon set
Layers produced

Every element here is a real Figma node, not a region of an image.

Drag across the window to scrub · press Mimic to re-run

Icon sets that arrive as vectors, not pictures

See it run

Sixty seconds, one click, zero redraw.

A real dashboard captured live, landing in Figma with its layer tree intact.

The difference

Other tools hand you a picture of an icon.

Screenshot-based importers flatten every icon into a raster image. You can move it, but you can't recolor it, can't resize it without softening the edges, and can't touch a single path. Some tools even document the workaround: rasterize your vectors first, then swap them back by hand after import. Mimic reads the SVG out of the DOM, so there's nothing to swap back.

Rasterized — other tools
Vector — Mimic

Drag to compare. Both are the same icon at the same size.

How it works

Three steps. No server in the middle.

01

Install and paste your key

Add the extension, paste your own Figma API key once. It stays in your browser — the capture never routes through infrastructure I control.

02

Open any page and click

Public sites, staging environments, or apps behind a login. It captures whatever your browser can already see, using your existing session. No credentials change hands.

03

Layers land in Figma

Pushed straight to your file over the Figma REST API. Named, nested, ungroupable. Zoom to pixel level and check the spacing against the original.

Compared to screenshot tools

Reading the DOM beats guessing at pixels.

Mimic is deterministic extraction, not image interpretation. Run it twice on the same page and you get the same result twice.

 Screenshot-based toolsMimic
Inline SVG iconsFlattened to images, or converted in a second manual passEditable vector nodes, automatically
Output consistencyVaries between runsSame input, same output, every time
Layer structureApproximated from visual groupingTaken from the actual DOM tree
Pages behind a loginUsually unsupportedWorks — uses your live browser session
TextOften baked into the imageReal text layers with detected fonts
Where your page data goesUploaded for processingStays client-side; pushed only to your Figma file

Pricing

Start free. Upgrade when it saves you a workday.

30 pages

Free
$0
  • Up to 10 exports
  • Full-fidelity DOM capture
  • Editable vector icons
  • Push to your own Figma file
Add to Chrome
Pro Popular
$9/month
  • Unlimited single-page exports
  • Everything in Free
  • Authenticated app capture
  • Priority email support
Get Pro
Studio
$27/month
  • Up to 5 members (6 on annual)
  • 15 URLs per job
  • Up to 150 pages per month
  • Page count preview — coming soon
Get Studio
Enterprise
Custom
  • Volume capture limits
  • Deployment via browser policy
  • Invoicing and procurement
  • Direct line to me
Get in touch

Questions

Before you install.

Is this AI?

No. It's deterministic DOM extraction — the extension reads the same computed styles and SVG markup your browser uses to paint the page, then maps them to Figma nodes. Nothing is inferred or approximated, which is why repeat runs match.

Where does my page data go?

Nowhere I can see. The extension runs client-side and talks directly to Figma's REST API with your key. There's no backend collecting captures.

Does it work on apps behind a login?

Yes. It captures what's already rendered in your browser using your existing session. You never hand over credentials.

What about icon fonts or CSS background images?

Inline SVG is preserved as vector paths. Icon fonts render as text with the font recorded, and CSS background images come through as images — those genuinely are images on the source page.

Do I need a Figma paid plan?

You need a Figma account and a personal access token. The REST API works on free accounts for files you can edit.

What happens after 10 free exports?

The extension keeps working for anything already captured; new exports need Pro. No trial timer, no card up front.

Stop redrawing what already exists.

Add the extension, capture a page, and see whether the layers hold up. Ten exports free.

Occasional build notes. No drip campaign nonsense.