String Freeze
A deadline after which no new translatable strings can be added before release.
Definition
String freeze is a milestone in software development after which no new user-facing strings can be added or existing strings changed. This gives translators a stable target to translate against and ensures translations are complete before release. String freeze is common in waterfall localization but less relevant in continuous localization workflows.
Examples
- →Timeline: Code complete → String freeze → Translation → Release
- →Duration: typically 1-4 weeks before release
- →Exceptions: critical bug fixes may require new strings post-freeze
- →Modern alternative: continuous localization eliminates hard freezes
Frequently Asked Questions
How long should string freeze be?
Depends on: translation volume, number of languages, quality requirements. Rule of thumb: 1-2 weeks for small updates, 2-4 weeks for major releases, longer for first localization. With continuous localization, freezes can be shorter or eliminated.
Is string freeze still necessary with continuous localization?
Less critical but still useful for: major launches, marketing sync, compliance verification. Continuous localization reduces freeze length—translations happen in parallel. You may still want a 'review freeze' for final QA before big releases.