How to Convert a Figma Design into a Custom WordPress Theme
You’ve signed off on a design in Figma, and now it needs to become a real WordPress site your team can edit. There’s no export button that produces a fast, maintainable theme, but there is a dependable process. This guide walks through it, step by step, the way our Figma to WordPress team runs it on client projects.
Can you convert Figma to WordPress automatically?
Not well. Figma describes how a page looks at specific screen sizes. A WordPress theme also has to define how content is stored and edited, how layouts adapt to every screen width, how the site behaves with real content of unpredictable length, and how it works with a keyboard and screen reader. Plugins and export tools that generate pages from Figma frames tend to produce heavy markup with fixed positioning, poor accessibility and an editing experience that breaks as soon as content changes.
Figma Sites can publish simple sites directly from Figma, and you can embed a Figma file or prototype in a WordPress page with Figma’s embed code, which is useful for sharing a design for review. Neither turns a design into a WordPress theme with a content management system behind it. That takes development.
Step 1: Prepare the design for handoff
A clean Figma file saves time and prevents guesswork during the build. Before development starts, check that the file includes:
- Every page template the site needs, such as home, interior page, blog listing, single post, archive, search results and 404.
- Desktop and mobile layouts at minimum, with tablet where the layout changes significantly.
- Components with variants for buttons, cards, form fields and navigation, including hover, focus, active, disabled and error states.
- Variables and styles for colors, typography and spacing, applied consistently rather than as one-off values.
- Auto layout on frames, which shows developers how elements should stretch, wrap and space out.
- Notes on interactions such as menus, accordions, sliders and animations, and on any content that changes, like logged-in states.
Figma’s Dev Mode gives developers measurements, CSS values, variables and exportable assets directly from the file, and lets designers mark frames as ready for development. It’s the best place to hand off a design. Our guide to writing clear project notes for developers covers what to include alongside the file.
Step 2: Plan the content model
Before writing code, decide how each part of the design will be edited. This is the step that determines whether the site is easy to manage for years or fragile from day one.
- Identify repeating sections. A hero, a feature grid, a testimonial slider and a call-to-action band each become a reusable block or ACF layout.
- Identify structured content. Team members, case studies, locations or events usually become custom post types with their own fields and templates.
- Choose the editing approach. Native or custom blocks in the block editor, ACF Blocks, ACF Flexible Content, or a page builder such as Elementor. Our comparison of WordPress page builders explains the tradeoffs.
- Decide what editors can change. Editors usually need to change text, images and the order of sections, but not fonts, colors or spacing. Locking down design decisions keeps the site consistent.
Step 3: Turn design tokens into theme.json and CSS variables
Figma variables and styles map directly to code. Colors, font families, font sizes, spacing values and border radii become design tokens, defined once and used everywhere.
In a block or hybrid theme, those tokens go into theme.json. WordPress then outputs them as CSS custom properties and offers them as the only choices in the block editor:
{
"$schema": "https://schemas.wp.org/trunk/theme.json",
"version": 3,
"settings": {
"color": {
"custom": false,
"palette": [
{ "slug": "primary", "color": "#0b3d91", "name": "Primary" },
{ "slug": "ink", "color": "#1a1a1a", "name": "Ink" },
{ "slug": "surface", "color": "#f5f6f8", "name": "Surface" }
]
},
"typography": {
"fontSizes": [
{ "slug": "body", "size": "1.0625rem", "name": "Body" },
{ "slug": "h2", "size": "clamp(1.75rem, 1.4rem + 1.5vw, 2.5rem)", "name": "Heading 2" }
]
},
"spacing": {
"spacingSizes": [
{ "slug": "40", "size": "1rem", "name": "Small" },
{ "slug": "60", "size": "2rem", "name": "Medium" }
]
}
}
}
Theme CSS then uses the generated variables, such as var(--wp--preset--color--primary), so the code and the editor always agree. In a classic theme, the same tokens are defined as CSS custom properties on :root. Our guide to CSS variables covers the approach.
Step 4: Build components as blocks or ACF fields
Each component in the Figma file becomes a reusable piece of the theme. With ACF Blocks, for example, a card grid section is registered as a block with fields for a heading, an intro and a repeater of cards, and rendered by a PHP template that outputs clean, semantic markup. With native blocks, the same section might be a block pattern built from core blocks plus a small custom block.
The rule of thumb is to build each component once and reuse it, so a change to the card design updates every card on the site.
Step 5: Build every template responsively
A Figma file shows a few fixed widths. A real site has to work at every width in between, with content that’s longer or shorter than the placeholder text.
- Build mobile-first with CSS Grid and Flexbox, and use fluid sizing with
clamp()so type and spacing scale smoothly. - Use container queries for components that appear in both wide and narrow areas.
- Test with real content, including long headings, missing images and translated text, not just the design’s sample copy.
- Optimize images and fonts. Export images at appropriate sizes, serve WebP or AVIF, self-host fonts in WOFF2 and load only the weights the design uses.
Step 6: Build in accessibility
Accessibility is far cheaper to build in than to retrofit. During development, use semantic HTML and a logical heading order, make every interactive element work with a keyboard with a visible focus style, label form fields, write meaningful alt text and respect prefers-reduced-motion. Check color contrast against WCAG 2.2 AA. If the design uses a color pair that fails, raise it with the designer before launch rather than shipping it.
Step 7: Quality assurance against the design
Before the client sees the site, the build should be compared to the Figma file page by page, at each breakpoint, and tested across browsers and devices. A thorough quality assurance pass covers:
- Visual accuracy against the design, including spacing, typography and component states.
- Functional testing of navigation, forms, search and any custom features.
- Cross-browser testing in current Chrome, Safari, Firefox and Edge, and on real phones.
- Accessibility testing with a keyboard, an automated checker and a screen reader.
- Performance testing with Lighthouse or PageSpeed Insights.
- The editing experience: can an editor add, reorder and update each section without breaking the layout?
We describe our own approach in inside our quality assurance and testing process.

Step 8: Launch
Launch is where the site moves from staging to the live server. A careful launch includes a final backup, migrating content, setting up redirects from any old URLs, confirming SSL, analytics and form email delivery, turning on search engine indexing and checking the live site after DNS changes. Our WordPress launch checklist covers every step.
Frequently asked questions
How long does it take to convert a Figma design to WordPress?
It depends on the number of unique templates and components, the amount of custom functionality and how complete the design file is. A small marketing site moves much faster than a site with custom post types, integrations and complex interactions. A clear handoff file shortens the timeline more than anything else.
Should I use a page builder or a custom theme?
A custom theme with blocks or ACF gives the leanest code and the most consistent editing experience. A page builder such as Elementor gives editors more freedom to create new layouts themselves. Both can be built accurately from a Figma design. The right choice depends on who will edit the site and how.
Can I embed a Figma prototype in WordPress?
Yes. Figma’s share menu provides embed code you can paste into a Custom HTML block. That’s useful for design reviews or portfolios, but the embedded prototype isn’t a working website.
Have a Figma design ready to build? Our Figma to WordPress team develops custom themes with blocks, ACF or Elementor, and our WordPress development team handles the custom functionality behind them. Get a proposal.
Get started now
Start with a risk-free, no obligation proposal delivered to your inbox in one business day or less.
Get Started- 5-Star Rated Technical Partner
- 100% White-Label - Sign our NDA
- 90-Day Code Guarantee