Google Cloud Translation Provider

Google Cloud Translation Provider

By Trados AppStore Team



Google Cloud Translation Provider is a dedicated plugin that integrates directly into Trados Studio while making use of all the capabilities supported by Google Cloud Translation, including:

  • Basic and Advanced authentication
  • Custom trained engines - AutoML
  • Glossary Reference

Other standared features suported by this plugin include:

  • Custom name reference
  • Resend draft and translated segments
  • Do not include tags in the transalted segments
  • Do pre lookup find/repalce
  • Do post lookup find/replace

To learn how to use this app and for more information, please check the Documentation tab.

Technical details - Trados Studio 2022 (SR1)


  • Fixed the issue with provider slowness when opening huge files in Editor view
  • Change wiki link with Documentation link

Checksum: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Release date: 2024-01-15 - 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: 7b5b85bcec33af9e8e632576dc6c7164c9733b4ed9d40fc465b3b8eac7a233ba

Release date: 2023-06-06

Support website:

Support e-mail:

Shared products:

No related information.

MTEnhanced was a plugin that supported both the Microsoft and Google translation providers in one. Since the relese of the Google V3 API it became apparent that it was getting more and more difficult to maintain the code in this combined form. It was also apparent that the UI needed improving to support users who were struggling with the setup of the V3 API. So a decision was made to split MTEnhanced into each of the respective MT providers, now catering for a dedicated Google Cloud Translation Provider as explained in this wiki.

Minimum Requirements

How to find the plugin?

You can install the Google Cloud Translator Provider either from:

Provided you have successfully installed the Google Cloud Translator Provider plugin, you can select it within Trados Studio. 

Either as part of:

  • Default settings under File – Options – Language Pairs – Translation Memory and Automation
  • Or as part of your project settings.


Google supports 2 editions, Basic and Advanced. These options reflect the range of capabilities offered by Google Cloud Translate when using their services and based on your requirements, how you authenticate when accessing these services through the pulgin.

  • V2 Basic Translation – API Key
  • V3 Advanced Translation - JSON

Further information

You can review more detailed information about the V2 and V3 options in these wikis:

For more information about the differences between the Basic and Advanced options please see here on the Google website. 

Authentication credentials for both V2 Basic Translation and V3 Advanced, can be obtained within your Google Cloud account under APIs and Services here


There are 2 additional settings

1. Use Custom name for this provider

This allows for you to associate a friendly name, which may help in the event you have access to multiple API keys or wish to work across several custom models.


2. JSON location

V3 – Advanced Translation requires direct access to a valid JSON file which can now be supported by referencing a URL. It does however require to be downloaded and the path can be user defined by browsing

Reference Files:

Log files can be located by browsing to C:\Users\[username]\AppData\Roaming\Trados AppStore\Google Cloud TP

Known Restrictions:

Google has restrictions over the number of characters that can be used, which can be seen here

2 Basic Translation

Creating API Key

Your API keys are tied to a specific Google Cloud Project. Click here to see your list of projects.

If you don’t already have an API Key, you will need to create one by following these steps:

  1. Locate API and Services Ensure you have the correct project – Example API ProjectClick on Create CredentialsSpecify API Key

Initially the name used for reference will be numerical. The actual key will contain a sequence of numbers and letters. Once they key is generated you may notice an orange warning as seen below. By default API keys are unrestricted as marked by an orange warning as seen below. The green circle tick implies restrictions have been imposed. To prevent unauthorised use, Google recommends that you restrict where and for which APIs it can be used.

On the left you can:

  • Show your key
  • Edit your API key
  • Delete your API Key

If you edit your key you can do any of the following

  • Give it a friendly name
  • Place restrictions namely: Application and API
  • View Creation Date
  • Access API Key

Authentication within Trados Studio

When using V2 Basic Translation, all that is required is your API key. 

For future Trados Studio projects you can enable the feature “Remember key” to eliminate ongoing reliance in knowing your API key.

3 Advanced Translation

To use V3 Advanced Translation in Trados Studio, a user must have direct access to a valid JSON file.

 JSON files are dependent on:

  • A specific Google Cloud Project
  • A Service Account

Service Accounts could be linked to a bucket. Buckets that manage your AutoML and glossaries. You can access your bucket by accessing your Cloud Storage

If you want to access your custom AutoML’s and glossaries in Trados Studio, you need to authenticate using JSON files

Generating JSON files

To download a JSON file, follow these steps:

  1. Locate API and ServicesEnsure you have the correct project – Example Google Translate V3See list of Service AccountsClick on your chosen service account email
  2.  Access Keys tab
  3.  Select Add Key then JSON

Once you see this popup, check your browser’s download location for the JSON file

Creating a Service Account

If you don’t have a service account listed you can create one by clicking on Create Credentials and selecting Service Accounts

Accessing your Data Sets

In order to access the datasets for your custom translation models within Google Translate, click here

Authenticating in Trados Studio

You can reference your JSON file either by:

  1. Drag/Drop Or Browse (pre-existing download)URL

1. Drag/Drop Or Browse (pre-existing download)

To upload your JSON file, use any of these supported methods:

  • Drag & Drop
  • Browse
  • UNC path

Once your JSON file has validated, all the features supported by that JSON such as location, AutoML and glossaries are made available.


If you selected the wrong JSON file, simply reattempt to make reference to another JSON file.

 2. URL

This is ideal when sharing a JSON file among a team of people.

By enabling URL you can pate your sharing link to read the JSON file.

By validating the URL, you are able to select the range of supported capabilities that fall part of the JSON parameters

If the wrong URL was reference, simply paste in a new link. Upon confirming your JSON file, it then gets downloaded locally to the user.

Download location is based on user preference and managed via the settings.

NOTE: Dropbox as a storage and sharing platform is supported and tested, out the box.

Updating Settings Mid Project

Once you have validated and confirmed your JSON file it will be added to your Trados Studio Project.

However you can access the settings at any point

Upon clicking on settings you get a summary of the project details that cant be amended.

By clicking on provider, you are taken back to the features that V3 Advanced Translations supports such as your glossaries and AutoML that can be amended mid project and applied to your Trados Studio Project

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.