Tonguestongues
Sign In

Recommended i18n Tools

Popular internationalization libraries and tools for different frameworks

React

Internationalization for React applications

react-i18next

Powerful internationalization framework based on i18next

PluralizationInterpolationLazy loadingTypeScript support
PackageGitHub

react-intl

FormatJS internationalization library for React

ICU Message FormatBuilt-in formattersRelative timeTypeScript
PackageGitHub

Lingui

Seamless internationalization in Javascript and React

Message extractionMinimal runtimeMacrosCLI tools
PackageGitHub

Next.js

i18n solutions for Next.js apps

next-globe-gen

Recommended by Tongues

Static i18n generation for Next.js

Static generationZero runtimeType safetyFile-based routing
PackageGitHub

next-i18next

i18next solution for Next.js

SSR/SSG supportAutomatic locale detectionSEO friendlyEasy setup
PackageGitHub

next-intl

Internationalization for Next.js App Router

App Router supportType-safeTime zonesRich formatting
PackageGitHub

Flutter

Localization for Flutter mobile apps

Flutter Localizations

Official Flutter internationalization

Built-in widgetsMaterial/CupertinoARB formatHot reload
PackageGitHub

intl

Dart package for internationalization

Message extractionPluralizationDate/number formattingBidirectional text
PackageGitHub

easy_localization

Easy and fast internationalization for Flutter

JSON/CSV/YAMLPluralizationGenderDynamic translations
PackageGitHub

Vue

i18n libraries for Vue.js

vue-i18n

Internationalization plugin for Vue.js

Component interpolationPluralizationDateTimeNumber formatting
PackageGitHub

Angular

Internationalization in Angular

@angular/localize

Official Angular i18n solution

Built-in CLIXLIFF/XMBAOT compilationExtraction tools
PackageGitHub

Transloco

Modern i18n library for Angular

Lazy loadingMultiple loadersTesting utilitiesScoped translations
PackageGitHub

Svelte

i18n solutions for Svelte/SvelteKit

svelte-i18n

Internationalization for Svelte

ICU formatSvelte storesTypeScriptSSR support
PackageGitHub

Best Practices

  • 1Use keys that describe the content, not the location
  • 2Keep translations close to components when possible
  • 3Implement proper pluralization rules for each language
  • 4Use ICU Message Format for complex messages
  • 5Extract and validate translations in CI/CD pipeline
  • 6Provide context for translators with descriptions