Generate consistent translation keys from UI text in camelCase, snake_case, kebab-case or dot.notation with optional namespaces.
One text per line
| Text | Key |
|---|---|
| Save changes | saveChanges |
| Are you sure you want to delete this project? | areYouSureYouWantToDeleteThisProject |
| Hello {name}, you have {{count}} new messages | helloYouHaveNewMessages |
| Größe ändern | grosseAndern |
| Zażółć gęślą jaźń | zazolcGeslaJazn |
| Save changes! | saveChanges_2duplicate |
Runs in your browser. Files are not uploaded unless the tool says otherwise.
Text-as-key looks convenient until the first copy change. Fixing a typo in "Save chnages" renames the key, which orphans every existing translation and forces a re-translation in each language. Two screens that show the same English word with different meanings ("Close" the window vs. "Close" to the station) collide on one key. And long sentences make code hard to read and diffs noisy. A stable, descriptive identifier avoids all three problems and lets translators work from a key with a description instead of guessing context.
checkout.payment.title keeps related strings together and makes it obvious where a key is used.checkout.submitButton survives a copy change from "Pay now" to "Place order".Each line is split into words, diacritics are optionally transliterated (ł to l, ß to ss, é to e), placeholders such as {name}, {{count}}, %s or %1$d are removed, and the remaining words are joined in the selected style. Keys are cut on a word boundary at the maximum length, and an optional prefix is prepended. When two texts produce the same key, the tool marks them and appends a counter or a short hash so the exported file stays valid.
Download the JSON file as a starting point for your source language, then upload it to SimpleLocalize and add descriptions and screenshots for translators. If your strings already live in code, the SimpleLocalize CLI can extract keys directly from i18next, FormatJS, Android and iOS projects instead of a manual list.
