How do I set up translation providers (DeepL, Google, Azure, Amazon)?

4 min readIntermediate

Better i18n supports multiple machine translation providers as alternatives or supplements to the built-in AI translation. Connect DeepL, Google Translate, Azure Translator, or Amazon Translate to use their engines.

Available providers

Provider Best for Pricing model
DeepL High-quality European languages Free tier + paid plans
Google Translate Widest language support (130+) Pay per character
Azure Translator Enterprise, Microsoft ecosystem Free tier (2M chars/month)
Amazon Translate AWS ecosystem, batch translation Pay per character

Setting up a provider

All providers follow the same setup pattern:

  1. Go to your project → Integrations tab
  2. Find the provider card (e.g., DeepL)
  3. Click Install or Enable
  4. Enter your API credentials
  5. Click Save

DeepL

  1. Get your API key from deepl.com/account
  2. Enter the DeepL API Key in the configuration
  3. Select Free or Pro API (different base URLs)

Google Translate

  1. Create a project in Google Cloud Console
  2. Enable the Cloud Translation API
  3. Create a service account and download the JSON key
  4. Paste the credentials in the configuration

Azure Translator

  1. Create a Translator resource in Azure Portal
  2. Copy your API Key and Region
  3. Enter both in the configuration

Amazon Translate

  1. Create an IAM user in AWS Console
  2. Attach the TranslateFullAccess policy
  3. Generate Access Key ID and Secret Access Key
  4. Enter both in the configuration

Using providers

Once configured, translation providers appear as options when translating:

  • In the AI translation drawer — select which engine to use
  • Via API/MCP — specify the provider in translation requests
  • Fallback chain — if the primary provider fails, others can be used as fallback

Provider vs. AI translation

AI Translation (built-in) Translation Providers
Engine Google Gemini LLM Machine translation APIs
Context-aware Yes (glossary, guidelines, key names) Limited
Quality Higher for nuanced content Good for straightforward text
Speed Moderate Very fast
Cost Included in plan Separate provider costs

Recommendation: Use AI translation for UI strings and important content. Use providers for bulk translation of simple, repetitive text.

Managing providers

  • Go to Integrations → click the provider → Manage
  • Disable — temporarily stop using a provider without removing credentials
  • Update credentials — change API keys when they rotate
  • Remove — completely disconnect the provider

Organization-level providers

Translation providers can also be configured at the organization level:

  1. Go to Organization Settings → Connections
  2. Configure LLM Providers for AI translation
  3. These settings apply to all projects in the organization

Next steps

Was this article helpful?