Webflow Client Handoff for Agencies: The Complete Process

TL;DR: A Webflow client handoff is finished when the client owns the site or its billing, holds a seat with the right role, can edit content without touching the design, and has written documentation of how the build works. The biggest change for agencies this year is that Webflow's legacy Editor becomes unavailable on August 4, 2026, so client access now runs through client seats and site roles instead (Webflow Help Center).

• The legacy Editor is unavailable from August 4, 2026, and Editor branding (whitelabeling) is deprecated with it.
• Agency Workspace plans include 3 client seats per site; Freelancer plans include 1 per site.
• Client payments moves the Site plan bill to the client while the site stays in your Workspace.
• A full site transfer moves the paid Site plan and the custom domain with no downtime.
• Content editor is the right default role for a client who edits copy but should not touch design.
• Keep build access after handoff through Webflow's Agency or Freelancer guest role.

What is a Webflow client handoff?

A Webflow client handoff is the process of transferring control of a finished site to the client, and it covers four separate things: billing ownership, Workspace and site access, editing permissions, and documentation. Agencies often treat handoff as one button, but Webflow keeps ownership and access in different places, configured independently.

On the white label builds I run for agencies, a project is not delivered until all four are written down and confirmed by the client in writing. If your contract says "handover on launch" without naming which of the four it means, rewrite that clause before the next project starts.

What changes for handoffs on August 4, 2026?

Webflow's legacy Editor becomes unavailable on August 4, 2026, and legacy Editor users are being moved onto a client seat or limited seat carrying the Content editor role (Webflow Help Center). Automatic migration began on May 4, 2026 and rolled out over two weeks, so most agency clients already have a seat waiting for them.

Two side effects matter for agencies. Editor branding, the whitelabeling feature that replaced Webflow's logo inside the legacy Editor, is deprecated along with it. And the quick-edit shortcut changed: appending ?edit to a live URL is replaced by ?update.

What I see agencies get wrong here is assuming the migration covered everyone. A client who was invited to the legacy Editor but never created a login before May 4, 2026 was not eligible and needs a manual invite. If you have a handoff scheduled in the next month, open Site settings, then Site access, then Clients on every live client site this week and confirm the seat exists.

Who should pay for the Webflow Site plan after launch?

The client should pay, and Webflow gives Freelancer and Agency Workspaces two ways to arrange that. Client payments lets a Workspace owner or admin hand the Site plan bill to the client, who then pays for the Site plan, bandwidth and add-ons such as Localize, Optimize and Analyze directly in Webflow, while the site itself stays in your Workspace (Webflow Help Center).

Two limits are worth knowing before you plan around it. Only one client can be attached to a site at a time, and a Workspace can hold a maximum of 10 pending client payment requests. Clients invited this way are assigned the content editor role by default, which you can change in Site settings under Site access.

On the projects I lead, client payments is the default for clients staying on a retainer, and a full transfer is reserved for clients who are leaving. If you plan to keep maintaining the site, use client payments rather than transferring it.

How do you transfer a Webflow site to a client Workspace?

A Webflow site transfer moves the site, its paid Site plan and its custom domain from a Freelancer or Agency Workspace into the client's Workspace with no downtime and no loss of unused plan time (Webflow Help Center). The transfer itself runs from Site settings, then Billing, then Transfer site. When I run a transfer, I clear the conditions below the day before rather than on handoff day.

• The receiving client Workspace must not be an Enterprise Workspace.
• The site has to be removed from Made in Webflow, and Creator Credits contributors cleared, before the transfer.
• Shared Libraries are uninstalled on transfer, and any library components, assets and variables in use become site-level equivalents.
• If the site exceeded its bandwidth for 2 consecutive months, the client has to buy a matching plan before the transfer completes.
• If the site exceeded bandwidth for a single month, Webflow allows the transfer and resets bandwidth usage to 0.

After a transfer you cannot make changes to the site unless the client adds you to their Workspace. Agree that return path in writing before you send the transfer request.

Which Webflow seats and roles should the client get?

Give the client a client seat with the Content editor role unless they genuinely need to build pages, in which case use Marketer. Client seats are site-specific, included free with Workspace plans for freelancers and agencies, and additional client seats cannot currently be purchased (Webflow Help Center). The rule I apply on client projects is one seat per person who will actually log in, never a shared login. If the client needs to approve work rather than edit it, Reviewer is the correct role.

Workspace plan	Client seats per site	Roles available
Starter (freelancers and agencies)	1 per paid site	Marketer, Content editor, Reviewer
Freelancer	1 per site, staged or paid	Marketer, Content editor, Reviewer
Agency	3 per site, staged or paid	Marketer, Content editor, Reviewer

What can a Webflow Content editor actually do?

A Webflow Content editor can edit static and dynamic content on the canvas, create, update, delete and publish Collection items, modify page settings including the SEO title and meta description, create and edit page branches, and view the Site Activity log (Webflow Help Center). Publishing to the live site only works when the "Can publish" toggle is on for that seat.

One restriction surprises clients regularly: no client seat role can edit form settings. Only owners, admins, site managers and designers can, while Marketers and Content editors are limited to viewing and exporting form submissions. If lead routing belongs to the client, price the time to make those changes for them.

What should a Webflow handoff pack contain?

A Webflow handoff pack is the written record that lets someone other than you maintain the site, covering structure, conventions, integrations and recovery. In the handoffs I run, the pack lives as a page inside the client's own documentation tool rather than a PDF that disappears into an email thread.

Recovery deserves more attention than it usually gets. Webflow creates restore points automatically on every 50th auto-save, paid Site plans keep unlimited backups, and only Site managers can access site backups (Webflow Help Center). If nobody on the client side holds the Site manager role, they cannot undo a mistake without calling you first.

How do you keep access to the site after handoff?

Webflow's Agency or Freelancer guest role lets a client Workspace invite your team in without giving up ownership of the site. A client Workspace can invite up to 2 Freelancer or Agency guest teams for free, or 10 on Enterprise, and the guest side needs its own Freelancer or Agency Workspace plan (Webflow Help Center). A guest Workspace admin can bring up to 5 guest team members, or 10 when the host Workspace is on Enterprise.

When I hand a site to a client who wants us on retainer, the guest invite goes out in the same session as the transfer, before anyone logs off. If the client is not on a plan that supports guest teams, agree an alternative access route in writing before transfer day.

What do agencies get wrong in Webflow handoffs?

The most common Webflow handoff failure is not technical. The agency hands over access without handing over understanding, and a client with a Content editor seat but no naming convention still calls for every change, which means the agency carries support cost it never priced.

• Handing over on launch day, when the client is distracted, instead of a scheduled session a week or two later.
• Leaving the agency's email on the domain registrar and DNS, which becomes an emergency years later.
• Never testing the client's login, so nobody notices the invite went to a shared inbox.
• Skipping a recorded walkthrough, which is the cheapest support deflection tool an agency can produce.
• Documenting the design system but not the integrations: forms, analytics, CRM and third-party scripts.

Fix that list and most handoff disputes stop happening. The delivery process that feeds into a clean handoff is covered in my white label Webflow workflow, and the checks I run before launch are in the Webflow QA checklist.

If your agency's handoffs keep generating support tickets months after launch, the fix is usually in the process rather than the build. Tell me how your delivery process works today and I will tell you where it leaks.