Tutorial

Import existing files

Bring the translations you already have into a project that holds values of its own, and decide what happens where the two disagree. Coming from Lokalise, Crowdin, Phrase or Tolgee? Export each language as JSON there, then import it here as this tutorial shows.

3 minutes · 4 steps Updated

  1. Step 01

    Import translations

    On the project’s Translations tab, click Import and keep Translations as what you are importing — the file holds German values for keys the project already has.

    How it works: Import & Export

  2. Step 02

    Add the file and its language

    Click Continue, drop de.json from your old tool and choose German as the target language — a JSON file names no language of its own.

    How it works: Import & Export

  3. Step 03

    Resolve the conflicts

    Click Continue, read what the file would change and choose Keep existing for the values that differ, then click Import.

    How it works: Import & Export

  4. Step 04

    Check the result

    Open German with Translate and click shop.product.notifyMe — the value is the one from the file, while the values you kept are unchanged.

    How it works: Import & Export

Where to go from here

The documentation covers everything this walkthrough skipped, and the other tutorials take the next task from here.

Do it with your own files.

Start on the free tier with the locale files you already have.

Create your account