Source
Machine translation & AI quality — found from sitemap — Locize
Checked for Locize on 1 Nov 2026
- Page
- https://www.locize.com/docs/guides/using-ai-translation-effectively
- Checked
- 1 Nov 2026, 10:04 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c41fe847b492db6766fb7ed59028c4436a34d20706f439e0afb7bab175252338
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
AI qe score Report an error
“every AI translation gets a Quality Estimation score. MT output is not scored.”
-
AI credits Report an error
“Both run on credits included in every paid plan.”
-
Placeholder protection Report an error
“Placeholders, plural forms and markup are protected: MT only touches the translatable parts of a parsed segment, AI providers are instructed to leave them untouched, and the checks flag whatever slips through.”
-
Origin tracking Report an error
“Every translation permanently stores its origin (human, MT or AI) as the segment's quality property, so AI output stays identifiable in the editor and in the history”
-
Glossary Report an error
“Terms go into every AI request and are checked on every save.”
-
Styleguide Report an error
“Set tone, formality, audience and do's and don'ts once, override per language where needed, and map language codes to locales.”
-
Mcp agent Report an error
“A coding agent connected over MCP can write the note from the code when it reports new keys, and look up a screenshot with get_screenshot_context.”
-
Qe review workflow Report an error
“Low-confidence AI translations become pending reviews with a critique and a suggested revision; confident ones are saved directly.”
-
Provider own key Report an error
“Your own key (OpenAI, Gemini, Mistral, Anthropic or Lara for AI, DeepL for MT) runs on your provider account with the model you choose, keeps the data flow under your own contract, and uses no Locize credits. Available on the Growth plan and above and on usage-based subscriptions.”
-
Openai compatible endpoint Report an error
“The OpenAI provider takes an optional base URL. Leave it empty to use OpenAI. Fill it in and Locize talks to that endpoint instead, with the model name as free text, which covers a self-hosted vLLM, LiteLLM, OpenRouter and anything else that speaks the chat completions API.”
-
Worker region Report an error
“Server-side translation runs from our workers in AWS eu-west-1, which have no fixed egress address, so authenticate with the token and not with an IP allowlist.”
-
Cors requirements Report an error
“your gateway has to allow the address you open Locize at as a CORS origin: https://www.locize.app, and https://locize.app if your team uses that one.”
-
Provider order Report an error
“When several providers are configured, Locize tries your own AI keys first, then your DeepL key, then Locize AI, then Locize MT.”
-
Provider failover Report an error
“The keys it could not handle move on to the next provider in that order.”
-
Self hosted isolation Report an error
“Switch those two off in the provider settings as well if nothing at all may leave your network; keys your endpoint could not handle then simply stay untranslated until it answers again.”
-
Provider health reporting Report an error
“A failure is reported on the provider's configuration and in the Project health card of the project overview, and clears itself once the provider works again.”
-
Org shared key Report an error
“Store the key once per organization to share it across projects.”
-
AI bulk start Report an error
“Run an AI bulk action on one target language, have a native speaker check a sample, adjust glossary and styleguide, then roll out to the other languages.”
-
Automatic translation workflow Report an error
“Enable the automatic translation workflow so new keys are translated as they arrive, with the same context and the same scoring.”
-
Regular review workflow Report an error
“For languages where everything must pass a human, enable the regular review workflow for them.”
Scores citing this record
- The App Developer Machine translation & AI quality
- The App Developer Confidentiality of translated content
- The App Developer Pricing transparency
- The Data Protection Officer Machine translation & AI quality
- The Data Protection Officer Pricing transparency
- The In-House Document Translator Machine translation & AI quality
- The In-House Document Translator Confidentiality of translated content
- The In-House Document Translator Pricing transparency
- The E-Commerce Marketer Machine translation & AI quality
- The E-Commerce Marketer Translation memory, terminology & review workflow
- The E-Commerce Marketer Pricing transparency
- The Localization Manager Machine translation & AI quality
- The Localization Manager Translation memory, terminology & review workflow
- The Localization Manager Confidentiality of translated content
- The Localization Manager Pricing transparency
- The Skeptic Machine translation & AI quality
- The Skeptic Pricing transparency