Skip to content

Odduel

We put the odds in your favour

Insights

Figma to WordPress: how a design becomes a website

How a Figma design becomes a WordPress website: preparing the file, the build steps, how long it takes, the common mistakes and how to keep the site easy to edit.

A designer and a developer seen from behind at a shared desk with printed page layouts and a laptop, handing over a website design

Figma to WordPress is the process of turning an approved Figma design into a working WordPress site: the design’s colours, type and components become a theme, its pages become editable blocks, and its interactions become tested code. Done well, the result looks exactly like the design and stays easy for your team to edit; done badly, it looks right on launch day and falls apart the first time someone adds a page. This guide explains the steps, how long they take, the common mistakes and what a small business should ask for.

Last updated: 11 November 2026.

What does “Figma to WordPress” mean in practice?

Figma to WordPress is the handover and build that converts a static design file into a content-managed website. Figma holds pictures of pages; WordPress needs rules: which fonts and sizes exist, how a card behaves at every width, what an editor may change and what stays fixed.

There are three broad ways to do it:

  • Hand-built block theme: the design system is written into a WordPress block theme, with its settings in `theme.json` and custom blocks or patterns where needed.
  • Page builder: the design is rebuilt inside a visual builder plugin, page by page.
  • Automated export: a plugin or service converts Figma frames into WordPress markup.

At Odduel, a creative and technology agency in Barcelona and São Paulo, we hand-build block themes in our website development service. The native block editor keeps pages light and lets clients edit content without touching the layout.

In short: prepare the Figma file as a system, not a set of pictures; agree what editors can change; translate tokens into the theme; build blocks and patterns; fill real content; test on real devices; then train the people who will edit the site.

Which approach should you choose?

Each route trades speed against control and long-term cost.

ApproachFidelity to designEditing for your teamSpeed and weightLong-term upkeep
Hand-built block themeExact, including motionSimple, guarded by patternsLight pages, fastLow, few plugins
Page builderClose, with compromisesFlexible but easy to breakHeavier markupTied to the builder plugin
Automated exportVaries, often rigidLimited or awkwardOften heavyHard to change later
Three ways to turn a Figma design into a WordPress site.

A page builder can suit a team that wants to redesign pages itself often. For a brand site where consistency matters, a block theme is usually the better investment. Our guide on how to choose a CMS helps if WordPress itself is still an open question.

What are the steps in Figma to WordPress?

Here is the sequence we follow, from file to launch.

  1. Audit the Figma file. Check that every page exists at desktop and mobile widths, that components and variants are used consistently, and that colours and text styles are defined as styles or variables rather than one-off values.
  2. Agree the content model. Decide which parts are pages, which are posts or custom types (projects, team, vacancies), and which fields each needs.
  3. Agree the editing rules. List what editors can change freely, what they can choose from (patterns), and what is locked.
  4. Translate design tokens. Colours, font families, sizes, spacing and widths go into `theme.json`, so the editor offers only the brand’s options. The WordPress global settings and styles documentation describes this file.
  5. Build templates and parts. Header, footer, page, post, archive and 404 templates come first, then the specific templates.
  6. Build blocks and patterns. Repeated sections of the design become patterns; anything with real behaviour (sliders, filters, forms) becomes a custom block or a small script.
  7. Add real content. Placeholder text hides problems; real headlines, long names and real pictures reveal them.
  8. Test. Check every page at many widths, in several browsers, with the keyboard, with a screen reader and on slow connections.
  9. Launch and train. Move to the live server, set redirects if replacing an old site, and show editors how to work with the patterns.

How should the Figma file be prepared?

The single biggest factor in a smooth build is a design file prepared as a system. Ask your designer for:

  • Named styles or variables for every colour, text size and spacing step.
  • Components with variants for buttons, cards, form fields and navigation, including hover, focus, error and disabled states.
  • Mobile and desktop frames for every template, plus at least one in-between width for complex layouts.
  • Real content lengths: the longest headline, a long product name, an empty state.
  • Interactions described: what moves, how fast and what happens with reduced motion.
  • Assets ready: icons as SVG, pictures at full resolution, fonts with a web licence.

A file built this way can be checked against the site screen by screen. A file of loose frames leaves the developer guessing, and guesses are where design and site drift apart.

