Skip to content

Figma to website guide

How Do I Turn a Figma Design into a WordPress Site?

Neither Figma nor WordPress has an official export. Hand-build a block theme, build in a page builder, or use a converter plugin that needs Auto Layout and exact layer names, then clean up the result.

Figment editorial teamPublished Updated

Publishing from Figma with Figment

The Figment plugin turns page frames in a Figma Design file into a hosted website.

Free planfigment.so address, Figment badge$0
Paid plansYour own domain, no badgeSee plans

Hosted publishing, not a code download.

There is no official "export to WordPress" button in Figma, and WordPress has no built-in Figma import. Three routes get a Figma design onto a WordPress site: hand-build a theme or page from the design, build it visually in a page builder, or use a Figma-to-WordPress converter plugin that generates blocks or widgets from your layers. Each trades speed for control, and each has a failure mode to know before you start.

Is there an official Figma-to-WordPress export?

No. Neither Figma nor WordPress publishes a first-party conversion between the two. What exists is a set of third-party plugins, on the Figma Community and on WordPress.org, that read a Figma file's structure and generate WordPress-compatible output. The other option is to build the page yourself with the design as a reference. None of it is a single click.

How do I hand-build a block theme or page from the design?

Build a block theme (or page) from your Figma values. Modern WordPress themes are block themes, built "entirely out of blocks," using the Site Editor to build templates for every part of the site, not just post content (WordPress Developer Resources, "What Is a Theme?"). "Both creators and users can edit the templates in the Site Editor" (same source), so once a template exists, ordinary editing happens in the block editor without code.

Read spacing, type and color from your Figma file as you would for any hand-coded page. Export images from Figma: select the layer, use the Export section, and choose PNG at 2x for photos and SVG for icons. Exporting Figma to HTML covers the asset export and the general hand-coding trade-off, which apply to a WordPress block template as much as a static page.

This route gives clean, maintainable markup and no dependency on a converter plugin's naming rules. It needs someone who can build a WordPress theme, and it is the slowest of the three.

How do I build it in a page builder?

Place sections, columns and elements by hand in a builder such as Elementor, using your Figma file as the visual reference. Visual page builders let you place widgets and containers without writing code. Elementor's documentation describes no built-in way to bring a Figma file in directly. It is the same placement work as the block theme route, inside the builder's editing model.

It needs less coding skill than a hand-built theme, but it is manual, section-by-section work, and it ties your content and layout to that page builder's data format.

Which Figma-to-WordPress converter plugins exist?

Three plugins are described below, each from its own Figma Community or WordPress.org listing. They are not ranked and we did not test them.

Figma To WordPress Block (by FigmaFy) converts a Figma design into code you paste into WordPress's default Gutenberg editor, and also supports Spectra and Kadence blocks. Its listing says it works "better for well grouped design," and gives naming tips: name a layer "button" to get a button block, group and lock image parts into one group to get an image block, and manually re-group anything that renders as a broken layout before converting again (Figma Community, "Figma To WordPress Block"). The same listing promotes a separate, manual, paid build service from the same team, Figmafy, for a fully custom result.

FigWP converts a Figma file into native Elementor widgets, using the separate Essential Addons for Elementor plugin. Its listing states prerequisites: use "Auto Layout" wherever possible, use a "Container" if a column layout breaks, make every section and inner section contain a "Column," and name frames or layers to match one of its supported Elementor widget names. More than 30 are listed, from Heading and Button to Pricing Table and Testimonial Slider (Figma Community, "FigWP - Figma to WordPress Converter").

UiChemy reads "frames, layers, Auto Layout, hierarchy" and converts them into your choice of output: native Elementor widgets (including Elementor's newer Atomic Elements, global classes and variables), Gutenberg blocks (core blocks plus Spectra, Kadence, GenerateBlocks or Nexter), or Bricks Builder elements. It states requirements of WordPress 6.9+ and PHP 7.4+, and runs on a paid-plan model with a 60-day money-back guarantee (WordPress.org, "UiChemy" plugin page).

All three read Auto Layout structure and layer names, and need your file organized their way. A design that is freely positioned, ungrouped or inconsistently named converts into something you spend as long fixing as building by hand, the same trade-off as Figma-to-code plugins in general.

What does each option cost me?

OptionSkill neededTypical timeWhat breaks itWhat you end up owning
Hand-built block themeWordPress theme developmentDaysNothing but your own build timeClean, maintainable block-theme code
Page builder, by handBasic WordPress plus the builder's UIHours to a day per pageNothing tool-specific, just manual effortContent locked into that page builder's format
Converter pluginFigma discipline: Auto Layout, grouping, exact namingMinutes to convert, then real cleanup timeUngrouped layers, missing Auto Layout, names that do not match the plugin's listOutput in the plugin's target format (Gutenberg, Elementor or Bricks)

What should I check before I commit to one?

  • Version requirements. UiChemy states a WordPress 6.9+ and PHP 7.4+ floor. Confirm your host meets it before you rely on a plugin.
  • What else you install. FigWP needs Essential Addons for Elementor. Several of these tools assume Elementor or a specific block library is in your stack, which is its own dependency to maintain.
  • Portable content. Gutenberg block output is closer to WordPress's native format. Page-builder widgets (Elementor, Bricks) are harder to move if you change builders.
  • A backup before you install anything. WordPress's guidance: "there are two parts to backing up your WordPress site: Database and Files. You need both to be able to fully restore a typical WordPress site" (WordPress Developer Resources, "Backups"). Do this before installing a converter or page-builder plugin, not after something breaks.

What about AI once the site is on WordPress?

That is a separate question from getting the design there. WordPress.com's AI Assistant and MCP support, or self-hosted routes like Application Passwords and WP-CLI, cover editing and drafting content on an existing WordPress site. Can ChatGPT or Claude Edit Your WordPress Site? covers what each can and cannot reach. None of it helps with the initial Figma-to-WordPress conversion.

When does publishing the Figma file directly make more sense?

If you do not need WordPress's CMS, plugin ecosystem or blogging tools, and you only need the design live as a portfolio, landing page or small business site, publishing directly skips all three routes. The Figment plugin does this for a Figma Design file: it publishes page frames as a hosted site rather than converting them to another platform's format. The Free plan uses a figment.so address with a badge, and Pro ($49/month, or $39/month billed yearly) adds up to 10 custom domains. It has no CMS and is not a blogging platform, so if you need either, use a WordPress route. See how to publish a Figma design.

What is the checklist before I convert?

  • Your Figma frames use Auto Layout throughout, if you use a converter plugin.
  • Layers are grouped and named to match your tool's requirements (or your own theme's structure, if hand-building).
  • You have confirmed WordPress and PHP version requirements for the plugin.
  • You have a full site backup, database and files, before installing anything new.
  • You tested the converted result on a draft or staging page, not the live site, and checked it on mobile.
  • You know which output format you end up with (block-theme HTML, Gutenberg blocks or a page builder's widgets) and whether you want to maintain it.

No route skips both the manual work and the plugin's naming rules. Choose by how much you value clean, portable code against the time you would rather spend converting and cleaning up.