Webflow designer or Webflow developer: who do you need?.
What Webflow designers and Webflow developers each do, where the skills overlap, and when a project needs both.
Search for help with a Webflow site and you will find people calling themselves Webflow designers, Webflow developers and sometimes both. The titles overlap because Webflow itself blurs the line: its main building tool is even called the Designer. So who do you actually need? It depends on whether your project is mostly about how the site looks, how it works, or both. This guide sets out what each role usually covers, where they overlap and when it makes sense to bring in both.
Why the roles blur in Webflow
On many platforms, design and development are separate stages done in different tools. A designer works in Figma, then a developer writes the code. Webflow lets people build production websites visually, so a designer can create the real site rather than a mock-up. That is one of Webflow's main appeals, and it is why some people describe themselves as Webflow designers even though they are building and publishing live sites.
The result is a spectrum rather than two boxes. At one end is someone who is mainly a visual designer and uses Webflow to build what they design. At the other is someone with a development background who builds from other people's designs and adds code, integrations and technical structure. Many people sit somewhere in between.
What a Webflow designer usually does
- Works out the visual direction: layout, typography, colour, imagery and brand expression.
- Designs pages in Figma, or directly in Webflow.
- Thinks about user journeys, content hierarchy and calls to action.
- Builds marketing pages and landing pages in Webflow using its visual tools.
- Adds interactions and animations that support the design.
A strong Webflow designer understands the platform's constraints, so their designs are realistic to build and maintain. You can see the kind of work this covers on our Webflow web design section.
What a Webflow developer usually does
- Turns designs into a clean, consistent build with a clear class naming system.
- Plans and builds CMS collections, references and template pages.
- Builds reusable components with properties editors can change.
- Writes custom code where Webflow does not cover a need: embeds, scripts, structured data or code-based components.
- Connects the site to other systems: CRMs, form tools, booking systems, analytics or automation platforms.
- Works with Webflow's APIs for data syncs or custom apps.
- Handles performance, accessibility, SEO settings, redirects and migrations.
The more your site depends on data, other systems or custom behaviour, the more you need these skills.
Webflow designer vs Webflow developer at a glance
| Area | Webflow designer | Webflow developer |
|---|---|---|
| Visual design and brand | Main focus | Usually works from an existing design |
| Building pages in Webflow | Often, especially marketing pages | Yes, with emphasis on structure and reuse |
| CMS planning | Simple collections | Complex structures, references, scale |
| Interactions | Designs and builds them | Builds them with performance in mind |
| Custom code | Occasionally, small embeds | Regularly, including JavaScript and APIs |
| Integrations | Basic form connections | CRMs, automation tools, custom data syncs |
| Accessibility and performance | Colour, contrast, readable layouts | Semantic structure, keyboard support, page speed |
| Migrations and redirects | Rarely | Commonly |
This is a general picture. Individuals vary, so ask about the specific skills your project needs rather than relying on a job title.
Where custom code comes in
Webflow covers a lot without code, but most business sites eventually need something extra. Common examples include:
- adding structured data (schema markup) to pages or CMS templates
- embedding third-party tools such as booking widgets, chat or calculators
- filtering, sorting or searching CMS content beyond what Webflow offers natively
- conditional logic in forms
- bringing in data from an external system through Webflow's APIs
- custom tracking for analytics and advertising
Custom code needs care. It can slow pages, conflict with other scripts or break when Webflow changes. A developer should keep it organised, document what each snippet does, and load scripts only where they are needed. Our Webflow custom code work covers this side of the platform. If you are looking at building on Webflow's APIs, the Webflow developer documentation is the official reference.
Integrations
Sending form submissions to a CRM, syncing products from another system, adding visitors to an email list or triggering a notification when someone books a call are all integration work. Some of this can be done with native Webflow features or an automation platform, and some needs custom code or a small server-side service. A developer can tell you which approach suits each case and what the trade-offs are for reliability and upkeep. See our Webflow integrations section for the kinds of connections involved.
When you need a Webflow designer
- You are launching a new brand or refreshing an existing one.
- Your current site looks dated or inconsistent and the structure is otherwise fine.
- You need landing pages designed and built quickly for campaigns.
- Your content is fairly simple: a handful of pages and a blog.
When you need a Webflow developer
- You already have a finished design, from an in-house team or another designer.
- Your site has several connected CMS collections or a large volume of content.
- You need integrations with a CRM, booking system or other tools.
- You are migrating from another platform and need content moved and redirects mapped.
- Your site has performance, accessibility or SEO problems to fix.
When you need both
Many projects benefit from both roles: a redesign that also restructures the CMS, a site that needs a strong visual identity and several integrations, or a larger site where the design system and the build both need careful thought. In these cases, the two roles work best when they talk early. The developer reviews designs for buildability and CMS fit, and the designer reviews the build against the intended look and behaviour.
Sometimes one person genuinely covers both. Ask to see examples of their design work and the inside of a build, using a read-only link, so you can judge both sides.
How to decide: a short checklist
- 1 List what the site needs to do, not just how it should look.
- 2 Mark whether you already have a finished design.
- 3 List any repeating content that will need the CMS.
- 4 List every system the site must connect to.
- 5 Note any custom features, such as calculators, filters or gated content.
- 6 If most items are about appearance, start with a designer.
- 7 If most items are about content, data and connections, start with a developer.
- 8 If both lists are long, look for a team or a pairing that covers both.
Writing this down also gives you the start of a brief. Our guides on writing a website brief and choosing between Shopify, WordPress or Webflow can help if you are still at an early stage.
Web Canvas offers UI/UX and brand design alongside Webflow development, so we can cover either side or both. If you are not sure which you need, get in touch and we can talk it through.
Planning something similar?
Tell us what you're building and we'll come back with ideas and next steps.
