Search result not found.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

On this page

Locize Docs

Introduction

Using locize

Integration

Guides / Tips & Tricks

More

Which integration option should I use?Do I have to use the locize CDN or can I host / bundle the translations directly?How is locize different from the alternatives?Why do I get “The passed json is nested too deeply.” when consuming the API?Is locize only for developers and translators or is project management within the process too?What is the regular way to update the translation memory?Is there any visibility on project’s level of completion that shows how translators are progressing?Why is my namespace suddenly a flat json?How to change the publish format?Why does my namespace contain an array with a lot of null items?Why is the pricing so complicated?How to change credit card or billing information or download the invoices?How to import translations from a file?How to manually publish a specific version?How to delete or rename a namespace?Why is there such a high download amount?Where do I find the namespace backups?How can a segment/key be copied/moved or renamed?Why a new namespace is created, when I upload a translation file?I want to use the locize CDN, but would like to have a fallback that uses local/bundled translationsIs it possible to integrate multiple projects in the same app/website?Why do I see strange new keys marked as ONE, FEW, MANY, OTHERS?How do I open and edit JSON files?i18n vs. i18nexti18next vs. locizeWord CounterHow to style text within locize?What do I have to consider if my translation texts may contain confidential information?How to translate a file and download the results?

How to translate a file and download the results?

locize is more than just a simple import/export tool for translations. It is usually used as an integrated part of your localization process - integrated in your application code or CI/CD pipeline.

But you can use locize also to import some files of your reference language, translate them to your target languages and export them back to files.

1. SignUp and create a project

Head over to our app and register. Create your first project on the dashboard after login.

2. Add your target languages

Click the "ADD LANGUAGE" button in the "..." menu of the "Start to translate" card:

Select the desired language and click "ADD":

3. Import your file

Click the "IMPORT FILE" button in the "..." menu of the "Start to translate" card:

Select the file you want to import:

Choose the appropriate file type:

Click on "IMPORT & SHOW IN CAT":If necessary change the namespace name.

Verify if all seems correct and click the "SAVE" button:

4. Translate

Deselect the "pending changes" filter and start to translate. Make sure you click the "SAVE" button: The machine translation feature is disabled during the trial.

5. Export

You have different options to export the translations.

The "all" export

If there is no language and no namespace selected in the filter, when clicking the "EXP" button, you can choose from various formats, i.e. json all (zip) This will return a zip file containing all json files.

The "single" export

If there is a language and a namespace selected in the filter, when clicking the "EXP" button, you can choose from various formats, i.e. json de This will return a json file containing the german json translations.