Tools

Webflow Localization Tools in 2026: Native Localize vs Weglot vs Linguana vs Manual, With Costs at 3 and 10 Languages

Six ways to localise a Webflow site, what each one does to URLs and the CMS, and what a 60-page site pays at three and ten languages, including the review bill nobody budgets for.

Summarize with AI
Octo Agency cover: Webflow Localization Tools in 2026, with a purple hexagon pattern

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.

Six routes to a multilingual Webflow site
RouteWho serves the translated pageWhere copy is editedNeeds the Localize add-onTranslated slugsPaid from
Webflow Localize (native)WebflowDesigner and CMS, per localeIt is the add-onAdvanced and Enterprise$9 per locale a month
WeglotWeglot's servers, via script and DNSWeglot dashboardNoPro and above€15 a month, free to 2,000 words
LinguanaLinguana's CDN, via DNSLinguana dashboardNoEvery plan$25 a month, free to 2,000 credits
TMS apps (Crowdin, Lokalise, Phrase, Smartling, others)WebflowThe TMS, synced into localesYesAs per Localize tierCrowdin from $59 a month, plus the add-on
Manual into native localesWebflowDesigner and CMS, pasted by handYesAs per Localize tier$9 per locale a month
Folder per language, no add-onWebflowDuplicate pages and CollectionsNoYes, 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.

Monthly software cost, 60-page site, 18,000 source words
Route3 languages10 languagesOne-offWhat decides the row
Localize Essential$27Not available, 3-locale capNone30,000 AI words a month, so the first 54,000-word pass takes two cycles; no translated slugs
Localize Advanced$87$290NoneTranslated slugs, asset localisation and routing included
Weglot€79 ($87), Pro€299 ($329), AdvancedNone54,000 words exceeds Business; Pro caps at 5 languages
Linguana$25, Starter$59, Individual$50 and $150 in extra creditsCredits do not renew; manual translation uses none
Crowdin plus Localize Advanced$146$349NoneCrowdin Pro $59 plus the add-on; check Crowdin's hosted-word allowance
Engine plus Localize Advanced$87$290$0 and about $12Google Cloud Translation, first 500,000 characters a month free
Folder per language$0$0NonePaid 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.

URL structure and search signals by route
RouteDefault URL structurehreflang written byTranslated slugsVisitor routing
Webflow LocalizeSubdirectory, /fr/Webflow, in page head and sitemapAdvanced and EnterpriseAdvanced and Enterprise, root homepage only
WeglotSubdomain, fr.example.com; subdirectory with DNS workWeglotPro and aboveWeglot auto-redirection
LinguanaSubdirectoryLinguana, as "meta language tags"Every planNot stated on the pricing page
TMS appsWhatever Localize doesWebflowAs per Localize tierAs per Localize tier
Folder per languageSubdirectoryYou, by handYesNone

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.

Frequently asked questions

What are the main Webflow localization tools?

There are six routes. Webflow's native Localize add-on keeps every locale in the Designer and CMS, from $9 a locale a month. Weglot and Linguana are proxy services that serve translations from their own servers without the add-on. Nine Marketplace apps, including Crowdin, Lokalise, Phrase and Smartling, push copy into Localize locales through the API. The manual routes are pasting engine output into native locales, or duplicating pages into a folder per language.

How much does Webflow localization cost for three languages?

With the native add-on, three locales cost $27 a month on Localize Essential and $87 on Advanced, which adds translated slugs, per Webflow's pricing page. Weglot's Pro plan at €79 a month covers a 60-page site of 18,000 words in three languages, because its word count multiplies by languages. Linguana's Starter plan is $25 a month plus one-off AI credits. Professional review at Weglot's €0.13 a word adds about €7,000.

Is Weglot better than Webflow Localize?

Neither is better; they put the translations in different places. Weglot goes live from a script snippet and translates sites you cannot rebuild, but the French copy lives in Weglot's dashboard, and subdirectories on Webflow need DNS work and a support email. Localize keeps every locale in the Webflow CMS the team already edits and writes hreflang itself. If the marketing team edits in Webflow, choose Localize; if the site is not yours to touch, choose Weglot.

Do translation apps like Crowdin still need the Webflow Localize add-on?

Yes. Marketplace apps read page, CMS and component data through Webflow's Data API and write translations into secondary locales, so the locales have to exist, and publishing a secondary locale requires a paid Localize add-on. The API cannot localise images, styles or primary-locale content, so those stay manual. The app earns its fee when the company already runs the same TMS for its product and wants one glossary across app, help centre and site.

Does Google penalise machine-translated pages?

Google's documentation on localised versions does not address machine translation directly. It says localised pages are only treated as duplicates when the main content stays untranslated, so a translated page is indexable on its own URL. What it warns against is automatically redirecting visitors by guessed language, which can hide versions from users and crawlers. The quality question is yours: a machine pass nobody reviews can rank, but it also represents the company in that market.

Sources

  1. Plans and pricing Webflow, 2026
  2. Website translation and localization tools Webflow, 2026
  3. The 6 best website localization services for translation and automation Webflow, 2026
  4. Webflow Localize checklist Webflow University, 2026
  5. Working with Localization APIs Webflow Developer Documentation, 2026
  6. Localization Webflow Apps Webflow Marketplace, 2026
  7. Pricing Weglot, 2026
  8. Translate your Webflow website Weglot, 2026
  9. How to use subdirectories on a Webflow website Weglot Help Center, 2026
  10. Pricing Linguana, 2026
  11. Localized versions of your pages Google Search Central, 2026
  12. Managing multi-regional and multilingual sites Google Search Central, 2026
  13. Cloud Translation pricing Google Cloud, 2026
  14. Flöa sitemap Flöa, 2026

Tags

  • Webflow
  • Localization
  • Tools
  • SEO
Mihajlo Stojanovic

Mihajlo Stojanovic

Co-founder, Octo Agency

Mihajlo runs the technical side of Octo Agency: Webflow builds, custom backends and the systems that keep a site editable after launch. He has shipped more than twenty Webflow sites a year as a white-label partner and writes about what survives contact with a real marketing team.

Veljko Nikolic

Reviewed by

Veljko Nikolic

Founder, Octo Agency

Veljko runs the build side of Octo Agency. He has shipped marketing sites for B2B teams in legal tech, health and manufacturing, and writes about what survives contact with a real review cycle.