x18n checks i18n keys across code and locale files

x18n.dev

x18n finds missing, unused, or broken translation keys by cross-checking code calls against locale files. Its CLI can fail CI on errors, while search and rename commands connect translated values to their usages.

The CLI, VS Code extension, and browser UI share the same engine. Renaming can update locale files and code, with --dry-run available to inspect changes before writing; the UI also exposes MCP tools for coding agents.

Screenshot of the x18n site in a dark theme: the left side shows “i18n files, checked and maintained,” while the right shows a translation interface with keys, values in several languages, and a missing French translation.