How Babelize Works

When you run Babelize on a project, here's what happens under the hood.

Pipeline

GitHub Repo → Code Scan → String Extraction → AI Translation → PR with Translations

1. Code Scan

Babelize clones your repository and scans for translatable content:

• Detects your framework (React, Next.js)
• Finds existing i18n resource files (JSON, YAML, etc.)
• Identifies hardcoded strings in your components

2. String Extraction

Translatable strings are extracted and deduplicated:

• JSX text content
• i18n key-value pairs
• Metadata and alt text
• Variables and interpolations are preserved as placeholders

3. AI Translation

The translation engine processes each string:

1. Checks your glossary for predefined translations
2. Analyzes surrounding context for accuracy
3. Generates translations using AI
4. Ensures identical source strings get identical translations

4. Output

Babelize generates translated resource bundles and raises a PR:

• .json or .i18n files per language
• Clean file structure matching your project
• PR includes a diff summary of all changes

Deterministic Translations

Babelize guarantees the same input + configuration produces the same output:

• Fixed model versions — pinned per project, updated only when you opt in
• Seed-based generation — eliminates randomness between identical requests
• Configuration hashing — glossary + language pair + settings produce a stable hash

Processing Times

Times vary based on repository size, number of target languages, and current system load.