Internationalization

i18next8.6k★

I18next is the JavaScript internationalization framework that works with everything: React, Vue, Angular, Node.js, React Native, Deno, plain JS. It loads translation files, handles pluralization, interpolation, and context-based translations across any platform. MIT, JavaScript, 10+ years old. The plugin ecosystem is massive: backends for loading translations from files, APIs, or CDNs; language detectors for browser, cookie, or header; post-processors for formatting. The react-i18next binding is the most popular React i18n solution. The core library is fully free. All plugins are free. No premium features gated. Locize (by the same creators) is a paid translation management platform that integrates with i18next. Plans start around $15/mo for small projects. It handles translation workflow, in-context editing, and CDN delivery. You don't need it (you can use JSON files), but it solves the "how do we actually manage 40 language files" problem. Solo: free. JSON translation files work fine. Small teams: free, use Locize when managing translations across multiple translators becomes painful. Medium to large: Locize or an alternative TMS like Crowdin starts making sense. The catch: i18next is configuration-heavy. The plugin system means you're assembling pieces: a backend, a detector, a formatter, an interpolator. Getting the initial setup right takes time. And the documentation, while extensive, can be overwhelming; too many options for someone who just wants basic translations.

weblate5.9k★

Weblate is a web-based translation management platform. Translators log in, see the strings that need translating, and work through them with built-in quality checks, machine translation suggestions, and version control integration. GPL v3. Integrates directly with Git, GitHub, GitLab, and Bitbucket; translations sync automatically with your repo. Built-in glossary, translation memory, quality checks (missing plurals, inconsistent translations), and machine translation via DeepL, Google, or LibreTranslate. Self-hosting is free. Docker Compose is the recommended setup: Weblate, Postgres, Redis, and Celery for background tasks. Ops burden: moderate. Updates, database maintenance, and managing translator accounts take 3-5 hours/month. Weblate.org offers hosted plans: free for open source projects (with attribution), then $42/month (Basic, 1,000 strings), $155/month (Medium, 10,000 strings), and $380/month (Advanced, 100,000 strings) with enterprise plans above that. Solo developer with a small project: hosted free tier if open source, or self-host. Small team: $42-155/month hosted or self-host to save. Medium to large: self-host likely cheaper, but factor in ops time at your hourly rate. The catch: the GPL v3 license means any modifications you make to Weblate itself must be open-sourced. For most users (who just run it), that doesn't matter. The self-hosted setup has real dependencies; it's not a single binary. And the UI, while functional, looks dated compared to newer translation platforms.

js-lingui5.7k★

Lingui uses ICU MessageFormat, the same standard used by Android, iOS, and Java, for handling translations, plurals, and formatting. It compiles translations at build time, so your runtime bundle stays small. MIT license, TypeScript. The key differentiator is the macro system: you write t`Hello {name}` directly in your code, and Lingui's compiler extracts messages automatically. No manual key management. Supports React, Vue, and plain JavaScript. The CLI extracts all translatable strings and generates catalogs. Fully free. No paid tier, no hosted service. The entire toolchain (macros, CLI extractor, runtime, React bindings) is open source. Solo to medium teams: Lingui shines when you want automatic message extraction instead of maintaining key-value JSON files. Large teams: works well, but the smaller community means fewer third-party integrations compared to i18next. The catch: the ecosystem is smaller. i18next has 10x the stars, more plugins, more tutorials, and wider adoption. If you're joining an existing team, they're almost certainly using i18next or FormatJS. Lingui is the better-designed library, but the network effects aren't there yet.

core4.7k★

