THE SHORT ANSWER
Figma is a design tool and WordPress is a CMS, so most sites use both: design in Figma, build and host in WordPress. Figma Sites, Figma's website builder, competes with WordPress for simple pages like portfolios and campaigns, but it is still in beta, has basic SEO controls and no code export, so WordPress suits long-lived business sites.
People search "Figma vs WordPress" for two reasons. Some are trying to work out whether a design tool can replace a website platform. Others have seen Figma Sites and want to know if they still need WordPress at all. Both are fair questions, and the answer depends on which Figma product you mean and what the site has to do.
This guide separates the tools, compares Figma Sites and WordPress feature by feature using Figma's and WordPress's own documentation, and shows the workflow most agencies use: design in Figma, build in WordPress. It is written for agencies deciding what to recommend, and for site owners deciding what to buy.
01Figma, Figma Sites, Figma Make and WordPress are four different things
Most "Figma vs WordPress" arguments go wrong in the first sentence, because people use "Figma" to mean three different products. Before you compare anything, separate them.
| Tool | What it is | What it produces |
|---|---|---|
| Figma Design | A design and prototyping tool | Frames, components, styles and clickable prototypes. Not a live website. |
| Figma Sites | A website builder inside Figma, released in open beta at Config 2025 | A published site hosted by Figma, with a CMS for structured content |
| Figma Make | Figma's prompt-to-app tool | Generated apps and prototypes. Figma's own docs point to Payload as a CMS option for content-driven builds in Make. |
| WordPress | An open source content management system (CMS), built on PHP and MySQL or MariaDB, licensed GPLv2 or later | A full website you host anywhere, with users, roles, plugins, themes and a database |
So the real questions are two:
- Figma vs WordPress: a design tool against a CMS. They do different jobs, and most professional WordPress sites start life as a Figma file. You rarely choose one over the other. You choose how to get from one to the other.
- Figma Sites vs WordPress: two ways to put a site on the internet. Here they do compete, and the trade-offs are real.
The rest of this guide takes them in that order, then covers when to use both, how the handoff works, and how to move a Figma Site to WordPress when a client outgrows it.
Have a Figma design ready to build?
We turn Figma files into WordPress sites your clients can edit, under your brand.
02Figma vs WordPress: a design tool and a CMS do different jobs
Figma is where you decide how a site looks and behaves. WordPress is where the site lives, gets edited and gets found. A quick way to see the split is to list the jobs a client website has to do and check which tool does each one.
| Job | Figma Design | WordPress |
|---|---|---|
| Layout, typography, color, spacing | Yes, this is its core job | Yes, through a theme, theme.json or a page builder |
| Clickable prototype for client sign-off | Yes | Only by building the real thing |
| Real-time design collaboration and comments | Yes | Basic (block editor notes, staging reviews) |
| Serve pages to visitors on a domain | No (that needs Figma Sites) | Yes |
| Let a client edit posts, pages and media | No | Yes, with roles and permissions |
| Forms, bookings, memberships, store | No | Yes, through plugins |
| SEO titles, sitemaps, redirects, schema | No | Yes (core plus an SEO plugin) |
That is why the older articles that rank for this keyword say "Figma is not a WordPress alternative." They are right about Figma Design. What changed is that Figma now ships a builder, so the honest answer has to cover Figma Sites too.
Why people still compare them
Two reasons come up again and again with agency clients:
- The design already looks like a website. A polished Figma file with auto layout and real copy feels nearly done, so a client asks why the build costs more than the design. The answer is that the CMS, editing, responsive behavior, forms, SEO and hosting are the other half of the work.
- Designers want to publish without a developer. That is the exact gap Figma Sites is built for. It is a fair goal for some sites and a trap for others, which the next sections sort out.
03Figma Sites vs WordPress: feature by feature
This table uses Figma's own help center and WordPress.org as sources, checked in November 2026. Figma Sites is still labeled beta in Figma's help center, and Figma says beta features can change, so re-check anything that decides a project.
| Area | Figma Sites | WordPress (self-hosted) |
|---|---|---|
| Status | Open beta since Config 2025 | Mature open source project since 2003 |
| Who can publish | Paid plans (Professional, Education not K-12, Organization, Enterprise). Editing and publishing need a Full seat. | Anyone with hosting |
| Hosting | Figma only. Hosted on AWS in the United States, domain and routing served by Cloudflare. | Any host you choose, or WordPress.com |
| Code export | Not possible, per Figma's help center | You own every file and the database |
| Custom domains | Professional: 10. Organization and Enterprise: unlimited. One domain per site, no path-based domains. | Unlimited, set at your host and DNS |
| CMS | Sites CMS: collections, fields, items, CMS pages and CMS lists, CSV import | Posts, pages, custom post types, taxonomies, custom fields, revisions |
| Content editing by clients | Needs edit access to the file | Built-in roles (Administrator, Editor, Author, Contributor, Subscriber) |
| SEO controls | Page title, meta description, social image, language code, noindex toggle, favicon | All of those plus sitemaps (core), redirects, canonical control and schema through plugins |
| Custom code | Site-wide snippets at the start or end of head and body | Anything: theme files, plugins, hooks, the REST API |
| Analytics | Google Analytics only, site-wide | Any tool |
| Password protection | Yes, site-wide or per page, paid plans | Yes, per post or page in core, more with plugins |
| Forms, ecommerce, memberships | Not documented as native features | Plugins such as WooCommerce, form builders, membership tools |
| Extensions | Blocks and embeds, plus site-wide custom code | 78,000+ free plugins in the WordPress.org directory |
| Version history | Republish a previous version, or unpublish | Post revisions in core, full backups through your host or a plugin |
| License and ownership | Proprietary platform | GPLv2 or later, you can run, study, change and redistribute it |
Notice what is missing from Figma's documentation rather than what is there. As of this writing, the Figma Sites help center has no articles on redirects, custom 404 pages, sitemap settings, robots.txt, canonical tags or forms. That does not prove a feature is absent, but if a project depends on one of them, test it on a real published site before you promise it to a client.
Where Figma Sites is the better tool
- Speed from design to live. No handoff. The person who designed it can publish it the same day.
- Design fidelity. Auto layout, components and interactions carry over from Figma Design by copy and paste.
- No server to look after. Figma handles hosting and SSL certificates, so there are no plugin updates, PHP versions or backups to manage.
- Short-lived pages. Campaign pages, event pages, portfolio pieces and pitch microsites that will be gone in six months.
Where WordPress is the better tool
- Sites that earn money or leads for years. Ownership, portability and a full SEO toolset matter more the longer a site lives.
- Anything with real functionality. Stores, bookings, gated content, multilingual sites, CRM and email integrations.
- Content teams. Editorial roles, scheduled posts, revisions and a writing interface built for non-designers.
- Clients who might leave you. A WordPress site moves to another host or agency with a backup file. A Figma Site cannot be exported.
04The limits of Figma Sites that matter for client work
Reviews of Figma Sites tend to focus on how it feels to use. For an agency, the questions are different: what happens in year two, who owns the site, and what you will be asked to fix later. These are the points to raise before a client picks it.
1. No export means no exit
Figma's help center states plainly that it is not currently possible to export a site's code for external publishing. If the client later wants a store, a different host or a different agency, the site has to be rebuilt. Price that risk in, or tell the client about it in writing.
2. SEO controls are basic
You get titles, meta descriptions, social images, a language code and a per-page noindex toggle. That covers a landing page. It does not cover a site that needs redirect management after a restructure, schema markup for products or FAQs, fine control over canonicals, or a large blog with category archives. On WordPress, core generates an XML sitemap at /wp-sitemap.xml, and an SEO plugin adds the rest.
3. It is still a beta product
Figma labels Sites as beta and says beta features can change during the beta period. The custom domain article even said domains were free through 2025 with limits "subject to change after 2025." Building a client's main revenue site on a product whose terms can still change is a decision the client should make knowingly.
4. Content editing assumes a Figma user
The Sites CMS lets collaborators update text and images without moving the layout, which is a real step forward. But editing still happens inside a Figma file and needs edit access. Most small business clients already know the WordPress dashboard, or can learn it in an hour. Few of them want a Figma seat.
5. Functionality stops at the page
Forms, ecommerce, memberships, bookings and multilingual content are not documented as native features. You can embed third-party tools, but each one is another subscription and another login, and the data lives in a different place from the site.
6. Test the output yourself
Third-party reviewers have criticized the HTML that builders like this generate and the page speed of early Figma Sites. None of them published a repeatable test, so do not quote their claims to a client. Instead, publish your actual design and run three checks before you commit: Lighthouse or PageSpeed Insights on mobile, a screen reader or axe pass for headings, alt text and focus order, and a View Source check that each page has one clear h1.
05When to use Figma Sites, WordPress or both
Here is the decision table we use with agency partners. Read across by project type, not by which tool the designer prefers.
| Project | Best fit | Why |
|---|---|---|
| Designer portfolio | Figma Sites | Design fidelity matters most, low traffic stakes, the owner already lives in Figma |
| One-off campaign or event page | Figma Sites | Fast to publish, short lifespan, lock-in is not a concern |
| Startup pre-launch page | Either | Figma Sites to ship this week, WordPress if a blog and SEO are part of the plan |
| Small business brochure site | WordPress | The client edits it for years, needs forms, local SEO and a host they control |
| Content or blog-led site | WordPress | Editorial roles, scheduling, categories, sitemaps, redirects |
| Online store | WordPress with WooCommerce | Ecommerce is not a native Figma Sites feature |
| Multilingual site | WordPress | Figma Sites offers a language code per page, not a translation workflow |
| Membership, bookings, LMS | WordPress | Needs users, logins and plugins |
| Agency client site you maintain | Figma for design, WordPress for the build | You can sell care plans, move hosts and hand the site over cleanly |
The last row is the common answer for agencies: design in Figma, build in WordPress. You keep Figma's strengths (fast design, client sign-off on a prototype) and avoid its weak spots (lock-in, limited SEO, no plugins).
Five questions that settle it
- Will this site still exist in three years?
- Will someone outside the design team edit it every month?
- Does it need forms, payments, logins or more than one language?
- Does organic search bring, or need to bring, real leads?
- Would the client be upset to learn the site cannot be moved to another platform?
Two or more "yes" answers point to WordPress. All "no" answers point to Figma Sites, and that is a perfectly good choice for the right page.
06Using both: the Figma to WordPress handoff workflow
When you design in Figma and build in WordPress, most of the cost and most of the mistakes sit in the handoff. This is the workflow that keeps rebuilds cheap and close to the design. We cover the choice of build method (block theme, ACF or page builder) in more depth in Figma to WordPress: block theme, ACF or page builder?
Step 1: turn Figma styles into design tokens
Every color style, text style and spacing value in Figma should map to one named token in WordPress. In a block theme, those live in theme.json. The settings reference on developer.wordpress.org defines settings.color.palette, settings.typography.fontSizes, settings.spacing.spacingSizes and settings.layout for exactly this. A minimal version looks like this:
{
"$schema": "https://schemas.wp.org/trunk/theme.json",
"version": 3,
"settings": {
"color": {
"palette": [
{ "slug": "brand", "name": "Brand", "color": "#1F4FD8" },
{ "slug": "ink", "name": "Ink", "color": "#0F172A" },
{ "slug": "paper", "name": "Paper", "color": "#FFFFFF" }
]
},
"typography": {
"fontSizes": [
{ "slug": "body", "name": "Body", "size": "1.0625rem" },
{ "slug": "h2", "name": "H2", "size": "clamp(1.75rem, 3vw, 2.5rem)" }
]
},
"spacing": {
"spacingSizes": [
{ "slug": "s", "name": "Small", "size": "0.75rem" },
{ "slug": "m", "name": "Medium", "size": "1.5rem" },
{ "slug": "l", "name": "Large", "size": "3rem" }
]
},
"layout": { "contentSize": "720px", "wideSize": "1200px" }
}
}Use the same slugs as the Figma style names. When a designer changes "Brand" in Figma, the developer knows exactly which line to update. In Divi 5 or Elementor, the same idea applies through global colors, global fonts and design variables.
Step 2: map components to blocks, patterns or modules
List every Figma component and decide what it becomes: a core block, a block pattern, a custom block, an ACF block or a page builder module. Write the map down in a short table before anyone starts building. Components that repeat with different content (cards, testimonials, team members) usually become patterns or post types. One-off hero sections can stay as patterns.
Step 3: model the content before the pages
Figma shows pages. WordPress stores content. If the design has a case studies grid, a team page and a services list, decide whether each is a page, a custom post type or a set of custom fields. This step decides how easy the site is for the client to edit, so do it before styling.
Step 4: confirm the breakpoints
Ask for desktop and mobile frames at minimum, tablet if the layout changes there. Where a mobile frame is missing, agree in writing how sections stack. Fluid type, like the clamp() value in the example above, removes a lot of breakpoint guesswork.
Step 5: hand off with Dev Mode, not screenshots
Figma's Dev seat includes Dev Mode, which lets a developer inspect spacing, export assets and read values without edit access to the design. Name layers sensibly, mark frames as ready for development, and export images at the sizes the build needs. Tidy files cut build time more than any plugin.
Step 6: check the build against the design
Compare the staging site and the Figma frames side by side at each breakpoint. Check fonts, line heights, spacing, hover states and focus states, then run the same Lighthouse and accessibility checks you would run on any site. Fix the differences before the client sees it, not after.
07Moving a Figma Site to WordPress
Because Figma Sites has no code export, moving to WordPress is a rebuild, not an import. The good news is that the design file is already in Figma, so you skip the design phase. The steps:
- Crawl the live site. Run a crawler such as Screaming Frog on the published Figma Site and save every URL, title, meta description and h1. This is your redirect map and your SEO baseline.
- Export the CMS content. Collections were often built from a CSV import, so check whether the original CSV still exists. If not, copy the content out of the CMS view or the crawl.
- Rebuild on staging. Use the Figma file and the handoff workflow above. Keep the same URL slugs where you can.
- Map redirects. Any URL that changes needs a 301. A WordPress redirect plugin is easiest for clients to manage. On Apache hosts you can also add rules to
.htaccess:
# Old Figma Site URL to new WordPress URL
Redirect 301 /work /case-studies/
Redirect 301 /blog/launch-recap /news/launch-recap/- Switch DNS. The custom domain on a Figma Site points at Figma through a CNAME plus a TXT verification record. Remove or replace those and point the domain at the new host. Figma notes that Cloudflare-proxied domains must be set to DNS only for Figma, so if you move the domain back behind the Cloudflare proxy for WordPress, follow our Cloudflare for WordPress setup guide.
- Unpublish after the switch. Once the new site is live and the redirects test clean, unpublish the Figma Site so two copies are not competing in search. Submit the new sitemap in Google Search Console.
The same pattern (crawl, rebuild, redirect, switch) applies to any closed builder. If you have done a Squarespace to WordPress migration, the steps will look familiar.
08Cost and ownership over the life of a site
Price comparisons between these tools usually compare the wrong things. Figma is priced per seat. WordPress software is free, and you pay for hosting, premium plugins and the people who build and maintain it. Look at the whole life of the site.
| Cost | Figma Sites | WordPress |
|---|---|---|
| Software | A paid Figma plan with a Full seat for each person who edits or publishes | Free (GPL). WordPress.com is an optional hosted service with its own paid plans. |
| Hosting | Included with the plan | Paid separately, from budget shared hosting to managed hosting |
| Build | Low if the designer publishes it | A developer or white label partner turns the design into a theme or builder layout |
| Ongoing care | Little technical upkeep | Updates, backups and security, which agencies resell as care plans |
| Exit cost | A full rebuild | A backup and a DNS change |
Figma changes seat prices from time to time and shows different numbers by currency and billing period, so check figma.com/pricing on the day you quote.
What a Figma to WordPress build costs with us
Our Figma to WordPress service builds in Divi, Elementor or ACF, billed to your agency under your brand. Current prices from our pricing page:
| Scope | Turnaround | Price |
|---|---|---|
| Landing page, 1 page from Figma | 3 working days | From $400 |
| Brochure site, 3 to 5 pages | 5 to 7 working days | From $500 |
| Larger site, 6 to 10 pages | 7 to 10 working days | From $1,200 |
| Pilot page, 1 page up to 6 sections, one per agency | 3 working days | $199 |
After launch, white label care plans start at $25 a site per month, with your logo on the reports. That recurring line is the part of the WordPress model a Figma Site cannot give an agency.
09How to explain this to a client
Clients rarely care about the tool. They care about cost, control and whether the site will still work next year. A short script that works:
- "Figma is where we design it, WordPress is where it lives." This answers the "why is the build extra?" question without a lecture.
- "Figma Sites is great for a page that has a short life." Offer it honestly for campaigns and portfolios. It builds trust when you recommend the cheaper option where it fits.
- "You own a WordPress site outright." No export lock, any host, any agency. For a business site, this is usually the deciding point.
- "Here is what changes if you outgrow it." If a client picks Figma Sites anyway, put the rebuild path in the proposal so nobody is surprised later.
If your team designs well but does not want to run WordPress builds in-house, that is what white label WordPress development is for: you keep the client and the design, a partner does the build behind your brand.
10FAQ
Is Figma better than WordPress?
Neither is better in general because they do different jobs. Figma Design is a design and prototyping tool. WordPress is a CMS that hosts, edits and serves a website. Figma Sites is the part that competes with WordPress, and it suits short-lived pages and portfolios better than business sites that need SEO, forms or ecommerce.
Can Figma replace WordPress?
Figma Design cannot, because it does not publish websites. Figma Sites can replace WordPress for simple pages such as portfolios and campaign pages. It cannot replace WordPress for stores, membership sites, multilingual sites or sites a client needs to move to another host, since Figma does not allow code export.
Can I export a Figma Site to WordPress?
No. Figma's help center says it is not currently possible to export a site's code for external publishing. Moving a Figma Site to WordPress means rebuilding it from the Figma file, copying the content across, and setting up 301 redirects for any URLs that change.
Does Figma Sites have a CMS?
Yes. The Sites CMS uses collections, fields and items, with CMS pages as templates and CMS lists for repeating blocks. You can import a collection from a CSV. It is built for structured content like blog posts and case studies, but it is far simpler than WordPress, with no editorial roles or plugins.
Is Figma Sites good for SEO?
It covers the basics: page titles, meta descriptions, social images, a language code and a noindex toggle. Figma's help center does not document redirects, sitemap settings, robots.txt, canonical tags or schema. For a site that depends on organic search, WordPress with an SEO plugin gives you much more control.
How do I convert a Figma design to WordPress?
Map Figma styles to theme.json tokens or builder global styles, map components to blocks, patterns or modules, model the content as pages, post types and fields, confirm breakpoints, hand off through Dev Mode, then compare the staging build to the Figma frames at each breakpoint before launch.
Do I need a paid Figma plan to publish a site?
Yes. Figma lists publishing on paid plans (Professional, Education not K-12, Organization and Enterprise), and editing and publishing a site needs a Full seat. Custom domains are available on Professional (up to 10), Organization and Enterprise (unlimited).
Should agencies build client sites in Figma Sites?
For campaign pages and quick microsites, it can be a sensible option. For client sites you maintain, WordPress is usually the safer choice: the client owns the site, you can move hosts, add functionality with plugins, and sell ongoing care plans.
SOURCES
- Figma Help Center: Publish, update, or unpublish a site
- Figma Help Center: Manage a custom domain for your site
- Figma Help Center: Edit website settings
- Figma Help Center: Guide to Figma Sites CMS
- Figma Help Center: What Figma features are in beta
- WordPress.org: About WordPress
- WordPress Developer Resources: theme.json settings reference
- WordPress.org Plugin Directory



