Ship every language without a second tool
Upload the string file your game already reads. Invite translators per language, watch progress per key, and export exactly what is approved.
Free while in beta.
Your file is the source of truth
Upload the JSON or CSV your build already ships. Re-uploading is a no-op for anything that has not changed, so a routine build never invalidates finished work.
- One JSON file per language, named after its code — en.json, pt-BR.json
- Or one CSV with a column per language, straight out of a spreadsheet
- Every import shows what it will change before it changes anything
Translators see one key at a time
A focused editor with the original text, your context note, placeholder warnings, and every sibling language for reference. Ctrl+Enter saves and moves on.
- Filter by untranslated, outdated, needs work, or placeholder problems
- Suggestions and translation memory so nobody phrases the same string twice
- Full history on every string, with one-click restore
Assign people to the languages they actually speak
Translators edit the languages they are assigned to. Reviewers approve them. Everyone else can still suggest.
- Per-language translator and reviewer assignments
- Approval is a separate, deliberate step from translating
- Changed original text flags every affected translation as outdated
Export what you trust
Download approved-only or everything translated, with or without a fallback to the original text — or let your build pull it over the API.
- JSON per language, or one CSV with every language side by side
- A read-only REST endpoint for your CI, using the same API keys
- Round-trips: what you export is what the importer accepts
Translate works on its own, and works better next to planning and documentation. See the API