Figma to WordPress service
We build a WordPress site from your Figma design. You get a theme made to the file, with each page layout in it set up as a WordPress page you can edit. For site owners and designers who have a finished design and need it built. A build, not a move, quoted after we have seen the file.
In short
- A WordPress theme built from your Figma file, with its page layouts made as pages you can edit.
- Built to the design at the screen sizes the file shows. Sizes it does not show are worked out with you.
- A fixed quote in writing that lists the layouts, after we have seen the file.
- Built on a staging copy that you look at before it goes live.
- We build the design. We do not design it.
- If the design replaces a live site, moving that site's content and redirecting its addresses is a second job.
A Figma file shows what a site should look like. Each screen is a frame: a container, drawn at a set size, that holds the text, shapes and images of one layout. A WordPress theme is what makes a real site look that way. In WordPress's own words, a theme "can control everything from colors, to fonts, to the entire layout".
This service turns the first into the second. It is a build, not a move. There is no live content to carry across and no old site to copy, only a design to be made into a working WordPress site.
It is for the point where the design is finished and agreed, and you need it built.
Who it is for, and who it is not
It fits when all of these are true:
- the design is finished, and whoever has to approve it has approved it
- it is in a Figma file you can share
- you have, or can get, the words, the images and the fonts the design uses
- you want pages you can edit yourself afterwards, in the WordPress editor
A different page fits better in these cases.
- There is no design yet, or it is still changing. We build what the file shows. For the designing, see WordPress design and development.
- The design only restyles a WordPress theme you already run: its colors, its type, its spacing. A child theme holds your changes to a theme, so the parent can be updated without losing them. How to create a WordPress child theme shows how, and it may be all the build you need.
- The design replaces a live site on another platform. The build is only half of that. Carrying the old site's content across and redirecting its addresses is a platform migration, quoted in writing as well. Say so in the assessment.
- The design shows a store, a booking calendar or a form that has to work. A design shows what a feature looks like, not how it works. The quote says whether each is included or is a separate job of custom development.
- You only want changes to a site you have. New text, a replaced image or a menu item are website edits.
What you get
- A WordPress theme built from your design. The theme controls how the site looks. Your text and images are stored by WordPress, apart from the theme.
- Each page layout in the file, made as a WordPress page you can edit. You change the words and pictures in the WordPress editor. The quote lists the layouts by name.
- The design at the screen sizes the file shows. If the file holds a desktop frame and a phone frame for a layout, both are built as drawn. A file does not show every width a screen can be. Sizes it does not show are worked out with you.
- A staging copy to look at. The site is built on a staging copy, and you go through it there before it goes live.
- A fixed quote in writing before any work starts.
What we need from you to start
The request goes through the free migration assessment form. It asks for your name and an email address for the reply. Under "Where is the site now?
- The Figma file, with view access. Use "Share" in the file to invite us or to copy a link. View access is enough. Figma lets anyone with view access export assets, unless the file's owner has restricted copying and sharing, so leave that restriction off or send the assets yourself.
- The fonts, and their licenses. Figma includes Google fonts and Apple fonts in a file by default. A font installed on the designer's own computer is not there for anyone else who opens the file. Tell us which fonts the design uses, and check that your license for each one allows use on a website.
- The images at full size. Figma exports assets as PNG, JPG, SVG or PDF, which suits logos and icons. Send photographs as their original files, not as they sit in the design, so that each can be prepared at the size its layout needs.
- The text. Send the final words for each page, or tell us that the sample text in the file is final.
- Which layouts are in scope. Name the frames you want built. A file can hold drafts and alternatives beside the agreed design.
How it works
Step 1: Ask for a free assessment
Fill in the free migration assessment. Say that it is a build from a Figma design, and share the file.
Step 2: Get a fixed quote that lists the layouts
We look at the file and reply in writing with a fixed quote that lists the layouts to be built. Whether to go ahead is up to you.
Step 3: The site is built on a staging copy
The theme and the pages are built on a staging copy.
Step 4: You look at it
You go through each page on staging, at each screen size, and say what does not match.
Step 5: It goes live
The site goes live after you have looked at it.
What it does not cover
- The design itself. We build what the file shows. We do not design it, and a layout that is not in the file is not in the build. For design work, see WordPress design and development.
- Hosting. You buy the hosting plan and the domain. The site is built to go onto it.
- Writing the content. The words and pictures are yours to supply.
- Looking after the site afterwards. Updates, backups and monitoring from then on are a care plan. See the WordPress maintenance service.
- Moving an existing site. If the design replaces a live site on another platform, carrying its content across and redirecting its addresses is a platform migration, quoted in writing as well.
Before you ask: do it yourself, or check first
Count the frames first. The quote lists the layouts to be built, so open the file and name the frames you want, leaving out drafts and alternatives. Add a phone frame for each layout you want built to a set phone design.
Each of these is free to use.
- How to create a WordPress child theme. The do-it-yourself route when the design only restyles the theme you run.
- WordPress launch checklist. What to check in the days before a new or rebuilt site opens: content, settings, accounts, forms and email, and search.
- How to set up a WordPress staging site. What a staging copy is, if the word is new to you.
If the design replaces a live site, its old addresses matter as much as the new pages.
- How to migrate a website without losing SEO. What Google and Bing document about a move, and why each old address gets a redirect of its own.
- Website migration checklist. The order of work before, during and after the switch.
- WordPress migration cost. Which job a quote is for, what moves the price of a change of platform, and what a quote should say.
- Redirect map builder and redirect checker. The first turns a list of old and new addresses into redirect rules. The second shows where an old address leads now.
- Platform detector. Reads what the present site is built with, from outside.
- Moving a WordPress site or changing platform. Every page we have on the subject, in one place.
What it costs
Figma to WordPress build
Ask us for a quote
A WordPress site built from your Figma design.
- A written quote before any work starts
- Built on a staging copy you can look at before it goes live
Common questions
What will it cost?
It is quoted in writing, after we have seen the file and know how many page layouts it holds. The quote is fixed, it lists the layouts by name, and you have it before any work starts. The assessment is free, and you owe nothing after it.
How long will it take?
This page gives no time, because that depends on how many layouts the file holds and on what each has to do. Say in the assessment when you would like the site live.
What if I do not have a design yet?
Then this is not the service for you yet. We build what a file shows and do not design it. WordPress design and development is for pages that still have to be designed.
Do you need edit access to my Figma file?
No. View access is enough, as long as copying and sharing have not been restricted for the file. Nothing in your file is changed.
My file only shows the desktop design. What happens on a phone?
The desktop layout is built as drawn. How each layout rearranges on a narrower screen is not in the file, so it is worked out with you: you see it on staging and say what should change. If you want set phone layouts, add those frames to the file before you ask for the quote.
Will the built site match the design?
It is built to the design at the screen sizes the file shows. A browser is not a drawing tool: real text is longer or shorter than sample text, and screens come in every width between the ones drawn. You compare the two on staging before the site goes live.
Can I edit the pages myself afterwards?
Yes. Each layout in the quote is made as a WordPress page, and you change its text and images in the WordPress editor.
The design includes a store or a booking form. Is that part of it?
A design shows what a feature looks like, not how it works. A form, a store or a calendar drawn in the file needs a plugin or code behind it. Say what each one should do when you ask for the assessment, and the quote says whether it is included or is a separate job of custom development.

