Figma to WordPress: What Designers Should Send Before the Build Starts
Most delays in a Figma to WordPress build come from missing pieces, not hard code. This is the handoff list I send designers: mobile frames, a type scale, spacing rules, states, real content and exported assets.
Last month I got a Figma file with 14 good-looking desktop pages. No mobile frames. Three slightly different greys for body text. A heading font that wasn't on Google Fonts and came with no license. And a hero photo that, if you hid the gradient on top, still had a stock site watermark on it.
The design was good. The handoff wasn't. It cost the client about a week, because every one of those things turned into a question, a wait for an answer and then a revision.
I posted about this on X recently: Figma to WordPress isn't "just copy the design". Spacing, fonts and mobile layouts take most of the time. Not because they're hard to code, but because they're the parts designers tend to leave for the developer to guess. So this post is the list I now send to designers before I start. If you're a designer handing a file to any WordPress developer, it will save you both a lot of back and forth.
If you're a business owner and want to know how the whole project runs, start with my Figma to WordPress process and what it costs. This post is the designer's side of it.
1. Mobile Frames for Every Template
This is the big one. If I only get desktop, I end up designing the mobile version myself. I'll make sensible choices, but they're my choices, and the designer often doesn't like them once they see the site on their phone. Then we redo it.
You don't need a mobile frame for every single page. You need one for every template: home, a standard inner page, blog list, single post, shop, product, cart, checkout and contact. A 375px wide frame is enough. Tablet is nice to have, but I can usually work it out from desktop and mobile.
Show what happens to the menu, how cards stack and which images get hidden or cropped. And show the order. A row with text on the left and an image on the right: on mobile, does the image come first or second? It sounds small. It changes how the whole page reads.
2. A Type Scale, Not Random Sizes
When I inspect a file and find headings at 46, 47 and 48px, I know nobody decided on a scale. Pick a set: H1, H2, H3, H4, body and small text. Give each one a size, line height and weight for desktop and for mobile. Save them as Figma text styles so they show up by name when I inspect.
Then tell me where the fonts come from. Google Fonts is easy. For anything else I need the web font files (WOFF2) and a license that allows use on a website. "I'll send it later" usually means the site launches with a fallback font.
3. Spacing Rules
Use a spacing system, even a simple one like 4, 8, 16, 24, 32, 48, 64 and 96. Use auto layout so the gaps are real numbers I can read, not elements dragged into place by eye. When section padding is 87px on one page and 92px on another, I have to ask if that's on purpose. It almost never is.
Also tell me the container width and the grid. "1200px content, 24px gutters, 12 columns" is one line of text and saves me measuring every page.
4. Colors as Named Styles
Primary, secondary, text, muted text, border, background, success and error. Set them up as Figma color styles or variables. I turn these into CSS variables or theme.json settings, so if the brand color changes next year it's one edit instead of fifty.
5. States: Hover, Error, Empty
A static design shows everything on a good day. A real site has more going on:
- Hover and focus states for buttons and links.
- Form fields with an error message, and the message after a successful submit.
- An empty cart, a search with no results and a 404 page.
- A product on sale and a product that's out of stock.
- The mobile menu when it's open.
If these aren't in the file, I'll build something that fits the design. But a quick frame for each one is better than my guess.
6. Real Content, or Close to It
Lorem ipsum hides problems. A product title that's three words in the design is twelve words in the client's real catalog, and the card layout falls apart. Use real headlines, real product names and text of a realistic length where you can. If the client's copy isn't ready, design for the longest version you can imagine.
7. Exported Assets and Image Ratios
Mark icons and logos for export as SVG. Give me photos at full size, not screenshots of a frame. And tell me how images should crop: are product images square, 4:5, or whatever the client happens to upload? That one decision affects the whole shop.
Please avoid text baked into images. I can't edit it, search engines can't read it and it looks blurry on some screens. Text on top of an image should be real text.
8. Which Parts the Client Will Edit
Not strictly design, but the designer usually knows. Will the client change the homepage banner every month? Add team members? Update a pricing table? Mark those sections. I'll build them as editable blocks or fields. Everything else can be simpler, and simpler is faster.
9. Animations, If There Are Any
If something fades in, slides or moves on hover, show it with a Figma prototype or a short screen recording. A note that says "nice animation here" will get a different result from every developer who reads it.
The Short Version
If you only send three things, send these: mobile frames for each template, text and color styles, and spacing done with auto layout. That answers most of the questions I would otherwise have to ask.
Final Thoughts
A good handoff doesn't add much work for the designer. It makes sure the work they already did ends up on the live site the way they meant it. Every gap in a file gets filled by someone, and it's better when that someone is the person who designed it.
If you have a Figma design ready and want it built as a fast WordPress or WooCommerce site that your client can edit, have a look at my WordPress development services. Send me the file and I'll tell you what's missing before we start, so there are no surprises halfway through.