Skip to main content
Webflow
Dmitry avatar
Written by Dmitry
Updated over 3 weeks ago

Webflow is a powerful website builder and content management system (CMS) that lets users design custom websites without coding.


Content support

Supported content

Lokalise can translate the following Webflow content:

  • Static pages

  • Collection items

  • Static elements within collection pages

Unsupported Content

The following cannot be translated due to Webflow API limitations:

  • Page settings (slug, title, description)

  • Page components

  • Collection slugs

  • Assets

  • E-commerce product descriptions

  • Forms

  • Custom code snippets


Getting started

To begin, create a Marketing and Support project if you haven’t already.

Enter a project name, select your base and target languages, and choose Webflow from the Content integrations dropdown.

Once everything is set, click Create project to finish. You're now ready to start translating your Webflow content.


Installation

To use the app, you must have access to Webflow Localization with at least one locale set up on your Webflow site.

Once the Marketing and support project is created, you should be redirected to the Content management tab. If not, open your project manually and switch to that tab. Click Authorize:

Choose a single website from your Webflow workspace, then click Authorize app:

Webflow allows access to multiple websites at once, but you should select only one website per Lokalise project. If multiple websites are chosen, only the first one will be connected.

After installation, synchronization may take 5–10 minutes. Synchronization should start automatically, but you can also trigger it manually by clicking Refresh.


Importing entries from Webflow to Lokalise

After installing the app, you'll see a list of available content from Webflow. In the Ready for import view, select the items you want and click Import from Webflow.

A dialog will appear where you can choose which languages to include in the import.

Enable Overwrite existing keys if you want to update previously imported translation keys with any changes made in Webflow. Updated keys will return to Unverified status.

If you plan to use Automations, it's best to import only the default language with Overwrite existing keys enabled. Alternatively, you can import all desired languages while keeping this option disabled.

The import will run in the background, and once completed, you'll see a notification:

Click View content to proceed to content editing.


Translating exported entries on Lokalise

You can go to the Editor and translate the content as usual or create tasks for your translators. Each key will have a tag corresponding to the name of the page or collection item.


Re-importing updated content from Webflow to Lokalise

If content on Webflow is updated before translations are finished or even after they are exported, you can re-import it.

Click Refresh to check the last update date, select the items you want to re-import, and click Reimport from Webflow.


Exporting translations from Lokalise to Webflow

Once the translations are reviewed, go to your project on Lokalise, open the Content management tab, and switch to the Imported view.

Select one or more items and click Export to Webflow.

A dialog will appear where you can choose the languages to export.

Click Export to Webflow to start the process. The export runs in the background, and you’ll receive a notification when it's completed.

You can view the translations by switching the language in Webflow’s Designer.


Known limitations

Languages

If a language is set to Disabled in Webflow, content exchange for that language won’t be possible in Lokalise. For example, if the Spanish (Argentina) locale is disabled, it cannot be imported or exported:

You need to enable publication for that locale to proceed:

Collections

Reference fields are not automatically imported along with the original item. Linked items must be imported separately.

Pages

Exporting a base language (e.g., English (en)) from Lokalise to Webflow is not supported due to Webflow API limitations.

Did this answer your question?