Webflow localization tools start at $9 a month per locale for Webflow's own Localize Essential add-on, so a three-language site pays $27 a month for the software, according to Webflow's pricing page and its own roundup of localisation services, both read on 7 November 2026. That is the cheap number. The expensive one is review: at the €0.13 a word Weglot quotes for professional translators, a 60-page site in three languages costs about €7,000 before anyone opens Webflow.
This roundup covers six ways to localise a Webflow site: the native add-on, the two proxy services most often paired with Webflow, the Marketplace translation apps, a manual route through native locales, and the folder-per-language build. For each, it shows how the tool touches the site, what it does to URLs, and what a 60-page site pays at three and ten languages, with prices from each vendor's pricing page.
Which Webflow localization tools exist, and how each one touches the site
The useful split is not by brand but by where the translated copy lives and who serves it. Webflow Localize keeps every locale inside the Designer and the CMS. Proxy services keep translations in their own dashboard and serve them from their own edge. Translation management systems sit on top of Localize and push copy into it. The manual routes use no translation software at all.
| Route | Who serves the translated page | Where copy is edited | Needs the Localize add-on | Translated slugs | Paid from |
|---|---|---|---|---|---|
| Webflow Localize (native) | Webflow | Designer and CMS, per locale | It is the add-on | Advanced and Enterprise | $9 per locale a month |
| Weglot | Weglot's servers, via script and DNS | Weglot dashboard | No | Pro and above | €15 a month, free to 2,000 words |
| Linguana | Linguana's CDN, via DNS | Linguana dashboard | No | Every plan | $25 a month, free to 2,000 credits |
| TMS apps (Crowdin, Lokalise, Phrase, Smartling, others) | Webflow | The TMS, synced into locales | Yes | As per Localize tier | Crowdin from $59 a month, plus the add-on |
| Manual into native locales | Webflow | Designer and CMS, pasted by hand | Yes | As per Localize tier | $9 per locale a month |
| Folder per language, no add-on | Webflow | Duplicate pages and Collections | No | Yes, by hand | $0 |
Sources: Webflow pricing page, Webflow Marketplace, Weglot pricing, Linguana pricing, Webflow blog roundup of localisation services, all read 2026-11-07
A native locale at /fr/ and a Linguana subdirectory at /fr/ look identical to a visitor. The difference appears in month three, when a marketer edits the English pricing page and asks where the French one is.
Native Webflow Localize: what each tier buys
Webflow's pricing page lists Localize Essential at $9 a month "based on # of locales", with up to three locales and 10,000 AI-translated words per locale per month. Localize Advanced is $29 a month on the same basis, with up to ten locales, 50,000 words per locale per month, and three features Essential lacks: asset localisation, localised URLs and automatic visitor routing. Webflow's own roundup spells out the basis: "from $9 per month per locale for the Essential tier and $29 per month per locale for Advanced". Enterprise adds per-locale element visibility, and the $2,500 a month Team site plan bundles Localize with two locales.
Inside the Designer, a locale is a view: you switch to it and override text, images, styles and SEO settings, or let AI translation fill it first. Webflow's feature page lists subdirectory URLs, localised metadata, a sitemap with hreflang tags and a locale selector element as standard. Webflow University's Localize checklist adds the constraints: the primary locale cannot be changed later, structural changes must be made in it, and Ecommerce products, categories and pages cannot be localised. The companion guide to Webflow localization on this site, published a few days before this one, covers the setup order, so this roundup stays on the tool choice.
What the API can and cannot do. Every app in the next sections works through the same door. Webflow's developer documentation says the Data API can localise page content, metadata, slugs, component content and CMS items in secondary locales. It cannot localise images, styles or classes, and "requests to update primary locale content will fail". Text and metadata flow through; pictures and layout do not.
Weglot and Linguana: proxy tools that sit outside Webflow
Both translate a live site rather than a Webflow project. Neither needs the Localize add-on, and neither puts a word of French into the Webflow CMS.
Weglot. The Webflow integration is a JavaScript snippet in the site's head code, after which Weglot "automatically creates language subdomains or subdirectories (depending on your preference)". Subdomains need one CNAME record per language. Subdirectories on Webflow are more involved: Weglot's support article lists four DNS scenarios depending on Cloudflare proxying and www, and in the standard case has you email support so they finish the setup "while keeping your DNS records still pointing to Webflow". Translated URLs are a Pro feature and above. Weglot counts source words multiplied by languages, so a 60-page site with 18,000 words in three languages is 54,000 words, just over the Business plan's 50,000. Business is €29 a month (three languages, 50,000 words), Pro €79 (five languages, 200,000 words) and Advanced €299 (ten languages, one million words), with two months free on yearly billing. Professional translation is ordered through Weglot "from 0.13€/word".
Linguana. Linguana connects by DNS and says "all translated pages are generated and served from our super-fast CDN". Subdirectories and translated URLs are on every plan, including the free one. Its pricing model is the opposite of Weglot's: AI credits are a one-time grant, one credit per word, with extra credits at $50 per 50,000, and "manual translations are completely free". Starter is $25 a month ($19 yearly) for three languages and 10,000 credits; Individual is $59 ($49 yearly) for unlimited languages and 50,000 credits; Business is $129 ($99 yearly) with 100,000 credits. The pricing page says "meta language tags" rather than hreflang, which is worth checking in a trial site's page source.
The shared trade-off is editing in two places. When the English page changes, the proxy machine-translates the new strings and someone reviews them in its dashboard, not in Webflow. That second dashboard is the real cost, and it is on neither pricing page.
TMS apps: Crowdin, Lokalise, Phrase, Smartling and the rest of the Marketplace
Webflow's Marketplace Localization category listed nine apps on 7 November 2026: Crowdin, Lokalise, Phrase, Localazy, SimpleLocalize, GlobalLink, LILT Connector, Smartling and a newer entrant called wxrks. Crowdin and Lokalise each showed more than a thousand installs.
These apps do not serve pages. They read page, CMS and component data through the API, send strings to translators or an engine, and write the results into Localize locales. So you pay for the add-on as well as the TMS: Webflow's roundup lists Crowdin from $59 a month, or $50 billed annually. And images and styles are still localised by hand.
The case for this route is a company that already runs a TMS for its product, with one glossary across app, help centre and site. Without a product behind it, the TMS adds a subscription and a sync step to a job Localize's own AI translation already does. Our guide to Webflow apps a B2B marketing team actually needs applies the same test to the rest of the Marketplace.
Manual routes: native locales filled by hand, and the folder-per-language build
Native locales, filled from an engine. The cheapest path that still uses Localize is to skip the AI allowance, run the copy through an engine yourself and paste it into each locale. Google's Cloud Translation pricing gives the first 500,000 characters a month free and charges $20 per million after that. At six characters a word, 18,000 words is about 108,000 characters per language, so three languages fit inside the free tier and ten cost about $12 once. The add-on is still paid monthly. It is worth it only when a human will review every line anyway.
Folder per language, no add-on. Before Localize existed, the Webflow answer was to duplicate every page into a /fr/ folder and every Collection into a French twin. It costs nothing in software. It also doubles the item count against the caps in our guide to Webflow CMS limits, gives you no locale selector and no automatic hreflang, and turns every edit into two. We would use it for a two-page landing set and nothing larger.
What a 60-page site costs at 3 and 10 languages
The model site has 60 pages at 300 words each, 18,000 source words, and a team that wants translated slugs. Prices are software only, at the monthly list price on each vendor's pricing page on 7 November 2026, with Weglot's euros alongside the dollar estimates its page gives.
| Route | 3 languages | 10 languages | One-off | What decides the row |
|---|---|---|---|---|
| Localize Essential | $27 | Not available, 3-locale cap | None | 30,000 AI words a month, so the first 54,000-word pass takes two cycles; no translated slugs |
| Localize Advanced | $87 | $290 | None | Translated slugs, asset localisation and routing included |
| Weglot | €79 ($87), Pro | €299 ($329), Advanced | None | 54,000 words exceeds Business; Pro caps at 5 languages |
| Linguana | $25, Starter | $59, Individual | $50 and $150 in extra credits | Credits do not renew; manual translation uses none |
| Crowdin plus Localize Advanced | $146 | $349 | None | Crowdin Pro $59 plus the add-on; check Crowdin's hosted-word allowance |
| Engine plus Localize Advanced | $87 | $290 | $0 and about $12 | Google Cloud Translation, first 500,000 characters a month free |
| Folder per language | $0 | $0 | None | Paid in editing time and CMS items |
Sources: Webflow pricing page, Weglot pricing, Linguana pricing, Webflow blog roundup for Crowdin, Google Cloud Translation pricing, all read 2026-11-07
Then the row missing from every vendor's page. Weglot's professional translators start at €0.13 a word, the only published rate in this set. At that rate, 18,000 words cost €2,340 per language: about €7,020 for three languages and €23,400 for ten. Even the dearest software row, $349 a month, is under 5% of the ten-language review bill in the first year.
SEO: what each route does to URLs, hreflang and crawl
Google's rules are short. Its documentation on localised versions says the page-head link element, the HTTP header and the sitemap entry are "equivalent from Google's perspective", and that each version must list itself and every other version, plus an x-default fallback. Localised pages "are only considered duplicates if the main content of the page remains untranslated", the sentence that makes machine-translated pages indexable. Its page on multi-regional sites advises against redirecting visitors between language versions automatically, because it "could prevent users (and search engines) from viewing all the versions of your site"; Googlebot usually crawls from the USA without an Accept-Language header.
| Route | Default URL structure | hreflang written by | Translated slugs | Visitor routing |
|---|---|---|---|---|
| Webflow Localize | Subdirectory, /fr/ | Webflow, in page head and sitemap | Advanced and Enterprise | Advanced and Enterprise, root homepage only |
| Weglot | Subdomain, fr.example.com; subdirectory with DNS work | Weglot | Pro and above | Weglot auto-redirection |
| Linguana | Subdirectory | Linguana, as "meta language tags" | Every plan | Not stated on the pricing page |
| TMS apps | Whatever Localize does | Webflow | As per Localize tier | As per Localize tier |
| Folder per language | Subdirectory | You, by hand | Yes | None |
Sources: Webflow feature page and Localize checklist, Weglot Webflow page and subdirectory article, Linguana pricing page, Google Search Central, read 2026-11-07
Google's comparison of structures calls subdirectories "simple setup" with "low maintenance". On Webflow the practical difference is who owns the DNS record: a native subdirectory needs no change, a Weglot subdomain needs one CNAME per language, and a Weglot subdirectory needs the Cloudflare scenario that matches plus an email to support.
The native output is easy to check. Flöa, a bilingual English and French Canadian site, publishes 66 URLs in its sitemap, each with en, fr-CA and x-default entries, and the same alternate links in every page head. That is what Google asks for, written by Webflow with no configuration beyond turning the locale on. Our answer to whether Webflow is good for SEO covers the redirect rule for localised paths, and the Webflow SEO checklist has the per-locale title and description step.
How to choose a Webflow localization tool
Four questions settle it. Where will the people who own each language edit copy? If the answer is Webflow, the native add-on wins, and translated slugs set the tier. Does the company already run a TMS for its product? Then a Marketplace app keeps the site in that process. Is the site not yours to rebuild, or does it need a second language this week? That is the proxy case, Weglot for the broadest integration and Linguana for the cheapest subdirectories. Is it two pages? Duplicate them.
Our position carries a bias. We build marketing sites in Webflow, and on Flöa we used native Localize with an English primary and a French Canadian secondary, because the client's team edits in Webflow. We would reach for Weglot where a client already runs it elsewhere, and for a TMS app where an engineering team owns the glossary. We would not put a proxy in front of a site whose marketing team has just learned the Editor. Our Webflow development service page explains how we scope a multilingual build.


