Webflow Localization

To start with the localization of your Webflow website, you must own the Webflow Localization Subscription Plan. Then you simply add new locale to your webflow project and connect it with Localazy.

Add new languages in Webflow #️⃣

1. Login to your Webflow account and go to your dashboard.
2. Choose website you want to localize and open Designer.
3. Click on the Settings icon in the left sidebar.
4. Select Localization.
5. Click on the Add new locale button and choose the language you want to add.
6. Click on the Save button.
7. Click on the Save changes button.

Translate your Webflow instance using Localazy #️⃣

1. Sign up to Localazy and create a new project
2. Install the Webflow integration in Localazy and connect your account.
3. Import your content to Localazy
4. Translate your content (learn more).
5. Export translations to Webflow

Unfortunately, Webflow API does not provide a way to update the translations of ecommerce collection items and dynamic components, so they are not supported. The integration is limited by what Webflow allows us to export/import via their API.

You can try the integration during your 14-day free trial and see if it works for your site.

There are two fundamentally different approaches to translating Webflow websites, and understanding the difference will help you choose the right tool for your needs.

Localazy is a Translation Management System (TMS) #️⃣

Localazy works as a backend translation layer. You import content from Webflow into Localazy, translate it (using your team, machine translation, Localazy AI, or professional translators), and then export the translations back to Webflow. The translated content lives natively in Webflow’s localization fields.

This approach means Localazy doesn’t inject any scripts into your website’s frontend. Your site structure, routing, domains, and hreflang tags remain entirely under your control in Webflow. You get clean output and full SEO control.

Localazy requires a Webflow Localization subscription on Webflow’s side, since we push translations into Webflow’s native localization infrastructure via their API.

Proxy-based tools work differently #️⃣

Tools like Weglot, Bablic, and similar solutions work as localization proxies. They sit between your visitors and your website, intercept the content, and serve translated versions on the fly. They typically handle the /en/, /es/, /de/ subfolder routing themselves and generate hreflang tags automatically.

The advantage is that proxy-based tools don’t require Webflow’s Localization subscription – they work with standard Webflow sites. The trade-off is that they inject frontend scripts and take control of your SEO metadata, which may not suit teams who want granular control over site structure and hreflang implementation.

Which approach is right for you? #️⃣

Choose Localazy if you want full control over your site’s SEO setup, prefer clean output without frontend script injection, need a proper translation workflow with roles, reviews and approvals, or plan to scale to many languages without per-language pricing surprises.

When you connect Localazy with Webflow, you can sync both static pages and CMS collections. The integration supports a complete translation workflow where translators propose changes, reviewers approve them, and only then do translations get exported back to Webflow. You can use machine translation to speed up the process, bring in your own team, or order professional translations directly through the platform.

Localazy pricing is based on source keys (strings), not the number of languages. Whether you translate to 5 languages or 25, the cost stays the same. All plans include unlimited team seats.

One technical limitation to be aware of: Webflow’s API currently doesn’t support e-commerce collection items or dynamic components, so those content types can’t be translated through the integration. This is a constraint on Webflow’s side rather than ours.