spec sheet · cms & commerce

Strapi and Transglot, publish your content across locales.

Choose Strapi in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.

Import and publish translations

Direction: Import and publish translations
Plan: Starter and up
Scope: entries, per content type, in one Strapi install
Authentication: a Strapi API token and the URL of your own install
Get started: Connect from your project’s CMS settings.

Create your project Setup

cms & commerce

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect Strapi
Choose Strapi in the project’s CMS settings. Add a Strapi API token and the URL of your own install.
connect
Choose the content and locale mapping
Select the types and fields you want to localize. The connector reads entries, per content type, in one Strapi install. Map the source and target locales to your project.
map
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
review
Publish to Strapi
Use Publish to CMS to send the translated values to the mapped target locales. Check the publish result in the project’s CMS settings.
deliver

Publish translated values back to the target locales you map in Strapi.

what moves

What you can translate and deliver.

Your own self hosted Strapi 5, over the content REST API with the i18n plugin. Each locale is a separate localization of one document, so a publish creates or updates the target localization and leaves every other one alone.

What you can translate and deliver.
Surface	What to expect
Source and scope	entries, per content type, in one Strapi install
Translated output	Publish translated values back to the target locales you map in Strapi.
Keep in mind	Only the content types and fields you select are synced. Source content stays in its source locale.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

a Strapi API token and the URL of your own install.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Create a Transglot project with the source and target locales you need.
Open the project’s CMS settings and choose Strapi.
Provide a Strapi API token and the URL of your own install.
Save the connection, select the supported content, map locales, then run Sync from CMS.

same project, more possibilities