The short answer
An in-house team converts Figma to WordPress by connecting one company site with a shared Connection Link, giving each designer a Figma seat, and pushing global styles plus the header and footer across first in Classic Mode. After that, each approved landing page converts in minutes, and marketers edit the live page without filing a design ticket.
What you need
- An approved Figma file that uses your team's named color, text and spacing styles, with the header and footer drawn as their own frames.
- A company WordPress site with admin access and Elementor, Gutenberg or Bricks active. Gutenberg ships with WordPress and Elementor is free. Only Bricks needs a paid license.
- The free UiChemy plugin from the WordPress.org directory on that site, and the UiChemy plugin open inside Figma.
- A plan with a Figma seat for each person who converts. The pricing page lists 1 seat on Free, 2 on Designer, 10 on Studio and unlimited on Agency, with early-bird offers of 4 on Designer and 20 on Studio for a limited time.
- A staging copy of the site for the first few runs. Staging and local sites connect the same way, with a Connection Link.
Step by step
Tidy the Figma file your team treats as the source
Most in-house teams already have a library. The question is whether the landing page frames actually use it. Swap stray hex values and one-off font sizes for the named styles, because Classic Mode pushes Figma colors, type and spacing into your builder's global styles. Clean styles become clean globals. Auto layout helps, but UiChemy says designs without it convert too.
Connect the company site once, then share the link
Generate one Connection Link in your UiChemy dashboard and paste it into the Figma plugin. UiChemy's own answer to "can my whole team use it" is to share that link, so every designer converts into the same site and draws from the same plan. Give each person who converts a Figma seat, and size the plan to that headcount rather than to the number of pages you ship.
Send the design system and the chrome across first
Run Classic Mode on a page that shows your styles, so colors, typography and spacing land in the builder's global settings before anything else. Then export the header and footer frames to theme builder templates. Every landing page after this inherits one header and one footer instead of carrying its own copy, which is what keeps a campaign page from drifting off brand three months later.
Pick a mode for each brief
Use AI Express Mode when speed matters more than exact control: it needs no layer tagging, adds motion, fixes spacing if you ask, and builds into Elementor today with Gutenberg and Bricks next. Use Classic Mode for brand-critical pages or when the site runs Gutenberg or Bricks. Both draw from one Credit balance, and Classic costs far fewer Credits, so a team with a weekly launch cadence can save AI Express for the pages that need it.
Convert the landing page and check every breakpoint
Pick the frame, choose a single page or the full site, choose motion (off, subtle or immersive) and let UiChemy build it as native, editable widgets. UiChemy says pages arrive 95% responsive, so plan a short pass in the responsive manager for tablet and mobile before you publish. A failed conversion doesn't spend Credits. If the page was built with AI Express, you can ask AI Chat for small fixes instead of opening every widget.
On this landing page, reduce the gap between the hero and the logo strip on mobile, make the three feature cards stack in one column below 768px, and do not change any text or colors.Give marketing the page, not the design file
Once a page is live, the marketer who owns it should be able to swap a headline or a hero image without a designer. Converted pages are ordinary builder content, so text, images and links are click-to-edit. For new sections between redesigns, UiChemy Composer runs alongside the builder you already use: Design Mode shows text, images, links, colors and spacing in plain fields, and AI Chat (on paid plans) builds a section from a description.
Add a section below the pricing table with a heading, a short paragraph and two buttons. Use the site's global colors and fonts, match the spacing of the section above, and keep the existing sections untouched.Set who can change what
The role manager in Composer controls what each WordPress role can edit. A sensible split for a company team: designers keep layout and global styles, marketers get content (copy, images, prices), and anyone outside the team gets nothing beyond view access. The pricing page lists the role manager on paid plans, not on Free.
Re-convert when the design changes
UiChemy reads a copy of the frame and never edits your Figma file, so a redesign is a new conversion rather than a rebuild by hand. Update the frame, convert again, and compare. If your next project starts from an AI build instead of Figma, the guide to editing AI code without coding covers that route.
What carries over and what does not
What you get
- One company WordPress site that every designer converts into, through a single shared Connection Link and one plan.
- Global colors, type and spacing from Figma sitting in the builder's global styles, so a brand color change is one edit.
- A header and footer living as theme builder templates, shared by every landing page.
- Landing pages built from native, editable widgets on hosting the company controls, with no export locked to UiChemy.
- Marketers editing copy, images and new sections themselves, with the role manager deciding how far they can reach.
What does not carry over
- AI Express Mode builds into Elementor only today. Gutenberg and Bricks teams use Classic Mode until AI Express reaches them.
- Global style sync is documented for Classic Mode. Don't expect AI Express alone to rebuild your style library in the builder.
- Seats cap who can convert. Five designers on the Designer plan means some of them wait or you move up a plan.
- Credits refresh monthly and unused Credits don't carry over. They're one balance shared across all four UiChemy products, so another team's AI Website Creator work can drain the pool you planned for landing pages.
- Composer AI Chat and the role manager are listed on paid plans. MCP and API access for Figma to WordPress is marked Soon on the pricing page.
- 95% responsive on arrival still leaves a breakpoint pass to do by hand on most pages.
Troubleshooting
The Figma plugin cannot reach the company site
Security plugins such as Wordfence and some managed hosts block the connection. UiChemy's docs list the one setting to allow it, and support can help. Test on staging first so IT isn't debugging production.
A teammate's page landed on the wrong site
Each Connection Link pairs with one site. Check which link that person pasted into the Figma plugin and replace it with the shared company link.
Brand colors show up as fixed values instead of globals
The page was probably converted in AI Express Mode, or the Figma layers used raw hex values instead of named styles. Fix the styles in Figma and run Classic Mode to sync them.
The Credit balance ran out before month end
Top up from your account, or switch routine pages to Classic Mode, which UiChemy says costs almost nothing. Check whether other products on the same plan are spending from the shared balance.
A marketer moved a section and broke the layout
Tighten their role in the role manager so they edit content only, and point them at Design Mode, which shows fields instead of code.
Every page has its own slightly different footer
The footer was converted as part of each page. Export it once as a theme builder template and remove the copies from individual pages.
Frequently asked questions
Can several designers convert into one WordPress site?
Yes. UiChemy says to share the Connection Link so your team converts into the same site, drawing from your shared plan. Each person who converts needs a Figma seat.
How many Figma seats do we get?
The pricing page lists 1 on Free, 2 on Designer, 10 on Studio and unlimited on Agency. For a limited time the early-bird offer raises Designer to 4 and Studio to 20.
Do our design tokens carry over?
Classic Mode pushes Figma colors, typography and spacing into the builder's global styles. That is the mode to use for the first run on a new site.
Does converting change the Figma file?
No. UiChemy reads a copy of the frame, so your library and file stay as they are, and you can re-convert after any update.
Can marketers edit pages without a designer?
Yes. Converted pages are native builder content. With Composer, marketers also get Design Mode for plain-field edits and AI Chat on paid plans, and the role manager limits what each role can touch.
Who owns the pages?
Your company. Everything lives on your own WordPress install as standard content. If you stop paying, published pages keep rendering because they're stored in your site, not served from UiChemy.
We also inherited an old site to replace. Is that a different route?
Yes. Rebuilding an existing site goes through AI to WordPress rather than Figma. See how to rebuild a site without starting over. Agencies running many client sites have their own guide: AI to WordPress for agencies.
Should we prototype in Figma Make or a vibe-coding tool instead?
It depends on who signs off. If your approvals happen in Figma, stay there. The Figma Make vs Lovable comparison covers the trade-off.