Versioning & Revisions
Every babel is kept in your project's history with its status, trigger, languages, credits and results. See past babels and how translations stay stable between them.
Every babel (one translation pass over your project) is kept in the project's history. Your code itself is versioned in git: Babelize changes it only through the pull request you merge, or the files you download.
What's Stored
Each babel records:
| Property | Description |
|---|---|
| Time and duration | When it ran and how long it took |
| Trigger | Manual, Auto (a push, with Auto-localize), or API |
| Commit | The commit it translated (GitHub projects) |
| Languages | The languages it translated into |
| Results | Files scanned, texts found and translated, translations reused, and any issues |
| Credits used | AI credits it used (none on your own key) |
Viewing History
- Babels in the sidebar lists every babel across your projects. Filter by status, trigger and project
- Babels History on a project page lists that project's babels
- Click a babel to open its results
The latest babel's results are editable; earlier babels are read-only, and their changed files aren't kept.
Stable Translations
Unchanged text keeps its translation from one babel to the next: the lockfile and translation memory reuse it instead of translating it again, so a babel only translates what's new or changed. A translation changes only when:
- its source text changes
- a glossary rule that applies to it changes
- you edit it in Results (your edit then wins on every later babel)
- you choose Re-translate everything
Changing the project's branch starts the project over: the next babel translates everything again.
Best Practices
- Translate after merging PRs — translate against your latest main branch
- Keep source content clean — clear, well-structured source text produces better translations
Last updated: 2026-11-01
Markdown & MDX Docs
Translate a docs site's Markdown and MDX pages with babelize translate: only the text readers see, code and JSX untouched, one paragraph at a time, in Fumadocs' i18n layout.
Exports
Get translations as a GitHub pull request with locale files, or download a ZIP of the translated project. Formats, encoding and line endings explained.