Common JSON layouts
Upload your existing translation files. StringsOS understands both simple and nested JSON.
Documentation
Bring in your translation files and download approved translations. You can preview every change first.
Navigation
Upload or download translation files any time, without connecting GitHub.
1Workspace
2Project
3Settings
4Import / Export
Files
Language detection
StringsOS reads the language from the file name, like fr-FR.json or es.json.
Checks and preview
Before anything changes, StringsOS checks your file for errors and shows exactly what will change.
Export any time
You can always download your translations as JSON, even if you use GitHub. You’re never locked in.
Placeholders stay safe
Some text has blanks that your app fills in later, like {{name}} or {0}. These are called placeholders. When you import, StringsOS checks that translations keep them, so your app doesn’t break.
- Error checking
- Placeholders kept intact
- Preview before you apply
Import
Upload your existing translation files (JSON) to bring your translations into StringsOS. Files from popular tools like i18next and react-intl work too. Before anything is applied, you’ll see a preview of the new text that will be added and any existing text that will change.
Export
When your translations are approved, download them as JSON files for your app. Only approved translations are included, so drafts and unreviewed text never reach your live product.
Fixing errors
If a translation is missing a placeholder that your original text has, or changes it, StringsOS flags an error. Open the translation and make sure every placeholder, like {count} or %s, is there and written exactly the same.
Next: skip the files
Tired of passing files around? Connect GitHub and send translations as a pull request.
GitHub
Upload a file and manage it in a simple editor.
Free during beta · No credit card required