How do I branch a page in Webflow?

Create a branch on a Team or Enterprise plan

Page branching is a working copy of a page. You design on the copy while the original page stays as it is. Webflow offers it on Team and Enterprise Platform plans. A branch can be a static page, including utility pages, user pages, and Ecommerce pages, a draft page, a dynamic page such as a Collection page or an Ecommerce page, or a brand new page.

Open the Pages panel. For a page that already exists, hover it and click the Create page branch icon. For a page that does not exist yet, click the Create new page icon and choose New page as a branch. Branched pages do not count toward the static page limit.

The branch does not affect the main site. Changes on the main site do not show up on the branch either, unless you pull in updated classes, components, variables, or interactions. Publishing the whole site is still allowed. That publish does not include the branch. You merge first when the branch should become the real page.

Site managers and designers can create branches and merge them. Content editors and marketers can create branches and cannot merge them. On an Enterprise plan, a custom role with the content editor base role or above can create branches. A custom role without Make changes without approval has to be approved before it can merge.

Example: the live Pricing page should stay up while you rebuild the layout. Hover Pricing and create a branch. The published Pricing page stays on the current design until you merge and publish the main site.

Edit the copy, and leave the shared CMS alone

On the branch you can add, move, and delete static elements, and style them with existing, new, or combo classes. You can create components, edit a main component, and change SEO, Open Graph, site search, and custom code settings.

You cannot change the page name, slug, folder, access control, or homepage. You cannot create or modify CMS Collections, Collection items, Classic interactions, or interactions with GSAP. You cannot modify variables, and you cannot create or modify swatches. Components inside rich text stay read-only. They still display. Add or edit those instances on the main page, or after you merge.

The branch shares the live CMS. A Collection list that gains an item on the main site shows that item on the branch too.

Webflow warns you if you edit a main page that already has a branch. Content edits on the original page during the branch are lost at merge. Changes to components, classes, or interactions are not lost. A class created on the branch with the same name as a main-site class is renamed at merge, so Button can become Button 2. Pasted elements use the branch version of any class the main site also changed. The main site classes stay as they were.

Pull updates before the designs drift

A class, state, HTML tag, component, variable, or interaction changed only on the main site takes effect after you merge. It does not show on the branch until you pull it.

Open the branched page. Click the Branched status indicator, then Check for updates. Click Pull updates, then Okay. If nothing changed, a modal says the branch is already up to date.

If the same item changed on both sides, choose Main site or Branch for each conflict, then click Resolve conflicts and update.

Example: a teammate darkens the button class on the main site while you rebuild Pricing. Pull updates so the branch shows that button. If you also changed that class, pick Branch or Main site before you merge.

Merge the branch, or delete it

Merge when the branch should replace the original page. Teammates see it after they refresh the Designer. On the branch, click the Branched status indicator, then Merge, read the summary, and click Merge branch. From the Pages panel, hover the branch, click Merge this branch with your site, and confirm. If a class, state, HTML tag, or main component changed on both sides, pick Main site or Branch for each row, then click Resolve conflicts and merge.

Comments on the branch are deleted at merge and cannot be recovered. Branches do not come along if you transfer or duplicate the site.

Delete the branch to keep the original page. Click the Branched status indicator, then Delete branch, and confirm. A site backup can restore the main site and the page branches to that timestamp. Several people can work on one branch at once. Presence shows in the top bar. If the person who started the branch leaves, another member with design access can take it over when that person is not in the branch.

Stage a review, then publish from the main site

Click Stage branch, then Publish branch, to put the branch on its own staging subdomain. That address is separate from the site's main staging subdomain. Anyone can open it, including people without a Webflow account. Private staging asks them to sign in.

The staged URL is a snapshot of the whole site plus this branch. On a class conflict, the branch version wins there. Each branch has its own URL. Merging or deleting the branch unpublishes that URL. Reviewers cannot stage. You must publish the site once before the first branch stage. Only Collection items that are already created and published appear. You cannot send that staging URL straight to production. Merge, then publish the main site.

Example: stage the Pricing branch and send the URL for review. After approval, merge, refresh, and publish the main site. If the live page is still old, the merge has not been published. If copy you edited on the original Pricing page during the branch is gone, the merge overwrote that page content. Restore a backup from before the merge if that copy has to return.