Webflow started metering its own AI features in 2026. As of June 29, every Workspace plan has a fixed monthly or yearly pool of AI credits, and running an AI Assistant prompt, an AI-generated section, or an AEO audit now draws from that pool instead of feeling unlimited. If you build on Webflow, or you’re deciding whether to, this changes how you budget for the platform, not just how you use it.
What Actually Changed, and When
Webflow added AI credits to every Workspace plan on May 13, 2026, alongside a broader pricing simplification: a new Team plan, a Premium Site plan that folds the old CMS and Business tiers into one, and a usage dashboard so workspace owners could watch their AI spend before it meant anything. For about six weeks, that dashboard just tracked usage. Nothing was blocked.
That changed on June 29, 2026. From that date, any feature that consumes AI credits counts against your plan’s included allotment, and workspace owners and admins get notified as they approach and hit the limit. If you’re on a legacy Freelancer or Agency workspace, or an older Site plan, the new structure doesn’t apply retroactively. It takes effect at your next renewal or billable plan change on or after November 16, 2026, which gives existing customers a real window to plan around rather than getting hit mid-cycle.
How the Credit Pool Actually Works
Credits are pooled at the workspace level, not per site. That matters if you run several Webflow sites under one workspace, including Starter sites that don’t carry their own paid Site plan. Every AI action anywhere in that workspace draws from the same shared pool.
Here’s the allotment by plan, straight from Webflow’s own help documentation:
| Workspace Plan | AI Credits | Reset Cycle |
|---|---|---|
| Starter | 200 / month | Monthly |
| Core / Freelancer | 300 / month | Monthly |
| Growth / Agency | 400 / month | Monthly |
| Team | 100,000 / year | Annual |
| Enterprise | Custom (contact Webflow) | Custom |
Unused credits don’t carry over. Self-serve plans reset monthly, Team and Enterprise reset annually, and whatever’s left on the table at the end of a cycle is just gone, not banked for a heavier month later. If a workspace runs out before the reset, Webflow doesn’t auto-upgrade the plan or lock you out of the whole site. AI-specific features stop working until you either buy an add-on credit pack or wait for the next cycle. Everything else, the Designer canvas, CMS editing, publishing, hosting, keeps running exactly as before. Credits also carry no cash value and can’t be redeemed for anything outside Webflow’s own AI tooling.
What Actually Burns a Credit?
This is the part worth getting precise about before you assume the worst. Ordinary site-building in Webflow, dragging elements in the Designer, building CMS collections, setting up Interactions, publishing changes, none of it touches your AI credit pool. The meter only runs on AI-specific features: the AI Assistant chat, AI-generated sections and layouts, AI code components, and AEO (answer engine optimization) site audits. One freelance consultant who tracked their own usage reported AEO audits running 8 to 12 credits per full-site scan, AI section generation around 4 to 6 credits per section, and roughly 1 credit per AI Assistant chat turn. Webflow hasn’t published official per-feature costs, so treat those as a real-world data point rather than a guaranteed rate, but they’re useful for sizing up whether a 300-credit monthly allotment is generous or tight for how your team actually works.
Does This Change Whether Webflow Is the Right Platform?
Not by itself, but it does change what “choosing Webflow” now means financially, and that’s worth sitting with if you’re comparing it against WordPress or a custom build. On WordPress, if you want AI features, you’re usually wiring in your own API key, whether that’s through a plugin or a custom AI integration, and you pay that provider directly for what you actually use. There’s no workspace-wide pool shared across every site you run, and no plan tier that quietly caps how much AI help you’re allowed before you have to buy more.
Webflow’s model bundles AI usage into the subscription instead, which is simpler to budget for in one sense (it’s a flat number on your invoice) and less flexible in another (you can’t choose a cheaper or more capable AI provider, and heavy AI use on a Starter workspace now has a real ceiling). Neither approach is wrong. A marketing team that leans on the AI Assistant daily to draft copy variations and rebuild sections is going to feel 200 or 300 monthly credits a lot faster than a dev-led team that treats Webflow as a design and CMS tool first, and barely touches the AI panel at all.
That second pattern is closer to how we actually build in Webflow day to day. When we put together an AI SaaS marketing site as an internal reference build, the animation, the Interactions setup, and the feature sections all came out of Webflow’s native Designer and Interactions panel, not its AI tooling. None of that would have touched a credit pool even under the new rules. If your team’s Webflow work looks more like that, structured CMS collections, hand-tuned Interactions, custom class systems, the credit system barely registers. If it looks more like “describe a section and let AI build it” on a regular basis, it’s worth actually checking your workspace’s usage dashboard before you assume the included allotment covers you.
What to Actually Do About It
- Check your workspace’s AI usage dashboard now, even if you’re not near the limit yet, so you have a baseline before enforcement affects a real project deadline.
- If your team uses the AI Assistant or AI section generation regularly, work out whether a Team plan’s annual pool is a better fit than restarting the clock every month on a self-serve tier.
- If you’re on a legacy Freelancer or Agency workspace, mark your renewal date. The new structure applies at your next renewal or billable change on or after November 16, 2026, and that’s a better time to review usage than after it’s already capped.
- Budget an add-on credit pack as a real line item if your team is consistently AI-heavy, rather than treating an occasional overage as a surprise.
- If most of your team’s value from Webflow comes from the Designer, CMS, and Interactions rather than the AI panel, don’t let this change your platform decision at all. It doesn’t touch any of that.
FAQ
Do unused Webflow AI credits roll over to the next month?
No. Self-serve plan credits reset monthly and Team or Enterprise credits reset annually, and whatever’s unused at the end of a cycle expires rather than carrying forward.
What happens if my workspace runs out of AI credits?
Webflow doesn’t lock you out of your site or auto-upgrade your plan. AI-specific features stop working until you buy an add-on credit pack or wait for the next reset. Regular building, publishing, and hosting are unaffected.
Are AI credits shared across all the sites in my workspace?
Yes. Credits are pooled at the workspace level, not assigned per site, so every site under that workspace, including Starter sites, draws from the same pool.
Does switching to WordPress avoid AI costs entirely?
Not entirely, but it changes who you’re paying and how. On WordPress or a custom build, you typically connect your own AI provider and pay that provider directly for usage, rather than drawing from a workspace-wide credit pool with a hard monthly or yearly cap.
When does the new credit structure apply to older Webflow workspaces?
For workspaces on legacy Freelancer or Agency plans, or older Site plans, it takes effect at the next renewal or billable plan change on or after November 16, 2026, not immediately.
Sources
Facts and dates in this post are drawn from Webflow’s own documentation and announcements:
