Figma to WordPress Block Theme: A Step-by-Step Guide to Full Site Editing

To turn a Figma design into a WordPress block theme, you map the design's colors, type and spacing into theme.json, build templates and template parts in the Site Editor, turn repeated sections into block patterns, and lock what editors should not change. The result is a lean WordPress site with full site editing, without a heavy page builder.

Key takeaways

  • A block theme stores your design system in one file, theme.json, so the whole site stays consistent.
  • Repeated Figma sections become block patterns that editors insert and fill in.
  • Block themes are usually lighter than page builder sites, which helps speed and Core Web Vitals.
  • Page builders like Elementor still make sense when your team already knows them or needs drag-and-drop layout changes daily.

What is a WordPress block theme?

A block theme is a WordPress theme built entirely from blocks. Instead of PHP template files full of markup, it uses HTML templates made of blocks, a theme.json file for global settings and styles, and patterns for reusable sections. Everything, including the header, footer and archive pages, can be edited in the Site Editor. This is what WordPress calls full site editing.

For a business, that means one editor (Gutenberg) for everything, fewer plugins, and a design system that cannot drift as easily as a pile of custom page builder layouts.

Block theme vs page builder: which should you choose?

FactorBlock themePage builder (for example Elementor)
Page weightLean, mostly core blocksHeavier, extra scripts and styles
Design consistencyEnforced by theme.json and patternsDepends on discipline
Editor learning curveGutenberg, built into WordPressSeparate builder interface
Free-form layout changesPossible, but patterns guide editorsVery flexible
Dependency on a third partyLowTied to the builder plugin

Neither is wrong. We compare both in more depth in Figma to WordPress: Gutenberg vs Elementor. If your marketing team lives in Elementor and is productive there, switching just for purity rarely pays off.

Step by step: Figma to WordPress block theme

Step 1: Audit the Figma file

Before any code, list what the design actually contains: color styles, text styles, spacing scale, components and every page template. Check for mobile frames and hover states. Missing pieces are easier to settle now than halfway through the build. Our guide on preparing a Figma file for developer handoff lists what to check.

Step 2: Translate design tokens into theme.json

theme.json is where your Figma styles live in WordPress. Add your brand colors to the palette, your font families and sizes to typography, and your spacing steps to the spacing scale. Set content and wide widths to match the Figma grid. Turn off what you do not need, such as custom colors, so editors pick from the brand palette instead of guessing hex codes.

Step 3: Set up the theme files

A minimal block theme needs a style.css with the theme header, theme.json, and a templates folder with at least an index.html. Most sites also need a parts folder for the header and footer, and a patterns folder for sections. The free Create Block Theme plugin from the WordPress team can generate this skeleton and export changes you make in the Site Editor back into files.

Step 4: Build template parts and templates

Build the header and footer as template parts first, since every page uses them. Then build templates for the front page, single pages, single posts, the blog archive and the 404 page. Use core blocks such as Group, Columns, Cover, Query Loop and Navigation wherever they can do the job.

Step 5: Turn repeated sections into patterns

Every section that appears more than once in Figma, like a hero, a feature grid, a testimonial row or a call to action band, becomes a block pattern. Patterns in the patterns folder register automatically. Use synced patterns for content that must stay identical everywhere, like a contact strip.

Step 6: Lock what editors should not break

Block locking lets you stop editors from moving or deleting key blocks. Content-only locking on a pattern lets someone change the text and images while the layout stays put. This is how you keep the design faithful to Figma months after launch.

Step 7: Check responsiveness against the design

Compare each page side by side with the Figma frames at phone, tablet and desktop widths. Use fluid type and spacing in theme.json so sizes scale smoothly. Add small custom CSS only where core blocks cannot match the design.

Step 8: Set up SEO and performance before launch

  1. Install an SEO plugin such as Rank Math or Yoast, and set titles and meta descriptions.
  2. Check the heading order on each template: one h1, then logical h2s and h3s.
  3. Compress images and serve modern formats like WebP.
  4. Add caching, and avoid loading scripts on pages that do not use them.
  5. Submit the XML sitemap in Google Search Console.

If you want this done for you, our Basic SEO Setup covers Search Console, the sitemap, on-page optimization and local schema.

Step 9: Hand over with a short guide

Show editors how to add a page from patterns, update the menu and publish posts. A five-minute screen recording saves weeks of support questions.

Common mistakes when converting Figma to a block theme

  • Hard-coding colors and sizes in blocks instead of using theme.json presets, which breaks consistency.
  • Building every page by hand instead of with patterns, so the next new page looks slightly different.
  • Adding a page builder on top of a block theme, which gives you the weight of both.
  • Skipping mobile frames and guessing breakpoints at the end.
  • Loading too many fonts from the design. Limit families and weights to what the site really uses, and host them locally where you can.

Most of these come from rushing the first two steps. Time spent turning Figma styles into clean theme.json presets pays back on every page that follows.

How RizeHub builds Figma to WordPress sites

RizeHub is a web development agency in the Philippines led by a founder with 9+ years in web development across WordPress, Webflow and Shopify. Our Figma to WordPress service builds with native Gutenberg blocks or Elementor, whichever your team prefers, and landing pages or smaller sites go live in 24 hours from file approval. You get a fixed quote within the hour, you own the site and its accounts, and there are 30 days of free fixes after launch.

Frequently asked questions

Is a block theme faster than Elementor?

Usually, yes. A block theme relies mostly on core blocks and loads fewer extra scripts and styles. A carefully built Elementor site can still be fast, but it starts from a heavier base.

Can my team edit a block theme without code?

Yes. Editors add pages from patterns, change text and images, and edit menus in the Site Editor. Locked patterns stop them from accidentally breaking the layout.

Do I need a child theme for a custom block theme?

Not if the theme is built for you from scratch. A child theme is mainly useful when you customize someone else's theme and want to keep its updates.

How long does a Figma to WordPress block theme take?

A landing page or small site can be done in about a day once the design and scope are locked. Larger sites with many templates, custom post types or WooCommerce get a timeline in the quote.

Ready to build your design in WordPress?

A block theme gives you a fast, consistent WordPress site that stays close to your Figma design long after launch. If you have a file ready, send us the link and we will reply with a fixed quote and a plan.