- Using SafetyCulture
- Templates (managing)
- Manage multi-language templates
Manage multi-language templates
Localize your multilingual team's inspection experience by managing template translations.
This feature is currently in Early Access. If you're interested, please contact our customer support team or your customer success manager to check if your organization is eligible.
How does a multi-language template work?
We understand that for a global organization, your staff might come from different backgrounds and speak different languages. With SafetyCulture, you can localize the inspection experience by adding translations to your templates, so your team members can do their work in a language they're comfortable with.
Take a look at this example of an inspection being started in English and Chinese using the same template:
What you'll need
Organizations on the Premium Plan are limited to one translation in addition to the original template language per template.
1. Download translations from a template
Select Templates from the menu on the left-hand side.
Click
on the template's right-hand side and select 
Translate template.In the side panel, click Download CSV and open the downloaded file.
If you want to update a template for all languages, please make sure to update it in the template editor first. Then, follow the manage multi-language templates instructions to update the translations.
2. Prepare translations
In the CSV file, you'll find that supported web app languages are visible as column headers.
Add each label's translations for each language you want to support.
Save your changes.
By default, translations are shown based on each user's preferred language on their web browser for the web app or mobile device for the mobile app. If the template doesn't have a translation available in the preferred language, then the default version will be shown.
If you want to add translations for languages other than those supported on the web app, you'll need to add an additional column for each language and use the language code as the column header.
Refer to the "ISO-639 language codes" section in this article for language codes that are supported across all web, Android, and iOS platforms. For example, for Chinese (Simplified), use "zh-CN".
If you want to show translated versions to your users by means other than browser or device language preference, you can use groups to show translations manually. To show the relevant language for your users, create a group and add its "Group ID" to the language's "fallback_identifiers" row.
Please note that we do not automatically provide translations for downloaded templates. If you want to add translations, you have to create them for each question and add them manually to the translation CSV file.
3. Upload translations to a template
Go back to the web app.
In the side panel, upload your translation CSV file.
Click Publish template.
4. Conduct inspections
Now that your template is ready to be used in different languages, you can give template access to your team for them to start inspections.
5. View and export as reports
Once your team completes their inspections, they can also view the inspections as web reports in their preferred language or export them as a PDF or Word file.
Currently, only languages supported on the web app are available when viewing and exporting multi-language reports.
ISO-639 language codes
The following is not a complete list of language codes from around the world. However, all language codes in the list should be fully supported by both Android and iOS devices when recognizing provided languages.
Code | Language |
|---|---|
ar | Arabic |
ar-EG | Arabic (Egypt) |
ar-IL | Arabic (Israel) |
bg | Bulgarian |
ca | Catalan |
zh-CN | Chinese, Simplified |
zh-HK | Chinese, Traditional (Hong Kong) |
zh-TW | Chinese, Traditional (Taiwan) |
hr | Croatian |
cs | Czech |
da | Danish |
nl-NL | Dutch (Netherlands) |
nl-BE | Dutch (Belgium) |
en-AU | English (Australia) |
en-GB | English (United Kingdom) |
en-US | English (United States) |
fi | Finnish |
fr-CA | French (Canada) |
fr-BE | French (Belgium) |
fr-CH | French (Switzerland) |
fr-FR | French (France) |
de-DE | German (Germany) |
de-AT | German (Austria) |
de-LI | German (Liechtenstein) |
de-CH | German (Switzerland) |
el | Greek |
he | Hebrew |
hi | Hindi |
hu | Hungarian |
id | Indonesian |
it-IT | Italian (Italy) |
it-CH | Italian (Switzerland) |
ja | Japanese |
kk | Kazakh |
ko | Korean |
ms | Malay |
no | Norwegian |
pl | Polish |
pt-BR | Portuguese (Brazil) |
pt-PT | Portuguese (Portugal) |
ro | Romanian |
ru | Russian |
sk | Slovak |
es-MX | Spanish (Latin America) |
es-ES | Spanish (Spain) |
sv | Swedish |
th | Thai |
tr | Turkish |
uk | Ukrainian |
vi | Vietnamese |
sr | Serbian |
sl | Slovenian |
tl | Tagalog |
Limitations
Responses for questions using Global Response Sets, Sites, and Assets can't be translated.
Media attachments can't be translated.
Multi-language is not supported for exporting inspections as CSV or Excel.
Multi-language is not available in Analytics for response breakdowns and question filters.
Was this page helpful?
Thank you for letting us know.