Lokalise is a project-based translation management system. We recommend keeping all platform keys within the same project. Upload iOS, Android, frontend, backend, and API language files – everything that relates to a certain app or website – to the same project. We provide you with key merging or referencing options that help you avoid repetitive work for translators. Thus, saving time and money.
Each phrase that is used in your app or website must be identified by a key and have values that represent translations into various languages. For example, the key
index.welcome would have values of Welcome in English and Benvenuto in Italian. Keys can be assigned to one or multiple platforms. Once a key is assigned to a platform, it will be included in the export for file formats related to this platform.
Lokalise automatically adjusts placeholders (format specifiers like
%d) when exporting to different file formats in the case that you are using universal placeholders. As you upload files to Lokalise, the placeholders are automatically replaced with the universal ones.
We extract key-value pairs from the files you upload (some have comments and some contain extra attributes) and store them in the Lokalise database. Keys are assigned to a file on per-platform basis (e.g. key
main_title can be assigned to file
index.json on a Web platform and to
Localizable.strings for an iOS platform). As you download files, you may choose to split keys by previously assigned files or simply group by one file per language. The latter is the preferred option, as once you start using a translation management platform like Lokalise, the optimal workflow involves performing all operations related to keys and translations using the platform and keeping language file structure to a minimum.
Each project has a unique ID (you can see it in project settings) used when referring to a project over API or CLI. Here is what it looks like:
Anyone who has access to the project can access it by the simple link: