- Webflow
- Guide
- No-Code
Webflow multilingual: how to translate your Webflow site (2026)
7 min read
Webflow now has native localization built into the Designer. It's also possible to add automatic multilingual support to any Webflow site with a single script tag — no rebuild, no per-locale billing, works on any Webflow plan. Here's everything you need to know to choose the right approach.
Webflow's built-in localization
Webflow launched native Localization in 2023. It lets you manage translated versions of your site directly inside the Webflow Designer — without a third-party tool or custom code.
With Webflow Localization you can:
- Translate text content, rich text, and metadata per locale from inside the Designer
- Swap images and videos per locale (e.g., localised product photos or hero images)
- Set locale-specific URL slugs (e.g.,
/fr/a-proposinstead of/fr/about) - Export content to XLIFF files for translation agency workflows
Webflow Localization uses a recurring locale plan in addition to the base Webflow plan. Verify current locale limits, packaging, and pricing on Webflow's site.
Webflow Localization limitations
All translations are manual
Webflow Localization does not include machine translation. You write or paste every translated string yourself inside the Designer, or use an external translation tool and import the XLIFF file. For sites with hundreds of pages and dozens of languages, this is a significant time investment.
Per-locale billing scales quickly
Locale-based recurring plans can add up across multiple languages or client sites. Model the current vendor price against the number of locales and sites you manage.
Translation changes require a republish
When you update a translation, you must republish the Webflow site for the change to go live. This means translation updates are tied to your Webflow publishing workflow — you can't push a translation fix without a full site republish.
Requires a paid Webflow plan
Webflow Localization is not available on the free Starter plan. You need at least a paid site plan to enable localization — which is an additional cost consideration for small projects.
The script-tag alternative
A DOM-based translation widget like Lingvit takes a completely different approach: rather than managing translations inside the CMS, it translates the published Webflow site automatically in the visitor's browser.
You add a single script tag to Webflow via Site Settings → Custom Code. The widget handles everything else: language detection, translation, language switcher, URL routing, and hreflang tags.
This approach works on any Webflow plan — including Basic — because it operates on the published HTML, not inside the Webflow platform itself.
Step-by-step: add Lingvit to Webflow
Create a Lingvit project and copy the script tag
Sign up at app.lingvit.com, create a new project, and enter your Webflow site's domain. Copy the script tag from the project settings.
Add the script to Webflow Custom Code
In Webflow: go to Site Settings → Custom Code → Footer Code (the section labelled “Before </body> tag”). Paste the Lingvit script tag there. Save and publish the site.
Select languages in the Lingvit dashboard
Back in the Lingvit dashboard, select your target languages. The language switcher widget appears after the configured script loads. Translations generate when first requested and are stored for reuse; verify the result before publishing broadly.
What gets translated
| Content type | Translated? |
|---|---|
| Headings, paragraphs, body text | Yes |
| Button labels and link text | Yes |
| Navigation links | Yes |
| Form placeholders and labels | Yes |
| Webflow CMS collection items | Yes (when rendered to the page) |
| Images and videos | Not translated (alt text is) |
| Third-party embeds (Calendly, Typeform, etc.) | No (loaded in iframes) |
Scroll horizontally to view every column.
SEO for multilingual Webflow
Multilingual SEO requires that each language version is discoverable by search engines. At launch, use Webflow Localization or another server-rendered routing layer for that search requirement; Lingvit runtime translation alone does not create indexable locale URLs.
Platform-owned hreflang tags
Configure
hreflangin the platform that owns each crawlable locale URL. Keep those tags reciprocal and aligned with the language switcher.Crawlable locale URLs
Use Webflow Localization or another publication layer to create URLs such as
/fr/and/de/. Validate those rendered pages before expecting per-language indexing.Translated meta titles and descriptions
Translate the page
<title>andmeta descriptionin the publication layer that renders each locale URL.
Webflow Localization vs Lingvit: when to choose each
| Factor | Webflow Localization | Lingvit |
|---|---|---|
| Translation method | Manual (paste or import) | Automatic + overrides |
| Setup time | Hours to days | Guided custom-code setup |
| Pricing model | Recurring locale plan; verify current pricing | Monthly or annual plans with word capacity and monthly generation |
| Webflow plan requirement | Paid plan required | Any plan including Basic |
| Image localisation | Yes (per-locale images) | No |
| Translation update speed | Requires republish | Published from dashboard; timing varies |
Scroll horizontally to view every column.
Choose Webflow Localization if you want translations managed inside Webflow with per-locale CMS entries, locale-specific images, and full editorial control over every string before it goes live.
Choose Lingvit if you want automatic translation, more languages, simpler simple monthly pricing and a guided custom-code setup.
Frequently asked questions
Does Lingvit work with Webflow CMS?
Yes. Webflow CMS content (blog posts, product listings, team members, etc.) renders as HTML on the published page. Lingvit translates whatever is in the DOM — including CMS-rendered content — so collection pages are translated automatically without any special configuration.
Does it slow down the Webflow site?
Stored translations can be reused without another provider request. Visitor experience still depends on the page, browser, network, and widget delivery, so test representative pages before launch.
What about Webflow Ecommerce?
Lingvit translates all text rendered to the DOM, which includes Webflow Ecommerce product names, descriptions, category names, and cart/checkout UI strings. Payment provider pages (Stripe Checkout) are not translated as they are hosted by the payment provider, not Webflow.