Versioning and Revisions
Track translation history, compare versions, and restore previous translations.
Versioning and Revisions
Babelize maintains a complete history of your translations, enabling you to track changes, compare versions, and restore previous outputs when needed.
How Versioning Works
Every translation creates a new revision. Revisions are immutable—once created, they cannot be modified. This ensures:
- Complete audit trail
- Reproducible results
- Easy rollback capability
Revision Properties
Each revision stores:
| Property | Description |
|---|---|
| Revision ID | Unique identifier |
| Timestamp | When the translation was created |
| Source File | Original uploaded content |
| Output File | Translated content |
| Configuration | Settings used (glossary version, formality, etc.) |
| Model Version | Translation engine version |
| Character Count | Source and target character counts |
| User | Who initiated the translation |
Viewing Revision History
- Open a project
- Select a file from the translation list
- Click History to see all revisions
The history view shows:
- Timeline of all revisions
- Size of each revision
- Who created each revision
- Quick comparison options
Comparing Revisions
Compare any two revisions to see what changed:
- In the history view, select two revisions
- Click Compare
- View side-by-side or unified diff
The comparison highlights:
- Added content (green)
- Removed content (red)
- Modified content (yellow)
Restoring a Previous Revision
To revert to an earlier translation:
- Open the revision history
- Find the desired revision
- Click Restore
- Confirm the action
Restoring creates a new revision based on the historical output—it does not delete newer revisions.
Model Version Pinning
Projects can be pinned to a specific translation model version:
Automatic Updates (Default)
Your project always uses the latest model version. Re-translating content may produce improved results.
Pinned Version
Lock your project to a specific model version to ensure identical output for identical input.
To pin a version:
- Go to Project Settings → Translation Engine
- Select Pin to current version
- Note the version number for reference
To unpin:
- Return to Translation Engine settings
- Select Use latest version
Retention Policies
Revision retention depends on your plan:
| Plan | Retention Period |
|---|---|
| Free | 30 days |
| Builder | 90 days |
| Team | 1 year |
After the retention period:
- Revisions are archived
- Archived revisions can be restored on request
- Permanent deletion occurs 30 days after archival
Storage Considerations
Each revision counts toward your storage quota:
| Plan | Storage Limit |
|---|---|
| Free | 100 MB |
| Builder | 1 GB |
| Team | 10 GB |
Tips to manage storage:
- Delete unused projects
- Export and archive completed translations
- Use the cleanup tool to remove old revisions
Programmatic Access
Access revision history via the API:
Best Practices
Version Control Integration
Export translations to your version control system for additional backup and tracking.
Meaningful Descriptions
When re-translating, note why in your project documentation to maintain context.
Regular Exports
Periodically export important translations to external storage for long-term archival.
Model Version Strategy
For production content, consider pinning model versions and upgrading deliberately after testing.