Every project has its space on our servers, which are covered with a CDN layer. The CDN is the fastest possible way to deliver translations anywhere, anytime for you, your users, and developers.Translation hosting
CLI can find translation keys in your project files locally, and send them to the cloud. You can also use it to upload your current translation files to manage them in SimpleLocalize. Once you translate messages, you can use CLI to download a ready to use translation file.Get started with CLI
SimpleLocalize hosting for translations acts same as a content delivery network but for your translations. We rely on Amazon S3 and Cloudflare CDN to deliver your translations to your users all over the world. You can change texts and strings in your app without any hassle, in real time, without any downtime.Learn more about translation hosting
Over 25 million people use our translation hosting service every month.
Greet your customers in their mother language
i18n terms stands for 'internationalization' and is used to describe the process of translating a software project. Number 18 is a number of letters between 'i' and 'n'. Other acronym is 'Localization' or 'L10n' in short.
i18n strings are a collection of translations for a specific language. For example, if you have a website with a
<title> tag, you can translate it in different languages. For example 'Register to our website' in English is an i18n string,
and it can be translated to 'Зарегистрируйтесь на нашем сайте' in Russian.
Managing translations is a great way to improve software for your users and developers. Users are more likely to use applications that are translated. Developers will save time and effort on managing texts in the source code. The code is easier to read and maintain when you can use a translation key instead of a block of text. The responsibility of managing translations is also more important for translators rather than developers. Product managers will be able to see the progress of translations to a new languages and see the impact on the user experience.
Translations are usually stored in files, locally in the project codebase, sometimes in a database or hosted on CDN. First, you need to decide how to import your existing translations and new translations to SimpleLocalize. Then you can use the translation editor to edit your i18n strings, or add new languages if needed. The last step is to decide how to connect SimpleLocalize with your application. There are several ways to do it:
All ways of connecting SimpleLocalize with your application are described in the integrations page.