What is Source by Webflow?

Source by Webflow is a new platform that brings visual website editing, AI agents and a team’s existing tools into one workspace. Webflow announced it at Webflow Conf on 2 September 2026, and it’s currently in a limited research preview. Source announcement.

I’ve applied for access, so I’m looking at this from what Webflow has published so far. There’s enough there to be interested, particularly in how a marketing team could keep working on a website after the initial build. Everything below is sourced from Webflow’s own pages, and each figure says where it came from.

How does Source work?

Source works on the code behind a website, and everyone works on that same code. A developer edits it directly, an editor makes a visual change on a canvas, and an AI agent drafts a change. All three write to the same files.

That’s a bigger shift than it sounds, and Webflow explained why in an engineering post on 4 August called Getting to the Source. When you design in the Webflow you know today, you’re editing an internal representation of your site, which Webflow’s systems then compile into the HTML, CSS and JavaScript that browsers run. The canvas is a rendering of that internal format. Getting to the Source.

Webflow’s own words for the problem: any system with two representations of the truth, joined by a translation layer, will drift. Their answer is to rebuild around code as the source of truth. Code as the canonical artefact, the thing the canvas renders, the thing agents manipulate, the thing you own.

For me, the useful example is a campaign page. The marketing team needs to change the message, add a section and get it reviewed. The developer needs the components to remain maintainable. If Source can make both sides of that handover easier, that’s something I’d be keen to use.

What are Views?

Views are the part of the announcement aimed at the people rather than the code. Webflow describes them as a new primitive: every marketer, designer and developer gets a workspace tailored to their role and the outcomes they own. Out of the box there are Views for visual site building, content management, assets and optimisation, and a team can build custom ones, such as a dashboard for the metrics it cares about or a View built around its own content approval process. Source product page.

Each View is governed. Brand systems, role-based access, approval paths and audit trails are built in from day one, according to the product page. That’s the bit an enterprise marketing lead should read twice, because it’s the answer to “what stops someone breaking the homepage”.

What do the agents actually do?

Webflow describes the agents as background teammates rather than a chat box. They monitor performance and flag opportunities in a Source inbox, an AEO fix or a CRO test worth running, with the work already drafted and ready for review. You can leave a comment on the canvas, such as “update this button to match the new brand colours”, and an agent picks it up, drafts the change and flags it for approval. Teams can also create agents scoped to one job, like checking every new page for brand voice before it ships. Source product page.

How much freedom they get is the team’s call. Webflow’s FAQ says teams can require human approval before changes ship, or give agents more room on lower-risk work. Either way, agent actions are governed by the same roles, permissions and review systems as human work, with a record of what changed and who, or which agent, made the change.

I think that’s the right design. Agents on a live site have been able to make changes for a while. The missing piece has been a record that tells you afterwards what they changed and why, and that record is what Source is promising.

Why is Webflow building Source?

AI tools have made it much easier to generate a first version of a page. Once more people start working on it, you need to know which changes are approved, whether the design is still consistent and what has actually gone live. Webflow’s announcement puts almost all of its attention on that ongoing work: scaling what works, knowing what to change, shipping campaigns and localising across markets continuously rather than at launch. Webflow Conf announcements.

There’s also a number in the engineering post that explains the timing. Webflow says over 30% of its enterprise customers are already running agents against production Webflow sites, and that figure has grown roughly four times since January. The demand for agents on live sites arrived before the tooling to govern them did. Getting to the Source.

I think that makes sense for where Webflow already sits. Marketing teams use it because they want control over their websites. As more of the work involves AI, that control needs to extend to what the agents can do as well.

What does this mean for the future of Webflow?

My expectation is that Webflow will take on more of the work around running a website. Source’s announced direction includes connecting existing tools and helping teams review and improve what they’ve published. That gives it a much wider role in the marketing team’s week.

For agencies, I think a well-built component system will become even more useful. Give a team a clear set of sections, sensible editing controls and an agreed brand system, and there’s a structure for people and agents to work within. One of the agency quotes on Webflow’s page names Next.js and Astro clients specifically, which matches how we build, and I’d expect the quality of that setup to make a noticeable difference to the result.

I’m also interested in whether Source can reduce the back-and-forth around small changes. An agent drafting an update inside the right component, ready for someone to review, could be very handy. We’ll need to use it on real work to see how much it helps.

What about enterprise security?

Webflow has an established security programme, including SOC 2 Type II and ISO 27001. For a company already considering Webflow, that gives its security team a supplier record to assess. Webflow security.

I’d still want the documentation that applies specifically to Source before recommending it for an enterprise project. Existing Webflow certifications don’t automatically tell us how every connected service or preview feature is covered. Permissions, data handling and support all need to fit the company using it.

What happens to existing Webflow websites?

Webflow says the platform you know isn’t going anywhere, and that it will keep investing in it, including expanding what agents can do there. The same-day launches back that up: Releases lets a large team branch and stage a whole site before anything goes live, and MCP 2.1 gives agents access to GSAP interactions, deeper CMS querying and deploy logs. Webflow also says there will be a supported migration path when Source is ready for a team that wants to move. Webflow’s Source FAQ.

I wouldn’t put a useful website improvement on hold while waiting for the preview. If your team needs a better CMS structure or a campaign page it can manage, we can work on that with the tools available today, and it will carry across. Our Webflow Enterprise service covers that ongoing work.

Can you use Source yet?

As of 9 September 2026, access is limited. Webflow is enrolling selected agencies and customers in phases, and you can apply through the Source preview form.

Once we get access, I’d like to try an ordinary editing job first: update an existing page, get another person to review it and publish the approved version. Then the awkward cases, such as two people editing the same component, a restricted publisher trying to go live, and rolling a release back. That’s the sort of work a marketing team needs to feel comfortable doing every week, and it’s what I’ll write up next.