Publish individual static pages and Collection pages without affecting the rest of your site.
Single-page publishing lets you publish an individual static page or Collection page without publishing your full site. You can launch a campaign page, update copy, or ship a new design without waiting for unrelated in-progress work to be ready — or risking accidentally pushing it live. Single-page publishing is an Enterprise-only feature.
Before you get started
Your site must have been published at least once using a full-site publish before you can use single-page publishing. You also need a role with the Can publish permission to publish a single page. Learn about site roles and permissions.
To publish a single page:
Open the page you want to publish in Webflow
Click Publish
Choose This page (or This CMS template for Collection pages) in the publish modal
Review the changes listed in the publish summary
Click Publish to staging or Publish to production
Note that you can’t publish a single page from staging to production. If you publish a single page to staging, you’ll need to run a full-site publish to push those changes to your production domain(s).
Good to know
You can also trigger a single-page publish using the Webflow v2 API — useful for automated publishing workflows and CI/CD integrations.
Understand what gets published
Publishing a single page publishes only that page and any localized versions of it — no other pages, CMS content, or site-level settings are affected.
Included in a single-page publish:
Page content and design changes
Page-level settings, including custom code
Optimize variations on the page
Instances of that page in secondary locales (unless in draft)
Not included in a single-page publish:
CMS item data — to update CMS content, publish the Collection item or your full site
Site-level settings such as fonts, site-wide custom code, and 301 redirects — these require a full-site publish
You can also publish individual Collection pages — publishing a Collection page applies your design and page-level settings changes to all Collection items using that template. Changes to dynamic content aren't included — publish the Collection item or your full site to make those changes live. If a Collection hasn't been published before, you'll need to run a full-site publish first.
Understand how global changes work with single-page publishing
If you've made changes to a global style, component, variable, or interaction since the last full-site publish and you choose to publish a single page, the publish summary flags them as global changes with a visual indicator. You can still choose to publish — the warning is there to keep you informed, not to stop you.
Only the current page reflects those global changes after publishing. Other pages keep their current live version until you publish them individually or run a full-site publish.
Important
If you publish a page that includes changes to global styles, components, variables, or interactions, other pages on your site will temporarily show an older version of those changes. Publish your full site to bring everything back in sync.
Limitations
No rollback — you can't revert to a previous published state. To undo a change, update the page and publish again.
No unpublishing — you can't unpublish a page using a single-page publish. If you set a page to draft, run a full-site publish to remove it from your live site.
No CMS item publishing — CMS item content isn't included in a single-page publish. Publish the Collection item or your full site for content changes.
No scheduled publishing — you can't schedule a single-page publish for a future date and time. Publish manually or use a full-site publish for scheduled workflows.
One publish at a time — only one publish can run per site at a time, whether full-site or single-page. If a publish is already in progress, Webflow shows who's currently publishing and the publish button is unavailable until their publish finishes.
Main branch only — you can't publish a single page from a branch environment. Switch to your main branch first.
Single-page publishing and page branching
Single-page publishing and page branching work together as complementary publishing workflows:
Use single-page publishing for fast, isolated updates — like launching a new campaign page, updating copy, or testing a page update — where changes are scoped to the current page.
Use page branching when working on changes that affect global styles, components, or multiple pages at once. Merge the branch when the work is reviewed and ready, then use a full-site publish.