Webflow Conf 2026: what it means for Framer designers
Webflow Conf 2026 was all about AI agents. Here is what Webflow announced and what it means for Framer designers and founders.

Webflow held its annual conference, Webflow Conf 2026, in Boston in early September, and the keynote on September 2 was almost entirely about agents: AI that writes code, builds landing pages, produces brand assets and drafts CMS content. If you build client sites in Framer, it is tempting to skip a competitor's event. We think that would be a mistake, because the announcements say a lot about where website tools are heading and what clients will soon expect from you.
This post sums up what Webflow actually announced, based on Webflow's own recap posts and CMSWire's coverage, and then looks at what it means in practice for Framer designers and the founders who hire them. We only list what was announced and the availability Webflow stated at the time. Several items were labelled beta or "coming later this year", so check the current status before you promise anything to a client.
The headline: Source by Webflow
The biggest launch was Source by Webflow, which Webflow describes as a way to connect your codebase and marketing stack for agentic and visual development. In plain terms, it aims to let AI agents and people work on the same site, with the site's code and its marketing tools in one place.
Source launched in a limited research preview, and no pricing was published. So this is a direction, not a product most teams can buy today. Still, the message is clear: Webflow wants to be where engineers, marketers and agents all touch the website, not only where designers build it.
Tools aimed at marketers, not designers
Three announcements were built for marketing teams rather than site builders:
- Campaigns: turns a brief into a live landing page with variants and ad creative, and connects to HubSpot or Salesforce. Webflow said it was in beta and would be available for purchase the following month.
- Assets: agent-driven, on-brand creative production built on technology from Vidoso. Webflow said it would enter beta in October.
- AEO content agents: agents that find topics competitors are being cited for in AI answers and draft content into the CMS. Webflow said all Enterprise customers have access by default, with content-refresh agents coming later.
Note that CMSWire's summary gave slightly different timing for Campaigns and Assets than Webflow's own post. That is a good reminder to treat conference timelines as targets, not dates.
What changed for people who build sites
Webflow's second-day builder keynote was more relevant to designers. The features it listed as rolling out at the event were:
- Breakpoint canvas: all breakpoints shown side by side while you design.
- Components in the CMS: drop components into rich text or CMS items and configure them with props.
- Visual editing for AI code components: edit components generated as code directly on the canvas.
Announced as coming soon were native popovers (modals, tooltips and menus), default content for component slots, Agentic Translation that carries copy changes across locales, and style props for components. Webflow also announced Releases, which branches a whole site for a staged release, as a beta planned for later in the year.
On performance, Webflow claimed up to 43% faster site rendering and up to 80% faster publishing.
Agents on the canvas and MCP 2.1
For anyone already using AI agents with their site builder, two announcements stand out. MCP 2.1 extends Webflow's Model Context Protocol server with GSAP-based interactions, better CMS querying and Webflow Cloud error logs that agents can read. Agent Presence shows agents working live on the canvas, the same way you see a teammate's cursor. Webflow also started generating markdown agent instruction files for sites, so an agent knows the project's rules before it edits anything.
Framer has been moving in a similar direction with its own MCP work, which we covered in an earlier post. Both tools now treat "an AI agent edits the site" as a normal workflow, not an experiment.
What this means for Framer designers
None of this is a reason to switch tools. Framer is still faster for design-led marketing sites, and most of the Webflow launches above target larger marketing teams. But a few things are worth acting on:
- Clients will ask about agents. Founders read these announcements. Be ready to explain how your Framer setup works with AI tools, and where a human still decides.
- Components with props are the baseline. Webflow putting components inside CMS content raises expectations. In Framer, build sections as components with variants and clear properties so clients can reuse them without breaking layouts.
- Write down your site rules. Webflow's instruction files are a simple idea you can copy today: a short document listing your type scale, spacing, colour tokens and naming rules. It helps agents, new collaborators and clients.
- Staged releases matter for bigger clients. If a client needs reviewed launches, plan your Framer workflow around staging and a clear publish checklist.
- AI search visibility is now a sales topic. AEO features show that clients care about being cited in AI answers. Clean structure, real headings and good meta data in Framer help here.
What founders should take from it
If you are choosing a website platform, do not decide based on keynote demos. Ask three plain questions: who will edit the site every week, how much of that editing you want an agent to do, and which features are generally available today rather than in preview. For a small team with a design-led brand, Framer is usually the simpler answer. For a large marketing team running many campaigns tied to a CRM, Webflow's new direction may fit better once the beta tools mature.
The useful question is not which tool has more AI, but which tool your team will actually keep the site up to date in.
Conclusion
Webflow Conf 2026 made it clear that site builders now compete on how well people and agents work together, not only on the visual canvas. For Framer designers, the practical response is to build component-based sites, document the rules behind them, and be ready to talk to clients about AI-assisted editing. Check each feature's current status before you mention it in a proposal.
Sources: Webflow: The biggest announcements from Webflow Conf 2026, Webflow: For the builders, CMSWire: Webflow launches Source.


