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.
Every time you run Babelize, a new revision is created. Revisions are immutable — once generated, they can't be modified.
What's Stored
Each revision records:
| Property | Description |
|---|---|
| Timestamp | When the translation was run |
| Source snapshot | Repository state at time of translation |
| Output files | Generated translation files |
| Languages | Source and target languages used |
| Credits used | AI credits consumed |
Viewing History
- Open a project
- Navigate to the results or history view
- See all past translation runs with timestamps and status
Deterministic Output
Babelize uses deterministic AI, meaning the same input + configuration produces the same output. This ensures:
- Consistent translations across runs
- Predictable results for CI/CD workflows
- No random variation between identical requests
Best Practices
- Run after merging PRs — translate against your latest main branch
- Keep source content clean — clear, well-structured source text produces better translations
Last updated: 2026-10-16
File Formats
Babelize writes JSON locale files for JavaScript frameworks and gettext .po/.mo catalogues for Django, one per language, with keys and placeholders preserved. Strings are extracted from .js, .jsx, .ts, .tsx, .vue, .html, .py and Django template files.
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.