Source by Webflow Is the First Webflow Announcement That Actually Made Me Stop and Think

Webflow Conf 2026 wrapped up last week (September 1–3, in Boston), and out of everything announced, Source by Webflow got most of my attention. Not because "AI can build websites now" — that part is already common and honestly isn't the interesting bit. It's because Webflow isn't just bolting another AI feature onto the Designer. They're rethinking what Webflow itself could become, and that changes the game for developers like me.

I haven't used it. This is me reading the announcement and thinking through what it means — one Webflow developer's reading, not a review. I could be wrong about a lot of this.

Source is a new platform that connects your codebase and your marketing stack into one shared environment. Instead of keeping code, visual development, CMS, hosting, marketing tools, and AI agents all separate, Source pulls them onto one surface.

The part I keep coming back to is the idea that code becomes the source of truth. Everything that ships — whether a human drags it in the visual canvas or an agent generates it — writes to the same underlying code. No abstraction layer sitting between the agent and what actually deploys.

The other new idea is something Webflow calls Views — each marketer, designer, and developer gets a workspace shaped around their specific job, all connected to the same underlying system. A marketer sees campaigns; a developer sees the codebase. Same project, different exits.

The biggest idea here isn't the technology. It's the shift in who can work on the same site at once.

Right now, building a site on Webflow mostly means one person in the Designer. If there's custom code, that's a different workflow in a different tool. If a marketer needs to change a headline, they're either poking around the Designer or waiting on the developer. Everyone's doing a different job in a different place, and the site is the only thing they share.

Source's pitch is that developers, designers, marketers, and AI agents all work on the same website through different interfaces — without everyone needing to understand the entire technical setup. That's a real change, and it's the first Webflow announcement that directly addresses how teams actually build and maintain sites, not just how one person builds faster.

This is the part I've been thinking about most, because I'm a Webflow developer who's also learning code — Next.js, Supabase, AI-assisted development — and Source makes the gap between visual development and traditional coding feel smaller.

Being fast in the Designer has always been the core Webflow skill. But if Source does what Webflow says — makes code the foundation, lets agents do more of the mechanical work — then being fast in the Designer might not be enough on its own anymore.

What gets more valuable is everything around the build:

• Structure — understanding how to organize a site or a CMS so it scales
• CMS architecture — knowing how collections and fields should be modeled
• Integrations — how your site talks to a CRM, analytics, or a backend
• Performance and SEO — the things that actually move a business
• Accessibility — the part most AI still gets wrong
• Custom code — knowing enough to work with the code Source puts front and center
• How AI agents fit into real workflows — where you trust them, where you verify them

Being the fastest person in the Designer used to be enough. As AI handles more of the mechanical build, the value shifts to everything around it — structure, judgment, and knowing where agents should and shouldn't get involved.

Source is still in a limited research preview. There are a lot of real questions no one can answer yet:

• How well does it actually work against real codebases (not a polished demo)?
• How much control do developers keep when an agent can write directly to the code?
• How do permissions and approvals work — what ships automatically versus needs sign-off?
• How does Git fit into the workflow? Do you see commits, branches, reviews?
• Where does Source end and normal Webflow begin — and what happens to the Designer we already know?

Webflow has been clear that the Webflow you know isn't going anywhere, and that there'll be a supported migration path when Source is ready. But "we'll give you a path" is a promise, not a product feature. I'll believe it when I see it.

I'm not treating Source as the future of Webflow yet. I'm treating it as Webflow telling us very clearly where they think that future is headed — and planning my own skills accordingly.

Here's the thing I keep landing on. Webflow isn't just adding AI to the Designer. They're rethinking what Webflow is — from a visual site builder into something closer to a platform where people and agents build together on real code. That's a much bigger bet than another AI feature, and it's the first time I've felt like the company is genuinely asking "what should this tool become?" instead of "what should this tool do next?"

For me, that changes my own roadmap. I'm not going to stop being a Webflow developer. But I'm going to keep learning the stuff Source puts front and center — code, structure, CMS architecture, and how AI actually fits into a real build. Not because I'm scared of being replaced, but because the work itself looks like it's about to get more interesting.

• Read the Source announcement and the code-as-source-of-truth post
• Sign up for updates or the research preview at webflow.com/source
• Watch the Webflow Conf 2026 keynote recap to see the full context
• Ask yourself: if an agent could handle your mechanical build work, what would actually be left for you — and are you good at it?