Description
inlang is an open-source translation management system that keeps translations as files inside your Git repository. Instead of a hosted translation database, the translation files sit next to your code, so they go through the same commits, pull requests and CI checks as everything else. The inlang CLI runs checks for missing and empty translations, missing variables, missing plural forms and unused messages. Paraglide JS connects the files to your app. Translators can edit in Fink, a web editor. Developers can use Sherlock in VS Code, and designers can use Parrot in Figma. AI coding agents such as Claude Code, Codex and Cursor can edit the files, run the check command and open a pull request for a person to review. Nothing needs to be hosted, and the site says agents need no account or API key. The project is developed on GitHub.…
Preview
Highlights
- Translations stored as files in your Git repo
- inlang check finds missing and broken translations
- Agents can translate and open pull requests
- Web editor, VS Code and Figma tools
- Open source with nothing to host
Ratings & Reviews
No ratings yet
Be the first to rate inlang.
People also visit
Accent
Developer-oriented translation tool. (Source Code) BSD-3-Clause Elixir/Docker
inlang FAQ
Which AI agents work with inlang?
Any coding agent that can edit files and run a command, such as Claude Code, Codex or Cursor. The agent edits the translation files and runs the inlang check command with JSON output. No inlang account or API key is needed.
How good are agent translations?
Agents translate with your code and a glossary file in your repo as context, which generic machine translation does not have. inlang check catches missing and empty translations, missing variables, missing plural forms and unused messages. People review the wording in the pull request.
How do I move from Crowdin or Lokalise?
Export your translation files into your repo in a format a plugin can read, for example i18next JSON. inlang reads them directly. Copy your glossary into a file in the repo so the agent can read it.
Does inlang have translation memory and glossaries?
Your translation files are the memory. Agents reuse the translations already in your repo and follow a glossary file you keep there.
What are the best inlang alternatives?
Popular alternatives to inlang include Accent, Languine and doloc. See all inlang alternatives









