DeepL Translation Provider

DeepL Translation Provider

By Trados AppStore Team



This plugin provides machine translation results from the DeepL Translator found here -

You will need to purchase a subscription to DeepL Pro and you'll need an API key to use the plugin which you can obtain through DeepL sales.

Pricing for the DeepL service is available through this DeepL website.

Technical details - Trados Studio 2022 (SR1+)


  • Add "tag_handling = xml" and "preserve_formatting = true" in our requests to DeepL 
  • Don't block import when empty glossary line found.

Checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Release date: 2024-02-16 - Trados Studio 2022


  • Corrected updated plugin manifest to ensure that the plugin will not attempt to install into Trados Studio 2022 SR1. This is important because the SR1 release contains breaking changes that will cause this version of the plugin to prevent Studio from starting. There will be a further update of this plugin specifically for the 2022 SR1 release either alongside, or shortly after SR1 is made publicly available.

Checksum: fb8465dcf1a0f8d8d18dde05f7b96f87f96bf7a5d5f3ed7e3c17e94bfb198150

Release date: 2023-06-06 - Trados Studio 2021


  • Make DeepL accessible from standalone apps.

Checksum: de0e8c83d44e551c64edd74efd4bab4b98f8e56b59128b984f0a1a1fa4a85918

Release date: 2022-12-07 - SDL Trados Studio 2019


  • Removed the error 'DeepL does not support any language pair in this project' when clicking OK without an API key being added.

Checksum: d35a23168db23b0412ddae6766595741e28246658b63280ce1dd4d2f182bfff0

Release date: 2021-06-15 - SDL Trados Studio 2017

No related information.

DeepL MT Provider is an application which retrieves translation results using the DeepL Translation Service. DeepL API is a paid service and you need an API Key to use the translation provider for Trados Studio or Language Cloud.  To obtain an API Key from DeepL please visit their website -

Also note that glossary support is only available with the DeepL plugin for Trados Studio 2022 and later.

Subscriptions Supporting CAT Tool Integration

Supported: DeepL Advanced and Ultimate subscriptions.

Not Supported: Other subscription types, including DeepL Translator, Starter, DeepL API Free, DeepL API Pro, and DeepL API for Business.

Glossaries in DeepL: Understanding the Distinction

When working with DeepL, it's essential to understand the difference between glossaries created via the DeepL API through a CAT tool integration, and those created directly via the DeepL website or DeepL apps.

Glossaries Created via the DeepL API

Accessibility: These glossaries are only accessible through the specific application, tool, or plugin that created them, such as the DeepL plugin for Trados Studio.

Integration: They are not integrated with or synchronized to the glossaries created through the DeepL website or DeepL apps.

Management: Creation, deletion, and other management must be handled through the API or the specific tool that uses the API. Note that direct editing is not possible; changes require complete deletion of the glossary and recreation.

Glossaries Created via the DeepL Website and Apps

Accessibility: These glossaries are accessible through the DeepL website and DeepL's native apps.

Integration: They are not integrated with or synchronized to the glossaries created via the DeepL API.

Management: Creation, deletion, and other management must be handled through the DeepL website or apps.

Practical Implications

Separation of Resources: Be aware that glossaries created in one context (API or website/apps) are not accessible in the other.

Potential for Confusion: Users expecting a unified experience will need to understand that these glossaries are distinct and independent.

Current Recommendations from DeepL

Taken from this website:

Glossaries created via the DeepL API are distinct from glossaries created via the DeepL website and DeepL apps. This means API glossaries cannot be used on the website and vice versa.

Note that glossaries are immutable: once created, the glossary entries for a given glossary ID cannot be modified.

As a workaround for effectively editable glossaries, we suggest to identify glossaries by name instead of ID in your application and then use the following procedure for modifications:

  • download and store the current glossary's entries,
  • locally modify the glossary entries,
  • delete the existing glossary,
  • create a new glossary with the same name.

DeepL API Glossary Feature Support

Glossary Support is now offered via a dropdown based on supported language pair. To access it click on "Manage glossaries" from the settings page:

This will take you to a view where you can start working with glossaries:

The following features are supported


  1. Add new glossary (Alt+A): When creating a glossary, you have an empty database whereby you can manually add new entriesImport glossaries (Alt+Q): Use this feature when managing glossaries between platforms. By default the name of your glossary will match the name of your imported file, but this can be changed using the edit featureExport selected glossaries (Alt+X): Supported formats being *.TSV & *.CSVImport entries into selected glossaries (Alt+D): This supports the import of a file into existing glossariesDelete selected glossaries (Delete): this will delete your selected glossariesEdit glossary (Alt+E): opens a view to edit the selected glossary

Once your glossary has been created, you can't change the name of your glossary.  However you can edit term entries

When editing your glossary the following features are supported:

  • Delete entry
  • Add entry
  • Import into Glossary
  • Edit entry

Glossary Restrictions

  1. Import file format: The format of the import can either be *.TSV & *.CSV (delimited by either a semi colon or comma). The placement of source / target terms within your file, should directly correlate with the supported language direction defined during importCommon Restrictions for All Glossary Formats
  • Duplicate source entries are not allowed
  • Neither source nor target entry may be empty
  • Source and target entries must not contain any C0 or C1 control characters (including, e.g., "\t" or "\n") or any Unicode newline

  1.  Limits imposed: You can create up to 1,000 glossaries. Please keep in mind that the maximum size limit for a glossary is 10 MB and each source/target text as well as the name of the glossary is limited to 1024 UTF-8 bytes.Editing existing DeepL API Glossaries is not supported by DeepL. You can implement the edit functionality yourself by creating a new glossary with the modified entries and deleting the old glossary.Language Support: Not all languages supported by the plugin for translation have glossary support. If you have a problem please make sure you check the supported languages here:

How the plugin works

After the plugin has been installed you can access it in Studio by going to your Project Settings -> All Language Pairs->Translation Memory and Automated Translation and then click on the Use... button to expand the options:

A new window will appear where you can introduce your API Key . The API Key text box is a required field, so if you don't fill it and click OK the window will not close and instead an warning message will appear. It's also worth noting that if you cannot close the window after adding your key it may help to add a space to the end of the key and then delete it. That should activate the OK button:

To close the window use "Cancel" button or "X" from the top right of the window


Sometimes errors can be reported when trying to get a translation result from DeepL. This may be related to firewall restrictions which can be resolved by whitelisting the following domains:

For more details on this you may find this link helpful:

Checkout other plugins from this developer:
XLIFF Manager for Trados Studio


XLIFF Manager for Trados Studio

By Trados AppStore Team

The ProblemYou need to share files for translation or review and the people you are sharing with don't use Studio, they can't support SDLXLIFF, and they want to use a CAT tool. You also do so much of this you need to have a better way of managing the process. You want to be able to share one XLIFF on a multi-lingual project and have the translators complete the target language.The SolutionThe XLIFF Manager is the solution to this problem as it provides the following core features:- export your Studio projects as vanilla XLIFF 1.2 files- export your Studio projects as Google Polyglot XLIFF files- choose whether the target language should be set or not on export- choose whether you export all the segments in your files or not- import the translated XLIFF files back into Studio and update your Studio projects- map unsupported languages from your clients system in support of the import- generate reports of the changed work- be in control of the end to end process with a project management view in StudioPlanned Enhancements for the future updates- progress bars while waiting for the export/import. Useful for large projects- support for tracked changes in the import- add support for an XLIFF 2.1 export- add support for an SDLXLIFF export (to help with the management of an SDLXLIFF file workflow outside of a package)- we're open to suggestions in the RWS Community!To learn how to use this application, please please check the Documentation tab.