Webflow Release Notes

Add Webflow components directly to rich text fields, both on canvas and in the CMS panel.

Components like CTA buttons, testimonial cards, and pricing tables can elevate your content, and guide users through their discovery journeys. But until now, these often required third-party solutions or custom code embeds.

Starting today, you can add any Webflow component directly into rich text, on the canvas or in the CMS panel, and configure its properties per item. Update the component once, and every instance across your CMS updates with it.

This will make it much easier to create and maintain functional CMS content that’s optimized for conversions.

How it works:

• Open a rich text field or element and hit / (or the + button) to bring up the insert menu.
• Choose Component, pick the one you want, and it drops in at your cursor.
• The component’s settings open automatically so you can configure that instance's properties right away.

Please note: Components containing Collection Lists can’t be placed in rich text. Additionally, components within rich text can’t be bound to the CMS, and their slots can’t be exposed.

Support for components in the CMS will begin rolling out today, and should be available to all users in the next week.

It can be difficult to maintain design consistency and quality across breakpoints — often requiring repeated context switching. Today, we’ll begin rolling out breakpoint canvas, so you can edit with all breakpoints side-by-side in a unified view.

With this release you can expand your canvas to see your desktop, tablet, mobile, and large breakpoints side-by-side for instant visibility into cascading changes. Alternatively, you can focus your canvas on a single breakpoint for scroll-based interactions, or a more browser-like experience.

This makes responsive design easier while you’re building, and it makes your AI agent’s changes much easier to review across devices, so you can maintain your design consistency and quality without the constant context switching.

Breakpoint canvas is rolling out now and will be available to all Webflow users in Design, Build, and Edit modes in the next week.

Please note: breakpoint canvas will not be available in Preview or Comment mode.

Today in the Webflow Conference keynote, we unveiled Source by Webflow: a new platform for marketing teams and their agents to launch, optimize, and scale digital experiences, together.

‍Source connects with your codebase and martech stack, bringing agentic and visual development into a shared operating environment, with every marketer, designer, and developer getting a workspace tailored to their job and the outcomes they own.

AI has made building easier. Anyone can ship a site through prompting, but building is only one part of the job. The hard part is what comes after: scaling what works, knowing what to change, and driving impact with every iteration.

That's especially true on the web, where AI has fundamentally changed how buyers discover, evaluate, and choose brands, raising the stakes from first impression to final conversion. Teams need to work synchronously with agents to ship campaigns, optimize for AI discovery, test variants for CRO, and localize across markets — continuously, not just at launch. But existing solutions haven't caught up to that reality.

What Source unlocks

That’s why we built Source: one system designed from the ground up for marketing teams and agents to drive growth on the web together. Here’s what it unlocks:

Agentic scale with visual control, on one surface.

Source makes code the foundation for everything that ships on your site. With direct access to that code, Source’s agents can take on larger, more complex changes without the constraints of an abstraction layer. And when the work calls for a human hand or precise finishing touch, Source brings the best of Webflow’s visual canvas, with every edit writing to that same underlying code. The result: AI speed while maintaining craft and control.

Views: a new way to tailor workspaces to your team.

Every marketer, designer, and developer gets a unique workspace powered by Views: a new primitive that lets teams shape their software to the exact jobs and outcomes they own. Views are dedicated surfaces for visual site building, campaigns, content, optimization, and can be custom-built for any workflow your team needs. Each workspace is governed with brand systems, role-based access, approval paths, and audit trails from day one, so your team of practitioners and agents can move fast within the right guardrails.

A shared operating layer across your existing stack.

Source is composable by default, bringing your codebase, CMS, hosting, and marketing tools (including sites you’ve already built in Webflow) into one environment where teams and agents work together. Whether you want to keep the infrastructure you’ve invested in or leverage Webflow’s native solutions, Source provides the flexible workspaces, governance, and agentic layer your team needs to launch, optimize, and scale the web.

Join us as we shape the future of web marketing

Source is currently in a limited research preview, and we’ll be enrolling select agency partners and customers in a phased approach over the coming months.

Fill out the form on webflow.com/source to stay in the loop on updates, or if you want a hand in shaping what's next, check the box and apply to join the research preview. If you’re approved, we’ll reach out with next steps.

To learn more details about what we're building with Source, how it comes to life across your team, and what our agency partners co-developing Source with us are saying, read the full announcement blog.

We're introducing visual editing for AI code components, bringing the same direct, on-canvas control to AI-generated elements that Webflow has always given native ones.

This makes it possible to:

• Select any element inside a code component and adjust it in the Style Panel, the same way you'd style any other Webflow element
• Add an element as context in a prompt, so the AI Assistant scopes changes to that element specifically
• Manually edit text on the canvas

AI code components now work like everything else in Webflow. Generate a component, then refine it directly, no prompt required for the small stuff.

Check out our help center article to see how it works

