Webflow Expert vs Developer vs Designer: What's the Difference?

TL;DR: A Webflow designer decides what a site looks like, a Webflow developer builds and ships it, and "Webflow expert" is no longer an official Webflow title at all. Webflow retired the Experts program in favour of the Certified Partner Program, so the credentials that can actually be checked today are the two Webflow certifications and the Foundations, Certified and Premium partner tiers.

• Webflow designer: visual design, layout system, hierarchy. Usually delivers Figma files, not a live site.
• Webflow developer: builds in Webflow, owns CMS structure, interactions, performance, SEO settings and launch.
• "Webflow expert" is a marketing phrase, not a credential Webflow issues today.
• Webflow's two certifications, Practitioner and Visual Developer, each cost $100, run 50 multiple-choice questions in 90 minutes, and stay valid for two years.
• Certified Partner status is the harder signal, because it requires three client sites reviewed against a published rubric.

What is the difference between a Webflow expert, a Webflow developer, and a Webflow designer?

The difference between a Webflow expert, a Webflow developer and a Webflow designer is that only two of those three describe a real job. A Webflow designer decides what the site looks like and how information is organised. A Webflow developer builds that design inside Webflow and owns everything technical that follows, including CMS structure, interactions, page settings and publishing. "Webflow expert" describes seniority rather than a function, and since Webflow retired its Experts program it no longer maps to anything the platform certifies. When an agency asks me to compare candidates, the first thing I check is which of the two real jobs the person actually does day to day, because the title on the profile rarely tells you.

• Ask a designer for a Figma file with named components and responsive frames, not flattened artboards.
• Ask a developer for a live Webflow site you can open and inspect, not a portfolio screenshot.
• Ask either one who owns the CMS schema, because that answer reveals where the boundary sits on their past projects.
• Ask who handles launch, redirects and form configuration, since those tasks fall between roles and often get dropped.

Is "Webflow Expert" still an official Webflow title?

"Webflow Expert" is not an official Webflow title today. Webflow replaced the old Experts program with the Certified Partner Program, and the current program tiers published in Webflow's Certified Partner program documentation, updated April 2026, are Foundations, Certified Partner and Premium Partner. Anyone still advertising themselves as a "Webflow Expert" is either using the phrase loosely or referencing a program that no longer exists under that name. When I vet a delivery partner for an agency, the check is simple: search the person or company in Webflow's partner directory, because directory listing is a benefit only Certified and Premium Partners receive.

The practical consequence is that "expert" tells you nothing verifiable. Certified Partner status, a certification badge, or a live site you can inspect all tell you something. Treat the first as marketing copy and the other three as evidence.

What does a Webflow designer actually do?

A Webflow designer produces the visual and structural design of the site, usually in Figma, and hands it to whoever builds it. A Webflow designer decides typography scales, colour systems, spacing rules, page hierarchy and how each section behaves across breakpoints. Some designers also build in Webflow, but designing and building are separate skills, and a designer who does not build often produces files that are beautiful and expensive to implement. On the projects I lead, the single biggest predictor of a smooth build is whether the designer used real components and auto layout rather than one-off frames.

• Deliverable: a Figma file with named components, a type scale, a colour system and layouts for every breakpoint.
• Green flag: the designer has defined mobile and tablet layouts, not just desktop.
• Green flag: interactive states such as hover, focus and error are designed, not left to the developer to invent.
• Red flag: a single flattened artboard per page with no reusable components.
• Red flag: no defined behaviour for CMS content of variable length, such as long post titles.

What does a Webflow developer actually do?

A Webflow developer builds the site inside Webflow and owns every decision that affects how it performs and how it is maintained after launch. A Webflow developer sets up the class system, builds reusable components, structures the CMS collections and reference fields, writes the interactions, configures page settings and SEO fields, sets redirects, and publishes. Webflow's own Visual Developer certification blueprint reflects that split, weighting build and design at 38%, content management at 20%, quality and performance at 15%, site configuration and forms at 15%, and site delivery and collaboration at 12%. When I audit a Webflow site I did not build, the first thing I check is the class system, because a chaotic one predicts every other problem in the project.

The distinction that matters for hiring is maintainability. Two developers can produce identical-looking sites, where one can be updated by the client's marketing team in minutes and the other cannot be touched without breaking layouts.

What do Webflow's certifications actually prove?

Webflow's certifications prove that someone passed a proctored multiple-choice exam on platform knowledge, which is a real but narrow signal. Webflow currently offers two: the Practitioner certification for foundational knowledge and the Visual Developer certification for advanced build skills. Both are 50 multiple-choice questions, AI-proctored, 90 minutes, priced at $100, offered in English, with no prerequisites and a validity period of two years. A certification tells you the person knows the platform's features; it does not tell you whether they can structure a CMS for a client who will double their content in a year.

Detail	Webflow Practitioner	Webflow Visual Developer
Level	Foundational knowledge	Advanced, production-ready builds
Questions	50, multiple choice	50, multiple choice
Time allowed	90 minutes	90 minutes
Price	$100	$100
Largest exam domain	Build and design, 33%	Build and design, 38%
Validity	2 years	2 years

Sources for the table above: Webflow University's Practitioner and Visual Developer certification pages, checked August 2026.

Is Certified Partner a role, or a credential?

Webflow Certified Partner is a business credential, not a job role, which is why it does not sit on the same axis as "designer" or "developer". A Certified Partner can be a solo freelancer or a fifty-person agency, and the tier says nothing at all about which of the two jobs that person performs day to day. Webflow's Partner Program runs three tiers, Foundations, Certified and Premium, paying 10% commission at Foundations and 20% at Certified and Premium on Site plans and add-ons for the first 12 months of each subscription. When an agency asks me how much weight to give the badge, my answer is that it narrows a shortlist and never decides it, because role fit still has to be checked separately.

Reaching the Certified tier is not trivial, which is why the badge carries some signal: Webflow requires an active Freelancer or Agency Workspace plan, a pre-qualification assessment, at least three new client sites built as a Foundations member, and a portfolio review against a published site grading rubric. For the full evaluation process that sits behind the badge, see the separate guide on evaluating a white-label Webflow developer.

Which one should you hire for your project?

Hire the role that matches the gap in your project rather than the title that sounds most senior. If you have no design and no site, you need a designer first and a developer second, or one person who genuinely does both. If you have a finished Figma file, you need a developer and hiring a designer will slow you down. If you are an agency looking for delivery capacity, you need a developer with agency experience specifically, because agency delivery involves handoff, documentation and client seats that direct-to-client work never touches.

• No design, no site: hire a designer, then a developer, or one person who does both and can show both deliverables.
• Design finished, nothing built: hire a Webflow developer and skip the design phase entirely.
• Site exists but nobody can update it: hire a developer to restructure the CMS and class system, not a designer.
• Agency needing delivery capacity: hire a developer who has worked white label and can document a handoff.
• Enterprise procurement requires a vetted vendor: prioritise Certified or Premium Partner status.

How to verify any of these claims in ten minutes

Verifying a Webflow professional's claims takes about ten minutes and needs no technical knowledge. Open one of their live sites, right-click and inspect an element, and look at the class names: consistent, readable names indicate a maintainable build, while stacks of names like "div block 47" indicate the opposite. Then search their name in Webflow's partner directory to confirm any Certified Partner claim. The rule I apply when vetting is that a claim you cannot check in ten minutes should carry no weight in the decision.

If you are choosing between candidates for a Webflow build and want a second opinion on which role your project actually needs, book a short call. For the interview stage, see the list of questions to ask a Webflow developer before hiring.