Ngx-translate is the most widely adopted internationalization library for Angular. It loads translation JSON files, swaps languages on the fly, and provides pipes and directives for translating templates. Plain terms: it makes your Angular app work in French, Spanish, Japanese, or whatever languages your users need. MIT license, TypeScript. The API is straightforward: TranslateModule in your app module, JSON files per language, {{ 'KEY' | translate }} in templates or TranslateService.instant('KEY') in code. Supports lazy loading of languages, parameterized translations, and a plugin system for different loaders (HTTP, PO files, etc.). Fully free. No paid tier, no premium features. Solo to large teams: free. The decision isn't about cost, it's about whether to use this or Angular's built-in i18n. Use ngx-translate when you need runtime language switching without a page reload. Use Angular's built-in i18n when you want compile-time optimization and don't mind separate builds per language. The catch: Angular has built-in i18n since Angular 9, and the official solution has gotten better over time. ngx-translate is still widely used because it's simpler to set up (runtime translation swapping vs. Angular's compile-time approach), but new Angular projects should evaluate the built-in i18n first. Also, ngx-translate's development has slowed. The library works, but major new features are unlikely.

tolgee-platform3.9k★

Tolgee is a localization management system. Developers push translation keys from code, translators fill in the values through a web UI, and Tolgee syncs everything back. It even lets translators click on text in your running app and edit translations in context. The self-hosted version is free and open source. You get the translation management UI, in-context translation editing (translators see your actual app and click to translate), machine translation integration (DeepL, Google, AWS), translation memory, and SDKs for React, Angular, Vue, Svelte, and more. Tolgee Cloud has a free tier (1,000 strings, 1 project), a Pay as You Go plan at $0.20/string/mo, and a Business tier at $0.35/string/mo with advanced features. Solo: overkill unless you're managing 5+ languages. Small teams: self-host free for collaborative translation. Growing teams: this is where Tolgee shines. Large orgs: compare with Crowdin and Lokalise. The catch: for small projects with a few languages, managing JSON files manually or using i18next is simpler. Tolgee's value kicks in when you have multiple translators, frequent updates, and need to coordinate translations across a team. The in-context editor requires their SDK integration, which adds a dependency to your frontend.

transloco2.2k★

Transloco is an internationalization (i18n) library: it handles translating your UI text into different languages at runtime. It's the translation layer between your app and your users' preferred language. The core library is free and open source under MIT. You get lazy-loaded translations (only load the language the user needs), runtime language switching, rich template syntax, SSR support, and a plugin system. It's the most popular i18n library in the Angular ecosystem outside of Angular's built-in i18n. Transloco has some paid plugins: the Keys Manager ($50 one-time) auto-extracts translation keys from your code, and the Optimize plugin ($50 one-time) removes unused translations at build time. There's also Transloco Locale ($50 one-time) for number/date formatting. Angular developers: this is the library to use for i18n. The free core does everything you need. The paid plugins save time but aren't required. The catch: Angular only. If you're using React or Vue, look at i18next or js-lingui. The paid plugins are nice-to-have productivity tools, not essential features; you can manage keys manually and optimize bundles yourself. Also, the documentation assumes you know Angular well.

ever-traduora2.1k★

Traduora gives you a web platform where translators can work independently, with an API you can integrate into your CI/CD pipeline. Upload your translation keys, invite translators, export in whatever format your framework needs (JSON, XLIFF, PO, Android XML, iOS strings). Self-hosting is free under AGPL-3.0. You get the full platform: multi-project support, role-based access, import/export in 15+ formats, and a REST API. Runs via Docker Compose with a Postgres or MySQL backend. The catch: the project's development pace has slowed significantly. The last major update was a while back, and the GitHub activity is sparse. The UI works but feels dated compared to newer tools like Tolgee. There's no built-in machine translation, no translation memory, and no visual context (screenshots showing where strings appear in the app). For a small team managing a few languages, it's fine. For serious localization workflows, Weblate or Tolgee offer more features and more active development.

django-rosetta1.2k★

Django-rosetta gives you a web interface to edit translation files. Instead of hunting through .po files in a text editor, translators (even non-technical ones) can log into your Django admin and translate strings through a browser. It's fully free. MIT license, no paid tier, no hosted service. Install the package, add it to your Django settings, and your admin panel gets a translation interface. It reads and writes the standard gettext .po files Django already uses. The catch: this is a developer convenience tool, not a translation management platform. There's no translation memory, no machine translation integration, no workflow for managing dozens of languages across large teams. It works well for small to medium Django projects where you have a handful of languages and a few people doing translations. For anything bigger, you need a dedicated platform like Weblate or Traduora. Also, giving translators access to your Django admin means they're inside your admin panel, which is a security consideration.