Explainer · Webflow Localization
Webflow Localization Doesn't Support Ecommerce: The Gap, Explained
Webflow Localization is a good tool with one decisive limitation: it does not work with Webflow Ecommerce sites. If your Webflow site sells products, the platform's own multilingual feature stops at the store's edge. This page explains what Localization is, exactly where the exclusion cuts, and why it matters more than it first appears.
What Webflow Localization is
Localization is Webflow's built-in way to publish a site in multiple languages: translated pages and CMS content, locale-specific subdirectories, and a language switcher, all managed inside Webflow. It is a paid add-on priced per locale — roughly $9–12 per locale per month on the Essential plan and $35 on Advanced, at published pricing checked in November 2026.
For portfolios, agencies, SaaS marketing sites and blogs, it is the obvious first choice, and usually the right one. Nothing in this article argues otherwise.
Where the line is drawn
The exclusion is about site type, not content volume. Webflow Ecommerce — the product catalog, collection pages, product pages, cart and checkout — is not supported by Localization. A store owner can localize the marketing pages around the shop ("About", "Journal", a landing page) while the shop itself, the part that takes money, stays in one language.
That produces a strange half-localized experience: a French visitor reads your story in French, clicks through to the product, and lands back in English at the exact moment they were about to buy. Stores report this pattern constantly, because the break happens at the worst possible step of the funnel.
Why stores feel it most
Three reasons the exclusion hits ecommerce harder than any other site type:
- Stores are the sites that sell across borders by default. A local plumber needs one language; a store shipping to the EU needs four on day one.
- The catalog is the content. On a regular site, the untranslated remainder is a few pages. In a store, the untranslated remainder is every product — the majority of the site's indexable, revenue-carrying pages.
- The fallback tools fit stores worst. JavaScript switchers don't create indexable language pages, and word-priced translation tools charge stores the most, because catalogs are word-heavy and multiply across languages. We break down that math in the Weglot alternative guide.
What store owners do instead
Today the realistic menu is: pay a word-metered third-party tool; accept a switcher widget that visitors see but Google mostly doesn't; duplicate the site by hand and maintain every product twice (or four times); or stay single-language and leave the foreign traffic unconverted. Our Webflow ecommerce multilingual guide walks through each option, and the step-by-step translation guide shows what a correct setup has to include regardless of tooling.
The gap is also why we're running the LocalePress presale: a store-first service — bulk catalog translation plus localized URLs, hreflang, sitemap and translated metadata, priced by catalog size. It's being validated before it's built: at least 5 refundable $15 founder pre-orders by December 7, 2026, or it doesn't happen and everyone is refunded automatically.
FAQ
What exactly of my store is not covered by Webflow Localization?
The ecommerce layer: product pages, collection pages, cart and checkout. Regular pages and CMS content on the same site can be localized; the store itself cannot.
Is Webflow Localization free?
No. It is a paid add-on priced per locale — around $9–12 per locale per month for Essential and $35 for Advanced, at published pricing checked in November 2026. The price is not the problem for store owners; the ecommerce exclusion is.
Will Webflow add ecommerce support to Localization later?
We don't know, and neither does anyone outside Webflow. Store owners who need multilingual sales now have to choose among today's options rather than a roadmap hope.