The Strapi connector for Lokalise Vantage supports collection and single content types that are enabled for internationalization and have at least one field set as translatable. Once connected, you can select the content you want to translate, review translations in the editor, and send translated versions back to Strapi.

You need a Strapi API token with permission to read and update content. You can scope the token to specific content types, but for simplicity, you can also create a Full Access token.

To create a token in Strapi:

Make sure to copy the token before leaving the page, because you will not be able to view it again later.

Before exporting translations from Lokalise, make sure all target languages already exist in Strapi.

The Lokalise app can update existing language versions, but it cannot create new ones for you. If a language does not exist in Strapi, exporting that language from Lokalise will not affect your documents.

To add a locale in Strapi:

You can also change the default language in Advanced settings by enabling Set as default and saving your changes. If you do this, make sure documents are already published in that language.

To make content translatable in the Content Manager, Internationalization must be enabled in the Content-type Builder. This can be configured both at the content type level and at the field level.

Once Internationalization is enabled and the content type is saved, all fields in that type become translatable by default.

The Lokalise app creates draft versions of translated documents, so the Draft & Publish feature must also be enabled for the content type.

To enable it:

Create a new Lokalise Vantage project. Then click Connect to your tool, choose Strapi, and click Continue.

Next:

After the project is created, you will see the list of available documents that can be imported from Strapi. Select the documents you want to translate and click Continue.

To narrow the list, you can use:

After import, wait for AI translations to complete. Then review the translated fields and make sure all segments are approved. You can verify or edit each field and approve it using the green checkbox icon on the right side of the field.

Once 100% of segments are approved, the content moves to Done status and becomes available for export.

If you did not import all the content you needed during the initial setup, you can add more documents later directly from the editor. In the editor, click Import from Strapi.

This opens a dialog where you can browse and select additional content from Strapi.

Choose the documents you want to add, then click Import.

The selected documents will be added to your project so you can translate them the same way as the content you imported earlier.

Once your translations are ready, you can send them back to Strapi directly from the editor.

In the editor, click Send to Strapi.

Choose the documents you want to export and click Next.

In the final dialog, confirm the target languages and click Send.

Wait until the success message appears. Once it does, your translations have been published successfully.

During export, fields that contain relations are not populated in the newly created draft versions of translated documents. You need to link them manually afterwards.

Lokalise sends HTML back to Strapi largely as is. It does not simplify or rebuild the layout.

If the original content contains very complex HTML, mixed editors, or broken tags, the preview in Strapi may look different after export. Always review the result in Strapi after exporting translations.