Exports
Get your translations as a GitHub pull request with locale files, or download a ZIP of the translated project from the dashboard. Formats, encoding and line endings.
After Babelize runs, your translations are delivered as a pull request on GitHub. You can also download translated files directly from the dashboard.
Primary Export — GitHub PR
The default way to get your translations is through a GitHub pull request:
- Run Babelize on your project
- Review the PR that Babelize creates
- Merge the PR into your repository
The PR contains translated locale files, one per target language, organized to match your project structure: JSON for JavaScript projects, gettext .po (and recompiled .mo) catalogues for Django.
Dashboard Download
Download translated files directly from the dashboard:
- Open your project
- Go to the Results tab after a completed run
- Click Download
- You get a ZIP of the project with the translations applied (locale files and i18n code changes)
Export Format
Translations are exported as JSON locale files with the same keys and nesting as your source locale file, or as gettext .po/.mo catalogues for Django. See File Formats for details.
All exports use:
- UTF-8 encoding
- Unix-style line endings (LF)
- Consistent indentation matching your project style
Last updated: 2026-10-16
Versioning & Revisions
Every Babelize run creates an immutable revision with a source snapshot, output files, languages and credits used. View run history and get deterministic output.
Notifications
Get notified when translation runs finish, syncs detect changes, or project activity happens. Notification types, settings, plan availability and CLI commands.