The Nothing To Eat website by Odduel on a laptop, a WordPress block theme built from an approved design

How long does Figma to WordPress usually take?

The build time depends on the number of templates, the number of unique sections, interactions, integrations and languages, more than on the number of pages. A site with five templates and fifty pages can be quicker than one with fifteen unique layouts and ten pages.

Rough proportions hold for most projects: setting up the theme and tokens is a small share; building templates, patterns and interactions is the largest share; content entry and testing together take a meaningful slice that is often underestimated. Our guide on how long it takes to build a website walks through the phases, and a clear website brief shortens every one of them.

What are the most common mistakes?

These are the problems we see most often when rescuing Figma to WordPress builds:

  • Designing only for desktop. The developer invents the mobile layout, and it shows.
  • One-off values everywhere. Twenty shades of grey in the design become twenty in the code.
  • No states. Focus, error and empty states are missing, so they are improvised or forgotten.
  • Too much freedom for editors. If any block can take any colour and size, the site drifts away from the brand within months.
  • Plugin pile-up. Each feature added through a separate plugin adds weight, risk and updates.
  • Ignoring accessibility. Contrast, headings, alternative text and keyboard use must be designed and built in, in line with WCAG 2.2.
  • Fonts without a web licence. A desktop licence used in Figma does not cover a website.
  • No content plan. The site launches with placeholder text in corners nobody checked.

What are the best practices for a lasting build?

A few habits make the difference between a site that holds up and one that needs a rebuild in two years:

  1. One source of truth for tokens. Keep Figma variables and `theme.json` in step, and change both together.
  2. Patterns over free layouts. Give editors well-designed building blocks rather than a blank canvas.
  3. Few, trusted plugins. Prefer theme code for small features and established plugins for SEO and forms.
  4. Performance from the start. Modern image formats, explicit image sizes, self-hosted fonts and minimal scripts.
  5. Version control. Keep the theme in a repository and deploy from it, never by editing files on the server.
  6. Document the system so the next developer, or your own team, can extend it safely.

Is Figma to WordPress right for a small business?

For a small business, the advantages are real: a site that matches the brand exactly, that the team can update without a developer, and that costs little to run. The key is to keep the scope honest. Start with the templates you need now, build them well, and add more later. A smaller, well-built site beats a large one held together with plugins.

If your budget is tight, prioritise a strong home page, service or product pages, a contact page and a clean blog template. Every one of them should work perfectly on a phone.

Questions people ask

Can Figma export directly to WordPress?

Some plugins and services convert Figma frames into WordPress pages, but the result is usually rigid, heavy and hard for editors to change. Figma describes how a page looks; a WordPress site also needs rules for content, editing and behaviour. A developer translating the design into a theme gives a cleaner, more durable site.

Do I need a page builder to turn Figma into WordPress?

No. The native block editor and a custom block theme can reproduce a Figma design exactly, with lighter pages and fewer dependencies. Page builders suit teams that want to redesign layouts themselves often, but they add weight and tie the site to one plugin for as long as it exists.

How long does Figma to WordPress usually take?

It depends on the number of unique templates, interactions, integrations and languages rather than the number of pages. A small site with a handful of templates takes weeks; a large site with many custom sections, integrations and languages takes longer. A prepared Figma file and a clear brief shorten every phase.

What should a designer deliver to the developer?

Named colour, type and spacing styles; components with all their states; mobile and desktop frames for every template; real content lengths; notes on interactions and motion; icons as SVG, full-resolution pictures and fonts with a web licence. A file organised as a system can be checked against the finished site screen by screen.

Will my team be able to edit the site afterwards?

Yes, if the build is planned for it. Patterns give editors approved sections to add and rearrange, while locked templates protect the layout and brand. A short training session and a written guide cover adding pages, posts and pictures without breaking the design or calling a developer.

Open your Figma file and check it against the preparation list above: it is the quickest way to see how ready the design is for a build. If you want a design turned into a fast, editable WordPress site, see our website development service or send us your file and brief.

More articles

More from our Insights.

Explore all insights

Get in touch

Let’s change your odds.

Odds do not change on their own. If you have something to build, launch or fix, tell us about it and we will show you how we would approach it.

    Need an NDA before you share details? Start a project

    Chat with us