https://github.com/opral/inlang

open file format for localizing software (i18n)
https://github.com/opral/inlang

globalization i18n localisation localization vscode

Last synced: about 2 months ago
JSON representation

open file format for localizing software (i18n)

• Host: GitHub
• URL: https://github.com/opral/inlang
• Owner: opral
• Created: 2021-08-10T19:13:21.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2026-01-11T20:16:56.000Z (about 2 months ago)
• Last Synced: 2026-01-11T23:52:48.625Z (about 2 months ago)
• Topics: globalization, i18n, localisation, localization, vscode
• Language: TypeScript
• Homepage: https://inlang.com
• Size: 233 MB
• Stars: 1,699
• Watchers: 5
• Forks: 169
• Open Issues: 15
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md

Awesome Lists containing this project

• awesome - opral/inlang - open file format for localizing software (i18n) (TypeScript)

README

          


    

  

  

  


    The open file format and ecosystem for localization (i18n)

  


  


    


    🕹️ Apps

    ·

    📄 Docs

    ·

    💙 Discord

    ·

    𝕏 Twitter

  





## The problem

i18n tools are not interoperable.

```

┌──────────┐        ┌───────────┐         ┌──────────┐

│ i18n lib │───✗────│Translation│────✗────│  Design  │

│          │        │   Tool    │         │   Tool   │

└──────────┘        └───────────┘         └──────────┘

```

Every tool has its own format, its own sync, its own collaboration layer. Cross-team work? Manual exports and hand-offs.

## The solution

An open file format. Everything interoperates.

```

┌──────────┐        ┌───────────┐         ┌──────────┐

│ Paraglide│        │   Fink    │         │ Sherlock │

└────┬─────┘        └─────┬─────┘         └─────┬────┘

     │                    │                     │

     └─────────┐          │          ┌──────────┘

               ▼          ▼          ▼

           ┌──────────────────────────────────┐

           │          .inlang file            │

           └──────────────────────────────────┘

```

One file format. Multiple tools. All interoperable. The good old Unix philosophy.

## Popular tools

- [Paraglide](https://inlang.com/m/gerre34r/library-inlang-paraglideJs) — i18n library for JS/TS with fully translated, typesafe & fast apps in minutes

- [Fink](https://inlang.com/m/tdozzpar/app-inlang-finkLocalizationEditor) — translation editor in the browser, invite collaborators to help

- [Sherlock](https://inlang.com/m/r7kp499g/app-inlang-ideExtension) — VS Code extension to translate right in your editor

- [Parrot](https://inlang.com/m/gkrpgoir/app-parrot-figmaPlugin) — see translations directly in Figma

- [CLI](https://inlang.com/m/2qj2w8pu/app-inlang-cli) — lint messages, machine translate, quality control in CI/CD

## Build your own

```ts

import { loadProjectFromDirectory } from "@inlang/sdk";

const project = await loadProjectFromDirectory({

  path: "./project.inlang",

});

const messages = await project.db.selectFrom("message").selectAll().execute();

```

The SDK gives you:

- CRUD API for translations

- SQL queries

- Plugin system for any format

- Version control via lix

[Read the docs →](https://inlang.com/documentation)

## Contributing

There are many ways you can contribute to inlang! Here are a few options:

- Star this repo

- Create issues every time you feel something is missing or goes wrong

- Upvote issues with 👍 reaction so we know what the demand for a particular issue to prioritize it within the roadmap

If you would like to contribute to the development of the project, please refer to our [Contributing guide](https://github.com/opral/monorepo/blob/main/CONTRIBUTING.md).

All contributions are highly appreciated. 🙏