What is Source by Webflow?
Source by Webflow is a separate platform from the Webflow most people know, built so that marketers, designers, developers, and AI agents can work in one shared system. Webflow describes it as a way to launch, optimize, and scale digital experiences, rather than only to build them.
Webflow's argument is that AI has made it easy to create a site, but that creating is only one part of the job. The harder parts come after launch: knowing what to change, testing it, localizing it, and keeping it visible as buyers move to AI search. Webflow argues that existing tools haven't caught up with that continuous work.
A note on our experience: theCSS Agency is a Webflow Premium Partner, but we have not used Source ourselves. This guide relies on what Webflow has published and on credited reporting. Treat early claims about a preview product with care, including Webflow's.
What features does Source by Webflow have?
Source by Webflow has five main features, according to Webflow's announcement.
How much control do people keep over the agents?
With Source, teams decide how much autonomy agents get. Webflow says you can require human approval before changes ship, or allow more freedom for lower-risk work. Agent actions follow the same roles, permissions, and review systems as human work, and there is a record of what changed and who or what changed it.
How is Source different from Webflow?
The main difference between Source and today's Webflow is the foundation. Webflow's current platform has a visual abstraction layer on top of the code it generates, while Source treats code as the source of truth, and it gives agents direct access to that code.
Webflow says that code is the native language of AI, and that working with the real code lets agents understand a system, change it and evaluate their own work. In its FAQ, Webflow calls this a fundamental shift from how it has worked historically.
Is Source replacing Webflow?
No, Source is not replacing Webflow. Webflow says the existing platform isn't going anywhere, and that it will continue to invest in it, pointing to recent launches including MCP 2.0 and 2.1, native AEO agents and AI Code Components. It also says that if you choose to move to Source when it's ready, it will provide a supported path.
Some agencies are watching this closely. We-R, a Webflow agency, points out that software companies often shift attention and engineers toward their newest product over time. That's a reasonable long-term question, but it's speculation about the future. There's no sign of a shutdown of the current platform.
When will Source be available, and how much will it cost?
Source by Webflow has no public release date or price as of November 2026. It is in a limited research preview, and Webflow says it will enroll select agency partners and customers in phases over the coming months.
On pricing: We-R reports being told that pricing will be based largely on AI consumption, and notes that Webflow added AI credits to Workspace plans in May 2026. Webflow hasn't published this on its pricing page, so don't budget around it yet.
What else did Webflow announce at Webflow Conf 2026?
At Webflow Conf 2026, Webflow also announced Campaigns, Assets, MCP 2.1, Releases and auto-generated Agent Instructions. These matter more to most teams right now, because they're closer to the current platform. Details come from Ayko's and Diginomica's coverage, along with Webflow's pricing page.
Check the current status of each one, because many were announced as a beta or a future rollout. For more detail, see the Webflow MCP server guide, Webflow Cloud and Webflow AEO.
What should marketing teams do about Source right now?
Marketing teams should keep building on Webflow as normal, and spend their effort on things that stay useful on any platform. Don't delay a needed project, and don't architect around a product you can't use yet. This table shows what we would do in each situation.
What can you do now that will still matter if you move to Source?
You can prepare for Source by cleaning up the things that move with you to any platform: your content model, your components, your documentation and your measurement. Pravin Kumar, in an early guide, makes much the same case for building what's portable. Here's a practical list:
- Clean up your CMS. Give each field one clear purpose, use references rather than free-text categories, and use stable slugs. See Webflow CMS mastery.
- Name things properly. Components, classes and variables should make sense to a new person, or an agent, without explanation.
- Build a real component system. Reusable components are easier to maintain, and easier for agents to reuse safely. See Webflow component libraries.
- Write down your rules. Document your brand voice, approved claims, page patterns and SEO rules in a place people and tools can read.
- Decide what agents may do. List what can ship without review, and what always needs a person. Do this before you connect any agent to a live site.
- Fix your measurement. Agents suggesting tests are of little use without reliable conversion data. See Webflow Analyze and Webflow A/B testing.
- Make your content quotable for AI. Clear headings and direct answers help now. You can test any page with our free AEO analyzer.
- Keep your SEO records. A current list of URLs and redirects makes any future move safer. See the Webflow migration checklist.
- Try the current agent tools carefully. Using MCP on a staging site teaches your team a great deal about reviewing agent work, at low risk.
What questions should you ask before adopting Source?
Before you adopt Source, ask who reviews agent changes, how you undo a bad change, and what happens if you leave. We-R raises similar open questions. These are worth putting to Webflow or your partner:
- What will it cost, and how predictable are AI usage costs?
- Who owns the code, and can you take it with you if you leave?
- How do you roll back a change that looks fine but breaks tracking or SEO?
- How do external developers work in the same repository?
- Which security and compliance certifications apply during the preview?
- What's the supported path from your current Webflow site, and what doesn't transfer?
- How are redirects, schema and metadata handled in a move?
What does "Source" mean for agencies?
For agencies, "Source" could mean larger projects and new services, because it works directly with real code and existing stacks. Webflow says agencies can take on technical builds they would previously have declined, work with clients without asking them to move to Webflow's CMS first, and create custom Views that they can reuse and sell.
Webflow is also pitching agencies as AI consultants to their clients. The CEO of Flow Ninja, a Webflow agency, is quoted in the announcement supporting the product, and Webflow says it has been building Source with agency feedback.
What this means for you, if you are hiring an agency:
- Ask how they use AI today, and how they review the output. That's a better signal than whether they have access to Source.
- Be careful with "Source experts." The product is in limited preview, so few people have real experience with it, and that includes us.
- Keep hiring for fundamentals. Structure, SEO, conversion and migration experience all carry over.
Compare options in our list of the top Webflow development agencies, and read how AI is changing Webflow development. If you have a project to plan now, our Webflow development agency can help you build it in a way that doesn't depend on what ships next.
FAQs
1. What is Source by Webflow?
Source by Webflow is a new platform for marketing teams and AI agents to launch, optimize and scale websites together. Webflow announced it at Webflow Conf in September 2026. It uses code as its foundation, offers a visual canvas and role-based Views, and can connect to your existing stack.
2. Is Source by Webflow available now?
Source by Webflow is available only through a limited research preview as of November 2026. Webflow says it will enroll select agency partners and customers in phases over the coming months. You can apply using the form at webflow.com/source, and no general release date has been published.
3. Will Source replace Webflow?
No, Webflow says Source won't replace its current platform, and that it isn't going anywhere. Webflow says it will keep investing in the existing product, and will offer a supported path if you choose to move to Source later. Webflow's advice to current customers is to keep building as usual.
4. What happens to my existing Webflow site?
Nothing happens to your existing Webflow site because of Source. Webflow says to keep building as you have been, and that a move would be your choice if and when Source is ready for you. Webflow also says Source can connect to sites you've already built in Webflow.
5. What is the difference between Source and Webflow?
The main difference is that Source uses code as its foundation, while Webflow's current platform is centered on a visual Designer that generates code. Source also adds role-based Views, built-in agents and the ability to connect to your existing codebase and tools.
6. Can Source work with my existing CMS and tech stack?
Yes, Webflow says Source can connect to your codebase, CMS, hosting and marketing tools, including sites already built in Webflow. You can also use more of Webflow's own stack, including its next-generation headless CMS. Real-world fit is hard to judge while it's in preview.
7. Should I wait for Source before building a new website?
No, you should not wait for Source if you need a new website now. It has no release date or public price, and Webflow's current platform remains fully supported. Build on what's available today, with a clean content model and components, so your work stays useful later.
