> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.drimify.com/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Multilingual option and language management **With Drimify's premium package, you can create games in 46 different languages.** You can enable participants to play your game in multiple languages, unifying your data export and statistics across different language versions of the same game. # Where is the multilingual support option? Once you are in your application, you can access the multilingual support settings by clicking on the cog icon below the app name and app ID, above the game creation steps. Here you can enable the premium option, and define what languages you wish to make your game available in. # Defining the available languages, and how different language versions are accessed Within the multilingual support option you have the following variables: **Selected languages:** These are the languages your game is available in. Search or select your languages from the “Add language” field above, and enable or disable the selected languages to define which versions are available to your audience. ![](https://storage.crisp.chat/users/helpdesk/website/b5930908db9b0800/screenshot-353_1111gva.png) **Language selection mode:** This is where you define how players access the different language versions of your game. Select from: * **Automatic detection based on the user browser:** This means whatever language a user’s browser is set to is the language they’ll play the game in IF that language is supported within the app’s configuration. || To the right hand-side of each of the selected languages is the “Primary” tick box. Whichever box is checked here is the primary, or fallback language. In the case that a user accesses your game in a browser set to a language you’ve not included, play will fallback to the primary language. * **Enable the language selection screen:** This gives users the option to select from the available languages through a pre-screen language selector at the start of the experience. ![](https://storage.crisp.chat/users/helpdesk/website/b5930908db9b0800/screenshot-352_1unxdpm.png) # Forced language selection by you (client) Where automatic selection nor a language selection screen suits your needs, you can manually select which language the game is displayed in. This is particularly useful for targeted campaigns where the language needs to be consistent regardless of the user’s system settings, but multiple language versions of it are still required. The client simply passes the specific language variable “preferred\_lang“ to the Drimify experience link, and the content is then rendered in the chosen language. ||| The **preferred\_lang** query string allows the client to force the display language of the Drimify experience via the URL. If the specified language isn’t available in the game, the experience will automatically fall back to the default language. # Creating your different language versions Adding and enabling new language versions of your game - as explained above - creates an identical version within your game with all the interface buttons and default texts set to that language. The branding and media (images, video, audio) is global across language versions, but each additional language version comes with blank fields for your translated copy. By selecting the cog icon (with the flag next to it) below your app name and ID, you can select which language version you are editing. ![](https://storage.crisp.chat/users/helpdesk/website/b5930908db9b0800/screenshot-355_1qahyut.png) You can then go through and add your translated copy manually for each customisable field in the creation steps — or use **AI Auto-Translation** to fill them for you (see below). # Translating your content automatically with AI Instead of filling in every translated field by hand, you can let Drimify's [AI Auto-Translation](/en/article/translating-your-app-with-ai-auto-translation-zp6up9/) do it for you. Your primary language remains the source of truth, and for each additional language you have the following options: * **Translate** — fills in only the missing (empty) fields for that language, leaving existing translations untouched. * **Refresh** — re-translates all content from the primary language, overwriting existing translations. Useful after you've updated your primary content. * **Bulk actions** — **Translate Missing (N)** and **Refresh Outdated (N)** let you process several languages in one click. Each language shows a status badge so you always know where you stand: **Missing** (red), **Outdated** (yellow, shown when the primary content changed after translation), **Translating** (blue), or no badge when the translation is complete and up to date. Each translation action costs **1 AI credit per language**. Translations run in the background, and you can still fine-tune any AI-translated field manually afterwards — manual edits are preserved as long as you use **Translate** (fill missing) rather than **Refresh**. | For full details, see [Translating your app with AI Auto-Translation](/en/article/translating-your-app-with-ai-auto-translation-zp6up9/). # Why can’t I have different media in my different language versions of the same game? The multilingual support option is here to make creating multiple language versions of the same game simple and easy. Adding more variables beyond the copy removes that simplicity. However, if you do require more tweaks, there is a workaround: 1. Create your game or interactive module in the first language. 2. When finished, duplicate your game from your Drimify dashboard. 3. Translate the content of your duplicated game into the second language, and make any additional required alterations. Remember, only basic user interface translations will be applied by the system (i.e. the buttons). For the content you have added, you will have to translate it yourself. ||| If you follow this method to create a game or module in 2 different languages, each language will have its own URL - technically you will have 2 separate applications. ## How can a user switch from one language to another by this method? You can set up different solutions to detect a participant’s language and direct them to the appropriate game or module's URL: **A banner, button, or link on your site** or a landing page that directs the participant to the game in their language of choice **A landing page with language selection buttons** **A landing page with an automatic language detection script** that automatically redirects the user to the game in their language **Using Drimify's Personality Test or Landing Page with a form,** without a start screen, you can create a "What is your language?" question or field and, depending on the answer chosen, give the participant access to a results screen with a button directing them to the desired game URL. | Contact us if you need assistance or a customised solution. What languages are available? Here's the list of 46 languages from the image: * Arabic * Azeri * Bulgarian * Bosnian * Chinese (Simplified) * Chinese (Traditional) * Croatian * Czech * Danish * Dutch * Flemish * English * Estonian * Finnish * French * German * Georgian * Greek * Hebrew * Hungarian * Hindi * Indonesian * Italian * Japanese * Korean * Latvian * Lithuanian * Luxembourgish * Macedonian * Malaysian * Norwegian * Polish * Portuguese * Portuguese (Brazil) * Romanian * Russian * Serbian * Slovak * Slovenian * Spanish * Spanish (Mexico) * Swedish * Thai * Turkish * Uzbek * Vietnamese || Other languages can be added upon request. Do not hesitate to contact us if your desired language is not listed here.