In your repo. globalize.now generates locale files and commits them to your GitHub or GitLab branch — just like any other code change. You own the files.
What the output looks like
After setup, your repo will contain a locale directory with one JSON file per language:
/locales
en.json
es.json
de.json
fr.json
Or, if you're using next-intl:
/messages
en.json
es.json
The exact location and format depends on your i18n library. The agent sets this up correctly for your framework automatically.
How updates work
When you push new code with new UI strings, globalize.now detects the diff, translates only the new or changed strings, and opens a pull request with the updated locale files. The PR is just like any other — you can review, merge, or request changes.
What if I merge a PR before translations are complete?
Not a breaking change. If you merge your code PR while the translation PR is still open, your app won't break. globalize.now also monitors your main branch — it will detect the missing translation keys and open a new PR with just the missing translations.
That said, the cleanest workflow is to wait for the translation PR, review it, and merge them together. This keeps your main branch fully translated at all times.
Can I review or edit translations in the globalize.now app?
Yes. The globalize.now app shows your translation output side-by-side with the source strings. You can review what was generated, edit specific translations that don't look right, and filter strings by language. Changes you make in the app are committed back to your locale files on the next sync.
If you prefer editing directly in your repo, that works too — your locale files are plain JSON and any editor will open them.
No vendor lock-in
Your locale files are standard JSON. If you stop using globalize.now, your translations stay in your repo and keep working exactly as they do today. You can switch to any other translation tool or manage the files manually — nothing is locked to our platform.
Do globalize.now servers store my translations?
The translation process runs on our infrastructure, but the output is committed directly to your repo. We don't maintain a separate database of your translations. Your locale files are the source of truth, and they live in your codebase.
Can I edit translations manually?
Yes. Your locale files are plain JSON — you can edit them directly or use any translation editor. On the next push, globalize.now only touches strings it generated. Manual edits to existing keys are preserved.