DEV Community

Cover image for Download Website as HTML: Get a Runnable Project From a Figma Capture
Sandeep Virk
Sandeep Virk

Posted on Originally published at crafttor.com

Download Website as HTML: Get a Runnable Project From a Figma Capture

Originally published on Crafttor.

TL;DR: Most ways to download website as HTML give you a broken copy: missing fonts, dead hover states, images pointing back at the live server. WebCapture to Figma's Download HTML saves a captured page as a ready-to-run HTML, CSS and JS project, with its images and Google fonts inside. Hover states, CSS animations and links work in it, and a flow recorded with the Chrome extension replays. You can open it in a browser, add it to Figma as a code layer, or use it as source material for an AI.

Why "Save page as" is not enough

Every browser can save a page. Press Ctrl+S or Cmd+S, choose "Webpage, Complete", and you get an HTML file plus a folder of assets. It is a fair first try. In practice it often falls short:

  • Fonts break. Web fonts loaded from a CDN or via CSS may not come along, so text falls back to a system font.
  • Layout shifts. Pages that build their layout with JavaScript can render differently, or not at all, when opened from disk.
  • Assets point elsewhere. Some images and styles still reference the live server. Offline, they are gone.
  • State is lost. You get the page as it loaded, not after you opened a menu or switched a tab.

Command-line tools like wget --mirror go further, but they copy a whole site's files, not one clean, self-contained page. You still have to sort out what is needed.

What Download HTML gives you instead

WebCapture works differently. It first captures the page into Figma as editable layers, recording how the browser laid it out. Then, after the import, Download HTML saves that page as a project you can run.

According to the plugin's documentation, the project:

  • is plain HTML, CSS and JS, ready to run
  • includes the page's images
  • includes its Google fonts
  • keeps hover states, CSS animations and links working
  • replays a flow recorded with the Chrome extension

Because the images and Google fonts are inside the project, it does not depend on the original site to look right.

How to download a website as HTML, step by step

1. Capture the page

Open WebCapture to Figma in a Figma file. You have two routes.

  • By URL. The page is rendered in a remote browser on Apify. Add your own Apify API token once; a free Apify account is enough to start.
  • With the Chrome extension. Best for pages behind a login or a bot wall. Capture the page as you see it and paste the result into the plugin. This route needs no token.

Choose a width before you import: Desktop 1440, iPad 820, Pixel 7, iPhone 14 Pro, iPhone SE, or a 360px Android phone. The width you pick is the layout you download. For more on picking breakpoints, read importing mobile and tablet websites to Figma.

Capture or rebuild only designs you own or have permission to use.

2. Optionally record a flow

If you want more than the default view, record the clicks in the Chrome extension first, such as opening a menu or toggling a price. That flow replays in the downloaded project. The method is covered in recording a website user flow.

3. Press Download HTML

After the import finishes, press Download HTML in the plugin. Save the project into its own folder so its files stay together.

How to open the project

Open the folder and double-click the HTML file. It opens in your default browser. Hover the buttons, watch the animations, click the links.

If anything does not load when opened straight from disk, serve the folder locally instead. Browsers apply stricter rules to file:// pages, and a local server avoids them. Two common options:

# Python 3, from inside the project folder
python3 -m http.server 8000

# Node.js
npx serve .
Enter fullscreen mode Exit fullscreen mode

Then visit http://localhost:8000 (or the address serve prints).

Since it is a standard static project, you can also open it in your code editor, inspect the CSS, and change things.

What works, and what to expect

Feature In the downloaded project
Layout, colours, gradients, shadows Rendered as captured
Images Included
Google fonts Included
Hover states Work
CSS animations Play
Links Work
Recorded flow from the Chrome extension Replays

A few practical notes:

  • One page, one width. The project reflects the page at the width you captured. Capture again at another width if you need a mobile version.
  • Non-Google fonts. The documentation mentions Google fonts being included. If a site uses a licensed font from elsewhere, check how it renders and swap it if needed.
  • Server features do not come along. Forms that post to a backend, search and logins depend on the original server. The project is a front end copy.

Three ways to use the project

Open it as a reference

Keep a dated snapshot of your own site before a redesign. Months later, you can still open it and see exactly how the old version behaved, including hover timing.

Add it to Figma as a code layer

A frame can show hover states and animations only as recorded data, since a Figma prototype cannot replay CSS animations. A code layer runs them. Figma plugins cannot create code layers, because the Plugin API has no way to make one. So WebCapture offers Copy prompt: paste it into Claude with the Figma MCP connected, and Claude adds the project as a code layer beside your frame. Set the layer to the size the prompt names, then press play. Code layers cannot be resized from the API, so this step is yours. The full walkthrough is in turning a website into a Figma code layer.

Hand it to an LLM

The project is real code, so it is useful context for an AI. You can attach the HTML and CSS files to a Claude or ChatGPT conversation and ask for a specific change. For example: "Convert this hero section into a React component, keeping the CSS values."

If your goal is a fresh rebuild rather than an edit, the Chrome extension's Copy for LLM is built for that. It carries the layout, colours with real gradient stops, border and shadow values, fonts, inline SVG icons, every interaction and any recorded flow.

Privacy

With URL capture, the URL you enter is sent to Apify to be rendered. Nothing from your Figma file is uploaded. Captures pasted from the extension stay on your machine. The plugin never sends anything to an AI. If you share the project with Claude or ChatGPT, that is your choice and your paste.

Get started

WebCapture to Figma is a free plugin. Capture a page you own, press Download HTML, and open the result in your browser. You get an editable frame in Figma and a runnable project on disk from one capture.

FAQ

How do I download a website as HTML with working fonts?

Capture the page with WebCapture to Figma, then press Download HTML. The project includes the page's images and Google fonts, so it renders without reaching back to the original site for them.

Do hover states and animations work in the downloaded HTML?

Yes. According to the plugin's documentation, hover states, CSS animations and links work, and a flow recorded with the Chrome extension replays.

Can I download a page that needs a login?

Yes, through the Chrome extension. Capture the page as you see it, paste it into the plugin, then download. No Apify token is needed for this route.

Is Download HTML free?

WebCapture to Figma is a free plugin. URL capture uses your own Apify account, and a free one is enough to start.

Can I edit the downloaded project?

Yes. It is a standard HTML, CSS and JS project. Open it in any code editor, or hand it to an AI with a specific change request.

Top comments (0)