Priced Out of Webflow: The Localization Math Nobody Shows You
An agency prices a five-language site on Webflow and finds the languages cost nearly six times the hosting: $29 per locale per month, capped at ten. Here is the per-locale math worked all the way through — Webflow, Framer, and what the same quote looks like on a platform that refuses to meter languages.
The quote that kills the deal
A client in Brussels wants a marketing site in Dutch, French, German, English, and Spanish. Nothing exotic — five languages is a Tuesday in Belgium. You scope the build, open Webflow’s pricing page to price the hosting, and spot Localization among the add-ons: from $9 a month. Fine. You pencil it in and keep scrolling.
Then you read the configurator. That $9 is per locale, per month, on Localize Essential — and Essential is capped at three locales. Your client needs five. Five means Localize Advanced at $29 per locale per month, capped at ten. Five times $29 is $145 a month. Before hosting. Before the plan that actually serves the pages.
Your job now is to explain to a client who asked for a brochure site why the translations — words they already paid a human translator for — carry a $1,740-a-year platform surcharge. The translation isn’t the expense. The permission to publish it is.
And that line item recurs. $145 a month is $1,740 a year, every year the site stays up — $5,220 over a three-year life. For plenty of five-language brochure sites, the localization meter alone eventually outbills the site build. Nobody puts that slide in the pitch deck.
The per-locale math, worked
Here is the full quote, priced from Webflow’s own pricing page as of July 12, 2026, and matching Tunel Studio’s independent worked example of the same five-locale scenario.
Read the shape of that bill. The metered unit — locales — is 85% of the total. The website is the rounding error.
And the caps put a ceiling on the math. Three locales on Essential. Ten on Advanced. An eleventh language moves you to Enterprise, where the prices aren’t printed. If you’re an agency quoting multilingual work on Webflow, four numbers deserve a spot in your estimate template:
The cap, not just the rate. $9/locale stops at 3 locales; $29/locale stops at 10.
Machine translation is also metered. 10K words per locale per month on Essential, 50K on Advanced.
Billing period. Premium is $25/mo billed yearly — $39/mo billed monthly.
Bandwidth. Premium now includes 50GB; each additional 50GB runs $20/mo billed annually.
May made the baseline worse
The hosting line in that quote is the new, post-restructure number. On May 13, 2026, Webflow simplified its plans and updated its pricing: the CMS and Business plans were folded into a single Premium plan, Basic’s monthly price went from $19 to $25 — a 32% jump — and Premium’s $39 monthly rate landed 35% above the old CMS monthly rate. The quiet change was bandwidth: Premium includes 50GB, down from the 100GB the plans it replaced had offered.
NoCode.Tech documented one user with a 400GB-bandwidth site whose annual bill jumped from $476 to north of $2,000 — a 320% increase. The r/webflow threads from launch week tell the story in their titles: “New pricing effective today — my bill jumped 320%” and, simply, “I’m done. Where is everyone going?”
Localization pricing predates all of this, and none of it touched the per-locale rate. The thread on Webflow’s own forum titled “Localization is WAY too expensive!” has been accumulating agreement since long before May. It is still accurate.
Why locale caps exist
Ask the engineering question: what does a locale cost Webflow to serve? A localized page is rows in a database and a branch in a router. Serving /fr/pricing costs roughly what serving /pricing costs — a little more storage, a little more bandwidth. Both of which are already metered and billed. The $29 isn’t recovering a cost. It’s doing something else.
The something else has a name in pricing strategy: a segmentation fence. You find a unit that costs you approximately nothing but correlates tightly with the customer’s budget, then you meter it. Businesses that need five languages skew bigger, better funded, and more locked in than businesses that need one. The locale count isn’t measuring load on anyone’s servers. It’s measuring the size of your ambition, and billing it.
The caps are the tell. If $29 per locale covered a real cost, there would be no reason to stop selling at ten — every locale would be profitable, so sell eleven. The cap exists to force growing customers into a sales conversation where the fence can be rebuilt at a higher altitude. That’s not a conspiracy theory; it’s just what the pricing page says, read twice.
There is a simple test for whether a meter is honest: does the unit show up on the platform’s own bill? Bandwidth does — someone pays for every gigabyte that moves. Storage does. Languages, seats, and locales do not. When a pricing page meters a unit its own cloud provider has never heard of, you’re not looking at cost recovery. You’re looking at a fence.
Framer runs the same play
Framer’s localization is $20 per locale per month (as of July 12, 2026). A cleaner number, same meter: five locales is $100 a month before the site plan.
And there’s a compounding trap. According to letaiworkforme’s February 2026 teardown of Framer’s pricing, CMS items count against your item cap per locale — a 2,000-item collection in English and Spanish counts as 4,000 items. Localizing your content spends a second meter you thought you’d already paid for. Framer’s community has a request thread politely titled “Rethink Localization Pricing.” We admire the restraint.
Worked the same way as the Webflow quote: Framer’s Pro plan is $30 a month, so a five-language site lands at $130 a month — $1,560 a year — with the locale line making up 77% of it. Different platform, same shape of bill.
What the quote looks like without the meter
We built StoryPress on the other answer. $5 a month, billed $60 yearly. We meter the things that actually cost money — bandwidth and storage — with sensible caps printed in plain sight. We refuse to meter artificial units: languages, seats, locales. A language isn’t a resource; it’s your content, stored in storage we already meter and served over bandwidth we already meter. Charging per language would be charging you twice for the same bytes.
Our native CMS is arriving imminently with first-class language support and no cap on the number of language variants. That’s not “unlimited everything” — the real meters stay, honestly labeled. It’s a refusal to invent a fake one.
So: the five-language Brussels quote from the top of this post, on StoryPress, is $5 a month. The sixth language is $5 a month. The eleventh — the one that triggers an enterprise sales call on Webflow — is still $5 a month. We walk through the full reasoning in why StoryPress doesn’t count languages, and we rank every major platform’s language pricing in the CMS language pricing index 2026.
What the $5 actually covers
A fair question at this point: what kind of website is $5 a month? Not a teaser tier. StoryPress is a managed CMS and hosting on Cloudflare’s edge — visual editor, a universal component system, and the checklist items agencies usually bill hours for wired in by default: SEO metadata, JSON-LD, sitemaps, Open Graph tags, llms.txt, cookie consent, and GTM.
There are no plugins to patch, so there’s no maintenance retainer to sell your client — or to eat when they decline it. Your content is fully exportable, so the exit door stays unlocked. And there’s an MCP server, so AI agents can edit the site conversationally when you’d rather delegate the Tuesday tweaks.
The math, in one place
Webflow Localize Essential: $9/locale/mo, capped at 3 locales (webflow.com/pricing, as of 2026-07-12).
Webflow Localize Advanced: $29/locale/mo, capped at 10 locales; beyond 10 is Enterprise.
Five locales on Webflow: $145/mo for localization + $25/mo Premium hosting = $170/mo, $2,040/yr.
Webflow’s May 13, 2026 restructure: Basic monthly $19 → $25 (+32%); Premium $39/mo monthly, +35% over the old CMS monthly rate; included bandwidth cut to 50GB (NoCode.Tech).
Documented post-restructure bill jump: $476/yr → $2,000+/yr (320%) for a 400GB-bandwidth site.
Framer localization: $20/locale/mo (framer.com/pricing, as of 2026-07-12); CMS items count per locale against item caps, per letaiworkforme.
StoryPress: $5/mo (billed $60/yearly); languages uncapped and unmetered; bandwidth and storage metered with plainly labeled caps.
If the per-locale line on your next estimate makes you wince, get started with StoryPress — the quote stays one line long. Still doing comparative math? The language pricing index and why we don’t count languages have the rest of the receipts.
The Meter Is Dying: A Short History of Paying Per Seat
On July 12, 2026, Netlify stopped charging for seats. The explanation fit in one sentence: “Seat pricing made sense for us when software was written by a handful of developers.” It reads like an epitaph — and it closes an argument the software industry opened in 1969, the argument about what unit software should be billed in. So here is a short history of the meter: the CPU-second, the core, the seat, the locale. Each one made sense in its era's cost structure. Each one outlived it.
Google Kept the Answer. You Kept the Hosting Bill.
Google now answers the question before anyone reaches your website, and your traffic graph has noticed. Here is the part the panic posts skip: the visitors who still arrive are converting better than ever, and the game has quietly changed from ranking to being cited.