Translation Providers — DeepL, Google Translate & Azure Integration
Multi-Provider Translation for Professional Localization
Managing translations across a growing product means choosing the right machine translation provider — and sometimes using more than one. Better i18n gives you a unified interface to connect, monitor, and manage multiple translation providers from a single dashboard.
Whether you need DeepL's superior European language quality, Google Translate's broad language coverage, or Azure Translator's enterprise compliance, Better i18n lets you plug in the providers that fit your workflow.
Supported Translation Providers
DeepL — Live Integration
DeepL is fully integrated and ready to use. Known for producing the most natural-sounding translations, especially for European languages, DeepL is the default choice for teams that prioritize translation quality.
Key capabilities with DeepL:
- One-click translation — Translate individual keys or entire namespaces directly from the dashboard
- Glossary sync — Push your project glossary to DeepL so brand terms, product names, and technical vocabulary are translated consistently every time
- Formality control — Choose formal or informal tone per language where DeepL supports it
- Usage tracking — Monitor your character consumption and API usage in real time
Enable DeepL through integration.enableDeepL and start translating immediately.
Google Translate — Coming Soon
Google Translate support is built into the codebase and will be available in an upcoming release. Google Translate offers the broadest language coverage of any provider, supporting over 130 languages.
What to expect:
- Widest language pair coverage for reaching global audiences
- Neural Machine Translation (NMT) for improved fluency
- Cost-effective option for high-volume translation needs
- Seamless switching between providers per language pair
Azure Translator — Coming Soon
Azure Translator integration is also in development. For teams already invested in the Microsoft ecosystem, Azure Translator provides enterprise-grade translation with compliance certifications.
What to expect:
- Enterprise compliance (SOC 2, HIPAA, GDPR)
- Custom Translator for domain-specific models
- Integration with Azure Active Directory for SSO
- Regional deployment options for data residency requirements
Provider Management Operations
Better i18n provides a complete set of operations for managing your translation providers programmatically:
List and Compare Providers
Use integration.listTranslationProviders to see all available providers, their status, and supported language pairs. This makes it easy to compare coverage and choose the right provider for each target language.
Health Checks
Run integration.checkProviderHealth to verify that your configured providers are reachable and responding correctly. Health checks monitor API latency, error rates, and quota status so you can catch issues before they affect your translation workflow.
Usage Tracking
Track translation volume and costs with integration.getProviderUsage. See character counts, request volumes, and cost breakdowns per provider, per time period. Set usage alerts to avoid unexpected bills.
Default Provider Selection
Set your preferred provider with integration.setDefaultProvider. When multiple providers are enabled, the default provider handles all translation requests unless you explicitly choose a different one for specific language pairs.
Disable a Provider
Temporarily or permanently remove a provider with integration.disableProvider. Active translations are not affected — only new translation requests will stop using the disabled provider.
Glossary Sync with DeepL
One of the most powerful features of the DeepL integration is automatic glossary synchronization. When you maintain a glossary in Better i18n, those terms are automatically pushed to DeepL's glossary system.
Why glossary sync matters:
- Brand consistency — Product names, feature names, and company terminology stay untranslated or are translated exactly as you specify
- Technical accuracy — Domain-specific terms are handled correctly instead of being interpreted literally
- Reduced post-editing — Fewer corrections needed when the machine translation already respects your terminology
Glossary entries are synced bidirectionally: add a term in Better i18n, and it appears in DeepL. Update or remove it, and the change propagates automatically.
When to Use Which Provider
| Criteria | DeepL | Google Translate | Azure Translator |
|---|---|---|---|
| Translation quality | Best for European languages | Good across all languages | Good with custom models |
| Language coverage | 30+ languages | 130+ languages | 100+ languages |
| Glossary support | Native glossary sync | Custom glossary via API | Custom Translator |
| Enterprise compliance | GDPR compliant | SOC 2, ISO 27001 | SOC 2, HIPAA, GDPR |
| Best for | Quality-first teams | Maximum language reach | Microsoft ecosystem teams |
| Status | Available now | Coming soon | Coming soon |
Get Started with Translation Providers
- Navigate to your project's integration settings
- Enable DeepL and enter your API key
- Configure glossary sync for consistent terminology
- Set DeepL as your default provider
- Monitor usage and health from the provider dashboard
As Google Translate and Azure Translator become available, you will be able to add them alongside DeepL and route specific language pairs to the provider that handles them best.