What Webflow's June 29 AI Credit Limits Will Actually Cost Your Studio

How Did We Get to AI Credit Limits Inside Webflow?

I spent most of last Friday on the phone with two retainer clients who saw the new AI Credits dashboard inside Webflow and panicked. One of them had already burned through 240 credits in three weeks experimenting with the AI Assistant inside the Designer. The other had not looked at it at all and assumed her plan was unlimited. Both calls ended the same way, with me opening a spreadsheet and walking them through what June 29 actually means for their site bill.

Webflow added AI credits to every Workspace plan on May 13, 2026, but enforcement starts June 29, 2026 according to Webflow's official pricing update post. That gives studio owners exactly four weeks to figure out how their team uses credits, what overage will cost, and whether the included pool covers a real working month. If you bill flat retainers the way I do, the answer matters more than you think.

I want to walk through what I learned auditing eight client Workspaces this week, where the credits actually go, what the add-on math looks like, and the three changes I made to my retainer template before I sent out invoices for June.

What Is a Webflow AI Credit and What Burns It?

A Webflow AI credit is the unit of metering Webflow now applies to every AI-powered action inside the Designer, CMS, and Workspace tools. Each AI Assistant message, AEO answer audit, Gemini translation, and AI-generated section costs credits at different rates published in the Workspace settings page.

The Starter plan ships with 200 credits per month, Core ships with 300, and Growth ships with 400. Freelancer Workspace gets 300 and Agency Workspace gets 400. That detail matters because the Freelancer plan I have been on for two years now gives me the same monthly credit pool as a paid Core plan does, which is not how I expected the math to land.

The most expensive actions in my testing have been AEO audits at 8 to 12 credits per full-site scan, AI section generation at 4 to 6 credits per section, and Gemini-powered translation runs at 1 to 2 credits per page depending on word count. The AI Assistant chat itself is cheap, about 1 credit per turn. So if you spend a working morning generating layouts and running AEO audits, you can vaporize a Starter plan's monthly allotment before lunch.

Why Does June 29, 2026 Matter More Than the May 13 Rollout?

June 29 is the day credit limits become hard caps. Until then, the dashboard tracks usage and shows overage, but Webflow does not block actions. After June 29, if you run out of credits, the AI tools stop working in your Workspace until you buy the add-on or wait for next month's reset.

Webflow's pricing post confirms the add-on price: 2,000 credits per month for $20 per month, billed yearly. That works out to one cent per credit. Single-page AEO audits cost about ten cents in overage. A weekly site-wide AEO scan plus daily AI section experiments would run a studio about $40 to $60 in overage on top of the base plan.

For existing legacy plans, enforcement does not hit until November 16, 2026. So if your site is on the old CMS plan that Webflow is sunsetting, you have until your next renewal after that date before any of this applies to you. I checked all my client Workspaces and roughly half are in this longer window, which gave me breathing room on those engagements.

How Much Will Real Studios Actually Spend on Add-Ons?

For a one-person Webflow studio running three to five active client sites, my audit suggests 600 to 1,200 credits per month is the realistic working range if you use AEO features once per week per site. That is well above the 300 credit Freelancer allotment, which means an extra $20 per month or roughly $240 per year in overage credits per studio.

The math gets uglier if you bundle AI work into client retainers without re-pricing them. I run six retainers at fixed monthly fees that I quoted in February 2026 before any of this existed. If I absorb a $20 monthly add-on charge per client because I use AEO scans on their behalf, I am writing off $1,440 of annual margin without doing anything wrong. That is the number that pushed me to send the email I sent on Saturday.

For agency teams the math is different but worse in absolute terms. A four-person Agency Workspace gets 400 credits combined. If each designer runs even one AI section generation per day, the team will hit the cap in the first ten days of the month. The 2,000 credit add-on covers it but you are stacking $20 monthly add-ons depending on team size, which is structurally different from the unlimited-Assistant feel of the prior plan.

What Did I Tell My Retainer Clients to Do This Week?

I told them to do three specific things before June 29, in this order. First, open the AI Usage dashboard inside their Workspace settings and look at the last 30 days of activity to see whether anyone on their team is already a heavy user. Second, decide whether AI Assistant and AEO scans are part of their workflow or mine, because that determines whose Workspace is consuming credits. Third, agree with me in writing on what the new retainer line item for AI usage looks like starting July invoices.

