Using translation
Open an item, press Translate in the detail view, and the content swaps into your target language. A small banner shows what was translated from and to. A few things to know:- The Translate button is always visible, so it still works when the stored language was wrong to begin with.
- Toggling off shows the original again. Toggling back on is instant while you’re still on the same item.
- If the content is already in your target language, you’ll see it unchanged.
- Mixed object content only translates the long natural-language fields. Short IDs, URLs, and tokens are left alone.
- Audio items show the translated transcript with a
(translated)tag next to it.
Choosing a target language
Each reviewer picks their own target language in user settings. English is the default. Per-project defaults aren’t supported yet.Reuse and rate limits
Translations are reused for 30 days across your organization. If another moderator opens the same item within that window, they get the translation instantly. No point doing the work twice. Each organization can run up to 60 translations per minute. Hit the limit and you’ll see a retry-after toast; wait a few seconds and try again. The cap is there to keep the feature responsive when a lot of moderators are working at once.What gets translated
| Content type | Translated |
|---|---|
| Text items | Yes |
| Object items, long natural-language fields | Yes |
| Object items, short IDs, URLs, tokens | No |
| Audio transcripts | Yes |
| Images and video frames | No |
Translation only changes what you see in the reviewer UI. The original content is what’s saved on the item and used for model feedback.