We're introducing Agent Instructions Generation. Instead of starting from a blank editor, agents can generate a first draft of Brand Guidelines, Design System, Asset Guidelines, and CMS Guidelines straight from your site.

This makes it possible to:

• Generate Brand Guidelines that capture your brand's voice, tone, and personality
• Generate a Design System guide that documents your components, variables, and how they're meant to be used
• Generate Asset Guidelines for how images and media should look and behave across your site
• Generate CMS Guidelines that document your collection structure and field-level rules

Every draft comes from your actual site, not a generic template. Everything it creates is yours to edit, and nothing is locked.

Check out our help docs to see how it works.

Designers can now control which components are allowed in component slots, helping Marketers build confidently while keeping layouts intact.

Nothing hurts more than handing off a carefully designed component system only to have a layout break because the wrong component was placed in a slot. Designers end up doing cleanup work to make everything fit back together, while Marketers have to wait for fixes before they can keep building.

Until now, there wasn’t a way to define which components were intended for a particular slot. That ambiguity could lead to mistakes, broken layouts, and unnecessary back-and-forth.

Starting today, anyone with the Designer or Site manager role (or equivalent custom role) can control which components are allowed in a given component slot.

Here’s what you can expect:

• Designers set the guardrails, Marketers build with confidence. Designers can define exactly which components belong in each slot, so Marketers don’t have to guess what works where.
• Mistakes get caught immediately. If a Marketer tries to add a component that isn’t allowed, they’ll see a clear message showing which components are permitted in that slot.
• Add guardrails only where they’re needed. Slots continue to allow all components by default, so Designers can introduce restrictions selectively without changing how the rest of their component system works.

One Light, Dark, or System theme for the Webflow UI — applied consistently as you move around the product.

One appearance preference for Webflow — System, Light, or Dark — now follows you across Dashboard, Sites and Optimize sites. This includes Light mode in Sites.

Choose your theme

Pick System, Light, or Dark. If you choose Dark, you can also pick Darker, Default, or Brighter. System follows your operating system's light or dark appearance.

One setting across product surfaces

Your preference saves to your account. Move between product areas without resetting theme on each surface.

This controls the Webflow interface — not your published site.

In Build mode, you can now use the arrow keys to change what's selected on the canvas — the same elements you can already click. Using the same keys as Design mode: ↑ Up, ↓ Down, ← Left, and → Right to move through parent, child, and siblings, and Option/Alt + ↑ Up or ↓ Down to step through elements one by one.

If you're working through a page — checking content, updating text, reviewing components — you can move through them in sequence without clicking each one individually.

Arrow keys only stop on elements you can select. A rich text element is one stop and components inside it stay reachable. Hidden elements are skipped.

Recently, we launched Webflow MCP 2.0, giving you and your AI agents the ability to design, build, and manage your sites, with the full context of your design system and CMS data. Now, those same MCP-powered capabilities are available in both Codex and ChatGPT, so you can work on your Webflow sites from whichever OpenAI experience fits your workflow.

As part of this update, you can now access an expanded set of built-in AI skills in ChatGPT and Codex. These specialized workflows help automate complex tasks while following Webflow best practices, including:

• Site audits: Review your site for SEO, AEO, accessibility, broken links, performance issues, and optimization opportunities.
• CMS management: Create, update, organize, and scale CMS collections and content with confidence.
• Safe publishing: Validate changes before publishing and manage custom code without disrupting your live site.
• Developer workflows: Scaffold projects, build reusable code components, create extensions, and deploy applications to Webflow.

To get started, connect your Webflow workspace from ChatGPT or Codex and grant access to the sites you'd like to manage.

Note: Webflow for ChatGPT is currently available at no additional cost and does not consume AI credits. As we expand capabilities over time, certain AI-powered actions may require AI credits in the future.

Learn more

• Read the full announcement
• Read the Help Center documentation

Every marketing website exists for a reason, whether it's generating leads, driving revenue, or booking demos. With Site Goals you can define the "north star" metrics for your website, allowing Webflow Analyze & Optimize to understand what matters most to your business.

Your site's north star — defined once, understood everywhere

Once you set up your Site Goals, they’re automatically available across every optimization and become the default lens through which Webflow Analyze and Optimize show how your site is performing.

In Analyze: The Site Overview surfaces performance across all your Site Goals, showing the total conversions, leads, revenue, and more your site has driven so you can answer, “Is my site performing?” the moment you land on the page.

In Optimize: Site Goals can be set as the target for any optimization and are available on every report, giving you a consistent measure of whether your tests are moving the needle on what actually matters. When paired with AI-optimized tests, they give the system context to optimize autonomously across multiple running experiments. They also power the Optimize Overview, which shows the cumulative ROI of your CRO program.

To set up your first Site Goal, you can:

• Promote any existing goal to a Site Goal
• Create new goals and track them as Site Goals
• Set up the HubSpot or Marketo integrations to track form submissions
  • Only available for Enterprise plans

You can also:

