To offer the same community or website content in more than one language, create a separate space for each language version and translate the content yourself or with the help of AI. Sutra does not translate creator-written content automatically, but you can connect your AI of choice to Sutra MCP and translate spaces with ease.
Choose a structure
Use one of these structures:
Separate top-level spaces: Create one top-level space for each language when each version needs its own community structure, website root, navigation, header, footer, access, or public address.
One top-level space with language sections: Keep the language versions inside one community or website when you want members to reach them from the same navigation bar. Create a parent subspace for each language, then place that language's pages underneath it.
For example, one website can contain an English subspace and a Spanish subspace. Each can contain its own About, Program, and Contact spaces.
Build separate top-level spaces
Create a top-level space for the first language and add its content and subspaces.
Create another top-level space for the next language. You can also use Duplicate on an existing top-level space to copy the selected parts of that space.
Rename the new space for its language.
Translate its creator-written content, space names, registration content, posts, broadcasts, automations, and other copied material that you plan to use.
Review the members, managers, access, registration, and website settings separately for each top-level space.
The Duplicate form shows choices for copying content, members, managers, posts, broadcasts, automations, and the registration page. Broadcasts and automations can be copied together by the backend when either option is selected, so review both in the duplicate.
Add language versions inside one community or website
You can organize the language versions in either of these ways:
Language sections: Create a subspace for each language, such as English, Español, and Français. Create the translated pages separately beneath the appropriate language section.
Duplicated sibling pages: Duplicate a page, rename the duplicate with its language, and translate its creator-written content. A full duplicate retains the original space's parent, so both language versions remain siblings in the same part of the hierarchy.
In website mode, open the three-dot menu next to a language section or translated page and use Show in nav to control whether it appears in the website navigation.
Website navigation follows the active subspace hierarchy. Eligible, active pages that the visitor can view can appear nested beneath a visible language section. A page hidden from navigation is excluded, and public website navigation also requires a valid website route.
Translate a duplicated space with an AI assistant
After you duplicate a space in Sutra, a connected AI assistant can read the duplicate's content and help rewrite it in another language.
Use Duplicate in Sutra to create the language copy.
Connect an AI assistant to Sutra if you have not already connected one.
Give the assistant the duplicated space and the target language.
Ask it to read the creator-written content, translate it, and update the duplicate.
Review the translated space, including its name, content, structure, links, and settings.
The current MCP tools can read spaces and content blocks, create spaces and content, and update content. They do not expose Sutra's full Duplicate action, so create the duplicate in Sutra before asking the assistant to translate it. The assistant does not automatically synchronize later changes between language versions.
What language switching changes
Sutra can load a supported interface language detected or selected in the browser. The current frontend includes English, Spanish, Russian, Portuguese, German, Italian, and French locale bundles.
This does not automatically translate creator-written space names or content. Translate and maintain each language version separately.
Current limitations
The current website configuration and route schema do not include locale fields or linked translation variants. Sutra does not automatically translate or synchronize duplicated spaces. A website also has one shared header, footer, and website configuration for its top-level root.
If each language needs different shared website navigation, headers, footers, or settings, use separate top-level spaces. If the language versions can share one website shell, keep them under one top-level space and expose the language sections in its navigation.