Table of Content

While Machine Translation (MT) is generally not a recommended translation method, it's useful in some cases; for example, if you have a lot of non-customer-facing content, or you want to translate something in conjunction with human post-edit.

Transifex supports Google Translate, Microsoft Translator, DeepL Translate (we support both DeepL API Free and DeepL API Pro and our integration is based on version 2 (v2) of the DeepL API), Amazon Translate, and KantanMT.

You'll need to have an account with one of these services before you can use it for machine translation in Transifex. Depending on which service you choose and how many words you're translating, you might need a subscription for that service too.


When setting up an IAM user to use Amazon Translate with Transifex, the minimum permissions required are TranslateReadOnly.

Machine Translation on an Organization level

To set up machine translation for your whole organization and use the same MT service across all your projects:

  1. Head to your Organization Settings from the main navigation.

  2. On the left menu, click on Machine translation.


  3. Select the machine translation service you'll be using.

    1. If you want to use Microsoft Translator, choose Microsoft Translator Text API (latest) and add your subscription key. Also, while setting this up in Azure (Microsoft's cloud), make sure to select a 'Location/Region' of "Global".

    2. If you chose Google Translate, add your API key.

    3. If you chose KantanMT, add your API key and engine alias (check here for more details).

    4. If you chose DeepL, you need to add your API key and set whether the translated text should lean towards formal or informal language. Optionally, you can enable the "Apply the default formality on translations for non-supported languages" option. By enabling this option, languages not supported in the selected DeepL Formality will be translated using the default formality; if this option is disabled, these languages will remain untranslated.

      This functionality is described in DeepL Documentation here.


For DeepL and when the mode is set to β€˜Plain Text’, strings that include placeholders display a certain behaviour. Specifically, spaces are intentionally introduced before and after the placeholders found in the string to ensure that placeholders are preserved in the translation. To avoid this from happening, we suggest setting DeepL mode to β€˜HTML’.

  1. Choose Machine Translation Mode: HTML or plain text.

    • HTML mode

      Transifex leverages most of MT services capability to detect and keep HTML tags, Transifex protects only the variables and custom placeholders. Current known MT services hiccups include conversions of special characters to their HTML entity counterparts. (ex. a single quote character could become a ' in the translation)

    • Plain text mode

      Transifex is trying to protect all HTML tags, variables and custom placeholders feeding strings as simple text to Machine Translation services. Current known MT services hiccups include: extra symbols (ex. 0x5a4d6e521); translation missing part of a sentence found in source, meaning is altered; missing HTML tags, variables, custom placeholders as the MT service mishandles them.

  2. Click Save changes.


In case you need to use a different machine translation key for a specific project, please see the section below.

Machine Translation on a Project Level

In Transifex, you're able to go into a project and override any machine translation settings you may have set for your organization. For example, you'd be able to set up Google Translate for your organization, and then set up and use Microsoft Translator for just one project. Or you can use one API key for your organization and another key for a specific project.

To set up machine translation for a specific project:

  1. Select the project from the project navigation in the Dashboard.

  2. Click on Settings.

  3. In the Project Actions section on the right, click on Override organization's Machine Translation settings. A modal will open where you can edit your Machine Translation settings.


  4. Select the machine translation service you want to use.

  5. If you chose Google Translate, add your API key. If you chose Microsoft Translator Text API (latest), add your subscription key; also, while setting this up in Azure (Microsoft's cloud), make sure to select a 'Location/Region' of "Global". If you chose Microsoft Translator (deprecated), add your Client ID and Client secret. If you chose KantanMT, add your API key and engine alias.

  6. Click the Save Changes button.

Enabling Automatic Machine Translation


Automatic Machine Translation is available on the Premium plan and up as part of our Advanced Workflows feature.

If you have a translation workflow that always starts with Machine Translation, Automatic Machine Translation can save you from needing to manually start MT. Automatic MT will run whenever you add new content or update existing content to a project.

To enable automatic Machine Translation:

  1. From the Dashboard, select the project you want to enable Automatic Machine Translation for.

  2. Click on Settings.

  3. In the submenu, click on Workflow.

  4. In the Pre-translation step, enable the Machine Translation Fill-up option.

  5. You have the option to exclude languages from Machine Translation Fill-up if you want to by enabling the option "Exclude languages from Machine Translation Fillup" as shown below:


    Once you enable the setting, a list with all the project's target languages will be available for selection.

  6. Click the Save Changes button.


Please keep in mind that Google Machine translation has limits regarding the recommended maximum length for each request which is 5K characters. More information you can find here.

All four MT providers we are integrated with have their limitations in supporting variables/placeholders during the translation process. However, we have taken steps to streamline this process to the best of our ability, resulting in 99.82% of translations with variables being accurately returned.

Identifying strings translated by Machine Translation

There're two ways to know how many words were translated by MT.

Filter in Editor

You can identify the strings that were translated by MT in your resource files by applying the following filter:

More > Origin > MT: <Provider Name>


Then you can mass-select all filtered strings and see the word count.


You can see the number of words translated by MT service on the Reports page.


Machine Translation & Translation Memory Fill-up

  • If you have TM Fill-up enabled for a project, 100% Translation Memory matches will be used before Machine Translation runs.

  • Automatically machine-translated strings don't go into your Translation Memory until they've been marked as reviewed. The same is true for strings that were machine translated in bulk.

  • If you add new project languages, or enable Automatic Machine Translation and/or TM Fill-up after uploading/updating files, you'll need to manually trigger MT and fill up from TM. You can do this by clicking the Enable fill-up button in the Fill-up on-demand section in the Workflow tab of your project settings.


Through Transifex-DeepL integration, you can now set whether the translated text should lean towards formal or informal language.

This feature currently only works for target languages "DE" (German), "FR" (French), "IT" (Italian), "ES" (Spanish), "NL" (Dutch), "PL" (Polish), "PT-PT", "PT-BR" (Portuguese) and "RU" (Russian). Possible options are:

  • "more" - for a more formal language

  • "less" - for a more informal language

Formality settings can be found under Organization settings -> Machine Translation.


Continue Reading

Did this answer your question?