Getting Started


inlang is not an i18n library
Inlang works on top of translation files. How you "feed" those translation files into your software/app is up to you and the job of dedicated i18n libraries.

I am starting to translate my software from scratch

You need an i18n library to load translations from files into your software. Since inlang is build on top of Mozillas Fluent system, choose an i18n library that supports Fluent translation files. For a list of libraries and examples, go to the awesome-fluent-i18n repository.

I am already internationalizing/localizing/translating my software

Inlang is build on top of Mozillas Fluent system. If your translation files are in the Fluent format (ending with .ftl), inlang works out of the box. In case your translation files are not not in the Fluent format (ending with .json, .string, etc.), you need a converter.

VSCode extension (takes 60 seconds)

  1. Install the VSCode extension download link.

  2. Create an inlang.config.json file in your project.

    • Either run npx @inlang/cli init in the terminal (but node must be installed).
    • Or manually create the JSON config:
      For an example and the config schema go to the config reference.

Translation Management (takes 2 minutes)

  1. Create a project in the dashboard.
  2. Import your translations either via copy & paste or the CLI.

Video tutorial

  1. 0:00 Introduction
  2. 0:27 Setup und use the VSCode extension.
  3. 1:47 Let non-technical team members and translators manage translations.