• Set an optional value for each Site Goal to reflect business impact (e.g., a demo request is worth more than a newsletter signup)
• Customize your terminology to refer to your Site Goals as leads, conversions, or revenue

What's next

Site Goals lay the foundation for more intelligent, agentic optimization. By giving Webflow Analyze and Optimize a shared understanding of what matters most to your business, AI can make smarter recommendations, measure their impact, and ultimately optimize your site more autonomously toward the outcomes you care about.

These updates are now available for all Analyze and Optimize customers with both Webflow sites and non-Webflow sites. Click to learn more about Analyze and Optimize.

Help Documentation:

• Site goals in Analyze
• Site goals in Optimize
• Site goals in Optimize for non-Webflow sites

Get page content's translatable parameter previously only checked whether a page's entire canvas was excluded from translation. A component instance's overridden property values were always returned as-is, even when the specific property was excluded — inconsistent with get component properties, which already filtered properties individually.

translatable now filters component property overrides the same way: an overridden value is omitted from a component instance's propertyOverrides if that property is excluded from translation for the requested locale. If a component instance's overrides are all excluded, the instance is omitted from the response entirely. A component instance with no overrides at all is unaffected.

Behavior that hasn't changed: only exclusion rules scoped to manual translation are respected, and omitting translatable returns the same response as before this parameter existed.

Webflow sitemaps now include timestamps to help search and AI engines find, crawl, and surface your latest content faster.

Webflow's automatic sitemap now includes a timestamp for every page, telling search engines and AI answer engines exactly when each page was last updated. This means when you publish a change, like a new blog post, an updated product page, or a pricing refresh, Google can prioritize re-crawling that specific URL right away instead of waiting on its own crawl schedule. This way, your updated content shows up in search results faster.

There are a few other sitemap improvements here, too. You can now use your canonical URL as the domain in your sitemap, which is particularly useful for sites running behind a reverse proxy. Sitemaps also update when you publish a single page, rather than requiring a full-site publish, so sitemap changes stay in sync with more targeted publishing workflows.

Just as importantly, AI-powered answer engines like Google AI Overviews, Perplexity, and ChatGPT search use to decide which sources to cite in the answers they generate. Without the timestamp, they had no reliable way to tell which of your pages were updated yesterday versus two years ago. Now your freshest, most authoritative content is the content those engines are most likely to surface and cite, which is a growing competitive advantage as search traffic shifts from blue links to AI-generated answers.

Because the timestamp is tracked per page (not per site publish), crawlers and answer engines alike can focus on the URLs that actually changed, making more efficient use of your crawl budget — especially valuable for larger sites or frequently updated CMS collections. It's a small sitemap change with a big impact on how visible your brand is in both traditional search results and the AI answers your customers are increasingly reading.

Global telemetry configuration

v2.5.0 changes where telemetry preferences are stored and fixes a crash affecting sites that combine code components from different sources.

webflow auth telemetry --enable/--disable now writes to a global config file (~/.config/webflow/telemetry.json on macOS/Linux, %APPDATA%\webflow\telemetry.json on Windows) instead of the current project's webflow.json. Bare CLI invocations in a project without a manifest no longer create one just to record a telemetry preference.

A new --local flag opts back into the previous behavior for teams that want a per-project override:

webflow auth telemetry --disable --local

A webflow.json that already has a telemetry setting continues to be read and takes precedence over the global config for commands run in that directory. DO_NOT_TRACK continues to override everything.

Fix: crash when combining code components from different sources

Fixed a crash — Element type is invalid: expected a string ... but got: object — that could occur when a published page loaded code components built against different React major versions. Upgrade @webflow/react to 2.1.1 and re-bundle libraries to pick up the fix.

Also in this release

Patched transitive brace-expansion and PostCSS dependencies addressing known vulnerabilities.

webflow cloud deploy can now resolve its framework builder from a shared @webflow/app package when enabled server-side; the local COSMIC_BUILD_ENGINE=v2|legacy environment variable can override the selection for a single run.

Upgrading

npm install -g @webflow/webflow-cli@latest

Hide specific components from the Marketer role to keep component libraries focused, reduce confusion, and give Designers more control over shared libraries.

Not every component is meant for every teammate. You may have complex components that are specific to development or design work that clients or marketers don't need to do their jobs. Until now, there was no way to keep these components out of view for collaborators who didn't need them.

Starting today, anyone with the Designer role can use a new toggle to hide specific components from the Marketer role, so marketers and clients only see the components relevant to their work. When someone with the Marketer role is viewing a site in Build mode, hidden components won't appear in the Add panel. If the component is part of a shared library, this setting travels with it, so the same visibility rules apply downstream.

This gives Designers more confidence to build robust component libraries without worrying about confusing or overwhelming less technical teammates or clients.

Tip: Have a whole group of components you want to hide? Open the group settings and click “Hide all for Marketers" to update the visibility for all the components in that group at once!