Importing a WordPress Theme Page Into Figma for a Redesign
Import a WordPress theme page into Figma by capturing the rendered page, not the theme files. Steps, limits and what to check after.
To get a WordPress theme page into Figma, capture the page as it renders in a browser and import that file. You do not need the theme's PHP or block template files for the import. This tutorial assumes the page loads in your browser and that you have UnHTML installed in Figma.
The steps are short. Work out which template renders the page, capture the rendered result, import it, check the report, and map each frame back to a template when the redesign is done.
Find the template that renders the page
A redesign of a WordPress site ends in template files, so it helps to know which file produces the page you are about to import. Do it before you capture anything. The answer tells you how many frames you need.
Why the template matters
The page you see in the browser comes from one template file in the theme. The design you build in Figma will eventually replace that file's markup. If you import the About page but the theme renders it with a generic template, your new design will affect every page that uses it.
The lookup order
WordPress picks the template for a static page in a fixed order, according to the WordPress theme handbook:
- A custom template assigned to the page
page-{slug}.phppage-{id}.phppage.phpsingular.phpindex.php
The front page has its own chain. If front-page.php exists, it overrides home.php. Block themes use HTML files instead of PHP files, and the handbook states that the hierarchy is the same. A slug-specific file beats page.php, and the first match in the list is the one in use.
Capture the rendered page
UnHTML doesn't take a URL directly. It reads a file, so your first job is to produce one. According to the UnHTML site, the plugin accepts three kinds of input: a self-contained .html file, a Safari .webarchive, or a scene.json from the open-source CLI or bookmarklet.
Pick a capture method
- If the theme page renders its content without needing scripts, save it as a self-contained HTML file or a Safari web archive. Both carry their own assets.
- If the page is built by JavaScript, loads remote assets, or you want to start from a live URL, use the CLI. Run
node capture/cli/capture.jswith the page URL and name the output filescene.json. - Drop the resulting file onto the plugin's drop zone in Figma.
The UnHTML site recommends scene.json for live sites, remote assets and JavaScript-built pages. If your theme builds sections with scripts, treat it as JavaScript-built and use the CLI. Check your own page before assuming either way.
Pages behind a login
A staging copy of a WordPress site is often locked. The approach for that case is covered in capturing a page behind a login.
What the capture sends
With default settings the import makes zero network requests, and scripts, inline event handlers and javascript: URLs are stripped from the markup before rendering. Fetching remote assets is an opt-in toggle that is off by default. The CLI is different: its headless browser does fetch remote assets when it captures a URL, so run it only against pages you are allowed to load.
Import and read the report
After the file is imported, open the import report before you touch the canvas. It tells you what the tool had to work around.
Layer cap
The free tier caps an import at 500 layers. A long theme page with many nested wrapper elements can pass that number. Pro ($39 one-time per editor, as of 2026) removes the cap. If your page hits the limit, import one section at a time, or move to Pro.
Auto layout and absolute positioning
The importer maps the page's CSS to auto layout where it can. Frames that cannot reproduce the captured geometry fall back to absolute positioning. In a WordPress theme this tends to happen with deeply nested builder wrappers, so expect to simplify a few frames by hand.
Fonts
Fonts that are not installed on your machine are replaced, with Inter as the default, and each substitution is listed in the report. Theme pages often load custom web fonts, so read the font list first. How missing fonts get replaced explains how to resolve them.
What to check after the import
An import is a starting point for the redesign, not a finished file. It isn't an exact clone of the page, so don't treat it as one.
Figma's own page capture has the same limit. Its help center says captures come in as plain Figma layers, not mapped to your library components or styles, and that heavy JavaScript animation, canvas rendering and virtualized lists may not translate cleanly (see Figma's guide to turning webpages into editable layers). Expect plain layers from any import path. Plan to componentize afterward.
A short checklist for a theme page:
- Compare the frame against the live page at the same viewport width.
- Delete layers that belong to the theme's furniture and not to the design, such as cookie banners and floating widgets.
- Check text runs for line breaks that differ from the browser.
- Resolve the font substitutions from the report.
When the frames look right, work through cleaning up an import before you build components.
Map frames back to templates
The goal of a redesign is new templates, so organize the Figma file the way the theme is organized. Give each template that matters its own frame: one for front-page, one for the default page template, one for the single post view, one for the archive. Name the frames after the template files they replace.
If the site uses a child theme, remember that a file in the child theme overrides the same file in the parent theme. Look in the child theme first when you decide which template a frame replaces, because the parent file may never run. Keep a short list of the frames, the template file behind each, and the viewport width you compared at, so the next person can repeat your checks.
That keeps the handoff honest. A developer reading the file can see that the "page" frame replaces page.php, and that a slug-specific file such as page-about.php needs its own frame only if its layout differs. UnHTML gets you the starting layers; the template mapping is your decision.
Conclusion
Capture the rendered page, import it, read the report, and treat the result as editable layers rather than a clone. Knowing the template hierarchy up front tells you how many pages you actually need to import, and naming frames after template files makes the redesign easy to hand off.
Frequently Asked Questions
Can UnHTML import a WordPress page from its URL?
Not directly. The plugin takes a self-contained HTML file, a Safari web archive or a scene.json. To start from a live URL, the open-source CLI captures it to scene.json, which you then import.
Do I need the theme's PHP files to import a page?
No. The import works from the rendered page. The PHP or block theme files only matter when you map the finished design back to templates.
Why do some sections come in as absolute positioning?
Frames that cannot reproduce the captured geometry with auto layout fall back to absolute positioning. Page builder wrappers with heavy nesting are a common cause.
Will the free tier handle a full theme page?
The free tier caps an import at 500 layers. A long page built with a page builder can pass that, in which case Pro removes the cap.
Questions
- Can UnHTML import a WordPress page from its URL?
- Not directly. The plugin takes a self-contained HTML file, a Safari web archive or a scene.json. To start from a live URL, the open-source CLI captures it to scene.json, which you then import.
- Do I need the theme's PHP files to import a page?
- No. The import works from the rendered page. The PHP or block theme files only matter when you map the finished design back to templates.
- Why do some sections come in as absolute positioning?
- Frames that cannot reproduce the captured geometry with auto layout fall back to absolute positioning. Page builder wrappers with heavy nesting are a common cause.
- Will the free tier handle a full theme page?
- The free tier caps an import at 500 layers. A long page built with a page builder can pass that, in which case Pro removes the cap.