For the two clients I run AEO audits for monthly, I added a flat 1,500 rupee per month line called AI Tooling and AEO Audit to their retainer. That covers my Webflow add-on cost, the Claude Opus 4.8 API time I burn doing the deep analysis, and the report I deliver them. It is transparent, it is small enough not to fight over, and it reframes AI as a billable input rather than a hidden overhead.

Is the Premium Site Plan Worth It Just for the AI Allotment?

No, the Premium Site plan that Webflow rolled out in May 2026 bundles former CMS and Business features into one Site plan tier but does not include extra Workspace AI credits. Workspace credits and Site plans are billed separately. If you upgrade a single site from CMS to Premium, your Workspace still has the same credit pool it had yesterday.

This is one of the most common misreadings I have seen on Webflow forums in the last week. People assume that paying more per site unlocks more AI. It does not. Workspace plans are the only lever for AI credits. If you want more AI without overage, you upgrade the Workspace, not the Site. I covered the broader Premium Site math in my earlier write-up on the Webflow Premium plan rollout if you want the full plan-by-plan comparison.

How Should You Track AI Credit Burn Before Enforcement Starts?

Open the AI Usage dashboard in your Workspace settings every Friday for the next four weeks. Webflow's dashboard shows per-tool breakdowns: how many credits AI Assistant consumed, how many AEO Audit consumed, and how many translation runs cost you. Snapshot the numbers and label each Friday. By June 29 you will have four data points that show your real burn rate.

If your weekly burn is under 50 credits, you are safe on any plan including Starter. If it is between 50 and 100, plan on the add-on. If it is over 100, either re-architect which Workspace owns the AI work or move that work outside Webflow entirely, into Claude or ChatGPT for drafting and only paste into the Designer when ready. I prefer the second pattern for my own studio because the model quality is better and the credits last longer.

What About AEO Specifically? Should You Stop Running It?

No, AEO is still the cheapest way to measure how AI search treats your content, and the credit cost is small relative to what you learn. A site-wide AEO audit on a 40-page Webflow site costs about 10 credits in my testing. That is one tenth of a Starter plan's monthly pool for a complete map of how your content is being parsed.

I run AEO audits monthly on retainer clients, not weekly, and that pace is enough to catch drift. The signal-to-cost ratio is good. If you want to layer in deeper analysis on top, I send the AEO export into Claude Opus 4.8 with a prompt that finds the lowest-citation pages and proposes rewrites. That happens outside Webflow so it does not touch credits at all. I wrote up the broader approach in my piece on tracking AI visitors in Webflow Analyze.

How Do You Roll This Conversation Into Your Retainers This Week?

Send your retainer clients a short email by Thursday, June 4. Tell them Webflow is metering AI features starting June 29, that you have audited their Workspace and know how many credits their site consumes per month, and that you are proposing a small monthly line item to cover the cost. Send the proposed amount and offer to skip it if they prefer to handle the add-on themselves. Most clients will say yes to the line item because the alternative is more setup work for them.

If you do not yet bill retainers and you are still on per-project pricing, add a one-line AI tooling note to every new proposal starting today. Two sentences is enough: AI tooling and AEO monitoring are billed at cost, currently around 2,000 credits per month. Clients sign things that mention numbers and timelines because they signal that you have done the research.

How to Get Ahead of This Before June 29

This week, open every Workspace you touch and look at AI Usage. Note the numbers. Decide which client work happens in their Workspace versus yours. Draft the email that explains the new line item. Send it by Thursday so you have a week of buffer before the cap activates. If you bill flat retainers, my advice is to add the AI line as a fixed monthly amount, not a pass-through, so you absorb small fluctuations and avoid invoice surprises.

For the deeper context on how Webflow's whole pricing structure shifted in May, my earlier note on the May 2026 pricing reset covers what changed across Site plans and Workspaces. And if you want the AEO foundation that makes credit spend worthwhile, my walkthrough on adding organization schema for AI is the cheapest possible foundation to put under any AEO scan.

If you want help auditing your Workspace credit usage or rewriting your retainer template for the new metering reality, I am happy to walk through it with you. Let's chat.