Multiple Languages
This article describes how Jimo supports localization for multilingual applications.
Jimo allows displaying content in a specific language depending on the user's browser language. You can do it manually if you want, but we offer an automatic translation of content with AI.
Additionally, you can force a specific language using an SDK command instead of relying on the browser’s settings, you can use the Jimo SDK.
This allows you to adapt translations based on your own website’s language parameter instead of relying on the browser's default setting.
See the SDK documentation on forcing a language for details.
Quick access
Languages available
Jimo allows you to translate your content into 34 different languages:
See the full list of supported languages
🇦🇱
Albanian
sq
🇸🇦
Arabic
ar
🇧🇬
Bulgarian
bg
🇨🇳
Chinese (Simplified)
zh
🇹🇼
Chinese (Traditional)
zh-hant
🇨🇿
Czech
cs
🇩🇰
Danish
da
🇳🇱
Dutch
nl
🇬🇧
English
en
🇫🇮
Finnish
fi
🇫🇷
French
fr
🇩🇪
German
de
🇬🇷
Greek
el
🇮🇱
Hebrew
he
🇭🇺
Hungarian
hu
🇮🇩
Indonesian
id
🇮🇹
Italian
it
🇯🇵
Japanese
jp
🇱🇦
Laotian
lo
🇳🇴
Norwegian
no
🇳🇴
Norwegian Bokmål
nb
🇳🇴
Norwegian Nynorsk
nn
🇵🇱
Polish
pl
🇵🇹
Portuguese
pt
🇷🇴
Romanian
ro
🇷🇺
Russian
ru
🇷🇸
Serbian
sr
🇸🇰
Slovak
sk
🇪🇸
Spanish
es
🇸🇪
Swedish
sv
🇹🇭
Thai
th
🇹🇷
Turkish
tr
🇺🇦
Ukrainian
uk
🇻🇳
Vietnamese
vi
It will be automatically displayed depending on the user's browser language. If the language is not found it will fall back to the default version.
If you ever need any other languages, reach out to Jimo's support team and we'll add it!
What if my website uses a custom language param in the user data?
Some apps store the user's language as part of the user profile (e.g. a locale or preferred_language field in your backend) rather than relying on the browser language. In that case, you can push that value directly to Jimo so translations match the user's preference regardless of the browser settings.
The recommended setup is to push the language code via the SDK using the force language method. Pass the language code (e.g. fr, en, pt) from your user data to the SDK at init time or whenever the user changes their language preference.
Read the user's language preference from your user data or app state.
Pass the matching language code to the SDK (
sq,ar,bg,zh,zh-hant, etc., see the full list).Jimo will then display the matching translation for every experience the user sees, ignoring the browser language.
This approach is useful when your product lets users pick their own UI language independently from their browser, or when you need translations to follow the user across devices.
What if my website uses a language slug in the URL?
Some websites use a language slug in the URL (e.g. yoursite.com/fr/pricing vs yoursite.com/en/pricing) rather than relying on the browser language. In that case, the built-in translation feature may not be the best fit, since the same user's browser language won't reflect the page they're actually on.
The recommended workaround is to duplicate the experience per language and use URL targeting on the audience to fire each version only on the matching URL pattern.
Build your experience in the default language.
Duplicate it once per language you need.
Translate each duplicate's content.
On each duplicate, set the audience to target the matching URL pattern (e.g.
/fr/*for the French version,/en/*for the English one).
See Target specific URLs, domains & where for the full audience URL targeting setup.
How to display experiences in different languages?
In your Experience edition (Jimo's builder), click on the Translation Feature on the left bar, and you will see all your step contents, then Add a translation.
Add your different languages, then modify the content with the right language manually or do it automatically with Smart Translate.
A (Add Translations Button): Click here to start adding translations to different elements of your tour. This is your first step towards creating a multilingual experience.
B (Smart Translate): Utilize this AI-powered tool to automatically generate translations based on your original content. It's efficient for quickly producing accurate translations across various languages.
C (Language Selection): This dropdown menu lets you select the language you're working on. Once selected, you can proceed to input or edit translations specific to that language.
D (Translation Editor): In this section, manually input or edit the translations for elements like titles, paragraphs, labels, and calls-to-action. This editor shows you exactly where each translated text will appear in your tour, ensuring you can tailor the content to fit cultural nuances and language specifics.
Last updated