Webflow Conf 2026: what was announced, and what you can use today
Webflow announced Source, Campaigns, Assets, Releases, MCP 2.1 and new AEO agents on 1 September 2026. Most are previews or betas. Here is each one with the availability Webflow attached to it.
Webflow announced eight things at Webflow Conf on 1 September 2026, and most of them cannot be used yet. That is not a criticism, it is how keynotes work, but it matters for anyone planning a project around them. Here is each announcement with the availability Webflow itself attached to it, read from Webflow's own recap on 21 September 2026.
Every announcement, and when you can have it
| Announcement | What it is | Availability |
|---|---|---|
| Source | A platform joining your codebase, CMS, hosting and marketing tools, with agents working in it | Limited research preview |
| Campaigns | Brief to landing pages, variants and ad creative, pushed to channels such as Google Ads | Beta, for purchase in October |
| Assets | Agents that adapt approved brand creative across channels | Beta from October |
| MCP 2.1 | GSAP interactions by prompt, better CMS querying, Webflow Cloud deploy errors surfaced to agents | Everyone, later in September |
| Releases | Branch the whole site, CMS and locales included, and stage it before shipping | Beta, later this year |
| AEO content agents | Find topics where competitors are cited and you are not, then draft content in the CMS | Enterprise customers by default |
| Agent Instructions generation | Webflow drafts the context files agents work from | Rolling out to everyone from 1 September |
| Agent Presence | Shows where an agent is working live on the canvas | All customers, later in September |
What changes for a project starting now
Two things, and both are small. Agent Instructions are usable today and worth writing properly, because they are the file an agent reads before touching your design system. And MCP 2.1 is close enough to plan around: the CMS querying change in particular means an agent can filter on custom fields and search across reference fields in one request, where before it needed the exact field name and several round trips.
Everything else is a reason to watch, not to wait. A launch scheduled for November should not depend on Releases, which Webflow describes as a beta later this year, and a team on the Premium plan should not plan around AEO content agents, which sit with Enterprise. Where the AEO announcement does help is the number Webflow published alongside it: across 2,000 company websites it analysed, the median company appeared in 16% of the AI answers it would want to be part of and was cited in 6%. That is Webflow's figure about its own market, and it is a fair measure of how much room there is. What moves it is covered in how AI search engines decide what to cite and what Webflow's AEO agents actually do.
