Managing translation resources efficiently and optimizing the usage of managed words ensures cost-effectiveness.
Platform owners and administrators can monitor capacity usage in the tab of the page.
The number of Strings managed words is calculated as follows:
A x B = Strings managed words
Where:
-
Ais the total number of words in the source languages stored in Strings projects at any point in time including locked keys.-
If the source language is a character-based language (e.g. Japanese, Korean, Simplified or Traditional Chinese),
Ais the total number of characters stored in Strings projects divided by two.
-
-
Bis the total number of languages configured in Strings projects including source languages.
Example
A customer has 1,000 keys. The keys contain 5,000 source language words (A) and are being translated into 5 languages from a single source language (B). Therefore, the total amount of managed words equals:
5,000 words (A) x [(5 target languages + 1 source language (B)] = 30,000 managed words
-
Legacy branches do not count towards the total number of managed words. Upon merging changes to the main branch, additional words may be added to the project and increase the number of managed words.
Important
Starting April 2026, legacy branches older than 30 days will begin to count towards Strings managed words.
-
New branching (as of December 10, 2025)
-
For new customers, branches unmerged for more than 30 days count toward managed words. Merged branches never count, regardless of whether they have been deleted. When merged, only new or updated content counts.
-
For existing customers, branches created will not count until April 2026, even if unmerged for more than 30 days.
-
-
Linked keys do not count towards the total number of managed words. Only the content of existing keys (parent keys) is counted, while child keys are not.
-
Use of Job Sync (adding languages) will impact total number of managed words.
To optimize the usage of managed words in Strings, the following strategies are recommended:
-
Regular scheduled strings audits to optimize content
Regularly review and eliminate unused or obsolete strings, languages and projects from accounts to maintain a lean and relevant word count.
-
Team education and training
Concise and clear content creation directly impacts the manageability and volume of source texts. Educating creators about the impact of word count on costs leads to more mindful content creation with a focus on brevity and relevance.
-
Remove and avoid duplications
Ensure the content management system or processes do not inadvertently duplicate strings across projects or departments.
-
Maximize strings reuse
Leverage existing strings across various projects to avoid unnecessary translations. Consistency in phraseology significantly reduces word count. If there are multiple keys with similar or duplicate content, consolidate them into single keys.