Design to WordPress conversion is the process of building a working, editable WordPress theme directly from a finished Figma, Adobe XD, Sketch or PSD design file — matching it pixel-for-pixel rather than approximating it with a stock theme or page builder. The resulting site is a real, editable WordPress installation with the block editor and ACF custom fields for content management, not a static HTML export. I review every screen and responsive state in the design file, flag any ambiguities before build starts, and deliver on a fixed price scoped from your design complexity.
Who it's for
What's included
How the process works
Design review
I go through every screen, component and state in your Figma, XD or PSD file and log a questions document covering ambiguous interactions, missing responsive states, and undefined hover behaviours — resolved before a line of code is written.
Build on staging
Theme built on a staging URL and compared side-by-side against the design file at every viewport width — pixel-level differences caught and corrected during build, not in review.
Review & revise
You compare the staging site directly against your design file. I fix any pixel-level mismatches, spacing discrepancies or interaction gaps in a single revision round.
Launch
Go live once the built site matches the design, passes Core Web Vitals, and clears cross-browser testing. Post-launch support available via care plan.
Common questions
Figma is the most common and gives the cleanest handoff — I can inspect spacing, type styles, component variants and exported assets directly from a shared Figma file without needing an export. Adobe XD, Sketch (with an inspect link or exported assets), and Photoshop PSD files all work. If your PSD is an older layered file without named components, I'll need a bit more time on the design review phase to map the intended structure. The most important thing is that the design is finalised — mid-build design changes are quoted separately.
It's a real, fully editable WordPress installation — not a static HTML export. Content, images, repeating sections and page layouts are editable via the WordPress block editor and ACF custom fields. Your team can update text, swap images, reorder sections and add new pages from the WordPress admin without developer assistance. If you need more editorial flexibility beyond what ACF custom fields offer, I can integrate the Gutenberg block editor with custom block patterns so editors can build new page layouts from reusable design components.
I flag any missing breakpoints or responsive states in the design review phase — before build begins. For missing mobile layouts, I propose responsive behaviour based on the desktop design intent (reflow order, touch target sizing, font scaling) and document the proposed behaviour for your approval. For designs that have mobile but no tablet, I interpolate between the two. I never guess silently — any assumption I make about underdefined responsive behaviour is explicitly called out and approved before I build it.
Design to WordPress conversion starts from a finished design file — your designer has already made all the visual decisions, and my job is to build it accurately. Custom theme development is broader: I work from a brief or a rough direction (mood board, reference sites, brand guidelines) and make the design decisions as part of the build. If you have a finished Figma or XD file with all screens designed, choose design-to-WordPress conversion. If you're starting from a brand guide and descriptions rather than a pixel-ready design file, custom theme development is the right service — I'll build both the design and the WordPress implementation.
Yes. Many design-to-WordPress conversions include a WooCommerce store, membership area, booking flow, or custom forms alongside the marketing site. I scope the design-to-WordPress build (theme and templates) and any functional requirements (WooCommerce setup, API integrations, custom post types) together in a single fixed-price quote. The design conversion and functionality build are done in parallel on staging so the final site reflects both the design's visual accuracy and the functional requirements, without a separate handoff between a 'design build' phase and a 'features' phase.