How do I set up translation providers (DeepL, Google, Azure, Amazon)?
4 dk okumaOrta Düzey
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:
- Go to your project → Integrations tab
- Find the provider card (e.g., DeepL)
- Click Install or Enable
- Enter your API credentials
- Click Save
DeepL
- Get your API key from deepl.com/account
- Enter the DeepL API Key in the configuration
- Select Free or Pro API (different base URLs)
Google Translate
- Create a project in Google Cloud Console
- Enable the Cloud Translation API
- Create a service account and download the JSON key
- Paste the credentials in the configuration
Azure Translator
- Create a Translator resource in Azure Portal
- Copy your API Key and Region
- Enter both in the configuration
Amazon Translate
- Create an IAM user in AWS Console
- Attach the TranslateFullAccess policy
- Generate Access Key ID and Secret Access Key
- 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:
- Go to Organization Settings → Connections
- Configure LLM Providers for AI translation
- These settings apply to all projects in the organization
Next steps
Bu makale yardımcı oldu mu?