Webflow lets designers curate component access in Build mode

Webflow introduced component visibility controls on August 19, 2026, allowing users with the Designer role to hide selected components from teammates and clients with the Marketer role. The feature keeps the component list in Build mode focused on the sections marketers actually need while leaving technical or design-specific components under the control of the design team.

{getToc} $title={Table of Contents}

Webflow lets designers curate component access in Build mode

Large Webflow projects can contain components created for different purposes. Some are intended for routine content production, while others may support specialized layouts, experiments, development work, or sections that require detailed design knowledge. Until now, every component remained visible to collaborators even when it was not relevant to their role.

The new visibility toggle lets Designers decide which components appear in the Add panel when someone with the Marketer role works in Build mode. Marketers receive a shorter and more relevant selection, reducing the chance of choosing a technical component or an internal variation that was not designed for everyday page building.

{getCard} $type={post} $title={More useful reading}

Components can be hidden individually or as a group

To hide one component, a Designer can open its settings and disable the Show for Marketers option. The component then disappears from the component list for users with the Marketer role, while remaining available to Designers who continue maintaining the broader design system.

Webflow also provides a Hide all for Marketers action in component group settings. This is useful when a complete group contains internal, experimental, or highly technical components that content teams should not insert. Designers can later restore the group with the corresponding Show all for Marketers option.

Shared libraries preserve the visibility setting across sites

When a hidden component belongs to a shared library, its visibility setting travels with that library to the sites where it is installed. Design system teams can therefore define the intended Marketer experience once instead of manually reorganizing the same component list on every connected website.

This can be especially useful for agencies and organizations that distribute one library across several client, campaign, or regional sites. Marketers can receive approved page-building components, while more advanced foundations and specialized layouts remain visible only to the Designers responsible for maintaining them.

Visibility settings do not remove existing component instances

Hiding a component only changes whether it appears in the component list for the Marketer role. It does not delete the component, remove it from a published website, or erase instances that were already placed on a page. Existing content continues to work after the component is hidden.

Group visibility also applies only to the components inside the group when the action is performed. If a Designer adds another component to that group later, the new item remains visible to Marketers until it is hidden individually or the group-level action is applied again.

IMPORTANT: Component visibility is an organizational control for the Marketer component list, not a command for removing content or hiding elements on the published website. Review existing page instances separately if a component should no longer be used.{alertWarning}

Daisuki's Take: What This Means for Web Designers

This update gives designers more control over the page-building experience they hand to clients and content teams. A component library no longer needs to expose every internal building block simply because all of them belong to the same Webflow project.

For template creators and agencies, curated visibility can make a sophisticated design system easier to use. Marketers can concentrate on approved heroes, cards, calls to action, and content sections without navigating components that depend on advanced layout or development decisions.

We would treat visibility as part of the library's documentation and governance rather than a substitute for clear component names and descriptions. The strongest workflow combines a focused Marketer list with organized groups, understandable labels, and regular reviews whenever the shared library changes.

{getCard} $type={custom} $title={What's New?} $info={Find more AI Web design news} $icon={}

Sources and Recommended Links

• Control component visibility | Webflow Official Updates
• Components overview | Webflow Official Help Center