Better in English?
Better in English? Switch the website language for a better experience.
Webflow announced a major update to its Page Branching feature, available since July 17, 2026. Until now, a page branch could only be worked on by one person at a time. Now, multiple members of the same team can view and edit the same branch simultaneously, without stepping on each other's toes.
Here's what's changing, concretely:
This feature is available today for all Enterprise customers.
On paper, this looks like a simple technical improvement. In reality, it's a genuine shift in approach. Until now, Webflow enforced a take-turns logic, even on branches: one designer worked while the other waited. On a project with multiple hands on deck -- which is daily reality for any agency -- that constraint created friction that was invisible but costly in time.
With real-time co-editing on the same branch, we're finally getting closer to what other collaborative tools (Figma leading the pack) have offered for years: multiple minds, one shared workspace, no waiting in line.
| Before this update | After this update |
|---|---|
| Only one person per branch at a time | Multiple people simultaneously on the same branch |
| Change review only after the fact | Live review and approval, before merging |
| No visibility into who's doing what | Real-time presence indicators |
| Implicit queue between teammates | Parallel work with no bottlenecks |
At Mazette.co, we work as a team on nearly all of our Webflow projects. Designer, developer, project manager: everyone gets involved, often on the same pages, sometimes on the same day. We knew that "one person at a time" limitation on branches all too well, and we've worked around it more than once with some fairly makeshift arrangements -- time slots, Slack messages to free up the branch, that sort of thing.
So this update addresses a real operational need, not a marketing whim. It will genuinely smooth out our production sprints, especially on larger projects where several specialists need to move forward in parallel on the same page before a launch.
The catch: it's Enterprise-only. A feature this fundamental to teamwork deserves, in our view, to be available more broadly -- at least on Team plans. We're hoping Webflow will roll this down to more accessible tiers, as it has already done with other collaboration features.
Another point we'd flag as a positive: the safeguards remain in place. One branch per page, protection during merge, only one active review. Webflow isn't sacrificing workflow rigor for the sake of speed, which is exactly the balance an agency looks for in a production tool.
For businesses that trust us with their website, this update translates into shorter delivery times on complex projects, and a reduced risk of errors caused by poorly coordinated back-and-forth between team members. A quiet benefit, but a very real one.
If you're considering evolving your website or migrating to Webflow with structured support, this is exactly the kind of operational detail that separates a smooth project from one that drags on. At Mazette.co, we've built our method around this kind of standard.
Want to talk about your own project? Get in touch, and we'll show you how we work with Webflow day to day.
Code
Over 120 companies have already stepped out of the shadows with us.
Page Branching is a Webflow feature that lets you create a parallel version of a page to edit without affecting the live site. Think of it as the equivalent of a Git branch, but built for visual design. Once changes are approved, the branch gets merged back into the main page.
No, this new feature is currently limited to Enterprise plan customers. The existing safeguards remain in place: one branch per page, protection against edits during merge and publishing, and only one active review at a time.
Page Branching creates an isolated workspace to test changes risk-free. Real-time co-editing is the new layer on top of it: it lets multiple people be present and active on that same branch at the same time, with visual indicators showing who's working on what.
