Skip to main content
Stringhive Machine Translation

Machine Translation

Machine translation gives you a first draft instantly. It's not a replacement for a human translator, but it's a solid starting point, especially for long queues.

Supported providers

Stringhive connects to six MT providers. You configure them in Settings > Machine Translation.

Provider Data region What you need
DeepL EU (Germany) API key
ModernMT EU (Italy) API key
Mistral AI EU (France) API key
Google Cloud Translation US API key
Azure Translator US API key + region
OpenAI US API key

EU-badged providers process all translation data within the European Union. If data sovereignty is a requirement for your team, choose from the EU providers.

You can have multiple providers active at the same time. Stringhive automatically routes each language pair to the best-performing provider based on translator acceptance rates. See Machine Translation Setup for details.

Translating a single string

In the editor, click the MT button next to the translation field. Stringhive sends the source text to the best provider for this language pair and fills the field with the result. Review it, edit if needed, then save.

Discarding MT output

If the suggestion isn't usable, click Discard to clear it. The discard is recorded as a rejection signal for the provider that generated it, which informs future routing decisions.

Bulk machine translation

Don't want to click MT a hundred times? Use Bulk MT from the queue toolbar. This sends all untranslated strings in the current queue to your MT provider in one go.

The results come back as Translated state, not Approved. You'll want to review them before approving, especially for strings with placeholders or domain-specific terminology.

Placeholders

Stringhive extracts placeholders from the source string before sending it to the MT provider, then reinserts them into the translation result. This means you won't get {nombre} back instead of {name}.

If the MT provider mangled a placeholder anyway (it happens with some providers), the editor will flag it with a validation warning when you go to save.

Tips for better MT output

  • Keep your source strings short and unambiguous. Long, complex sentences produce worse MT output.
  • Add glossary terms with renderings for each locale. Stringhive passes these to providers that support glossaries (DeepL, Mistral AI, and OpenAI).
  • Run multiple providers in parallel and let the quality routing surface the winner naturally rather than guessing upfront.
  • Use Bulk MT for the untranslated queue, then work through the Translated queue to review and approve.