Tutorials, insights, and best practices for localization and i18n — by the creators of i18next. https://www.locize.com/blog 2026-08-09T00:00:00.000Z Locize Team https://www.locize.com/blog/many-projects-one-team 2026-08-09T00:00:00.000Z

The second app is where translation management quietly breaks: the same people re-invited everywhere, offboarding by memory, one invoice per project, and no answer to "who can change the German copy?". What the account layer above your projects has to do, and how organizations in Locize do it.

https://www.locize.com/blog/i18n-without-translation-files 2026-07-08T00:00:00.000Z

A new wave of i18n tools pitches "your code is the source of truth, translation files are build artifacts". The i18next ecosystem has supported exactly this workflow for years: natural-language keys, JSX serialization via Trans, saveMissing reporting, automatic AI translation, and CDN delivery with no locale files in your repo at all. The recipe, the honest trade-offs, and what "no files" does not solve.

https://www.locize.com/blog/i18n-formatting 2026-07-07T00:00:00.000Z

Hand-rolled "$" + toFixed(2) formatting is a bug in most locales: 1,234.56 is 1.234,56 in German and 1 234 567,89 in French, and yen has no decimal places. This guide covers Intl.NumberFormat, DateTimeFormat, RelativeTimeFormat, and how i18next wires them into translation strings with {{val, number}}, currency, datetime and custom formatters.

https://www.locize.com/blog/who-uses-i18next 2026-07-06T00:00:00.000Z

We scanned the top 100,000 websites to see how many run on i18next. At least 1,534 do, from X and GitLab to Deezer, Strava, DeepL and Microsoft Power BI. Here is the data, the method, and why it matters for open source.

https://www.locize.com/blog/i18n-pluralization 2026-07-05T00:00:00.000Z

Pluralization in i18n is not "singular vs plural". English has 2 plural forms, Polish has 4, Arabic has 6, Japanese has 1. This guide covers CLDR plural categories, i18next v4 _one/_other keys, ordinals, ICU, and the mistakes that quietly break plurals.

https://www.locize.com/blog/phrase-lokalise-price-changes-2026 2026-07-02T00:00:00.000Z

Phrase removed its $135/mo Starter plan and now starts business plans at $1,245/mo. Lokalise restructured to processed-word billing and gated its top tiers. What changed, why the market is moving upmarket, and what a small team can do about it.

https://www.locize.com/blog/when-ai-translations-break 2026-07-01T00:00:00.000Z

LLM translation in CI works, until terminology drifts, a plural rule bites, or a native speaker calls the output insulting. What actually breaks in AI-only localization pipelines, why better prompts don't fix it, and how to add scoring, review and delivery without throwing your pipeline away.

https://www.locize.com/blog/continuous-localization-deployment 2026-06-25T00:00:00.000Z

A batch translation handoff is a release-blocking step hiding inside your pipeline. Here is exactly how it breaks continuous deployment, and what continuous localization wired into CI/CD looks like instead.

https://www.locize.com/blog/browser-translates 2026-06-17T00:00:00.000Z

Chrome 138 and Edge 148 ship a free, on-device Translator API that translates any page instantly, offline, and privately. It is genuinely useful, and it is not a translation management system. Here is the honest demo, the governance gap, and a recipe that uses the browser as a sanctioned fallback while your TMS stays the governed core.

https://www.locize.com/blog/ai-act-article-50 2026-06-13T00:00:00.000Z

Article 50 of the EU AI Act applies from August 2, 2026, and was not delayed by the Digital Omnibus. The Commission's final guidelines (July 20, 2026) exempt faithful AI translations from machine-readable marking, and name human-reviewed AI translation as the worked example of the Article 50(4) exemption. What that means for translated websites and apps.

https://www.locize.com/blog/inlang-interop 2026-06-12T00:00:00.000Z

i18next-cli init --inlang scaffolds an inlang project on your existing translation files: Sherlock, Fink and Paraglide work directly on your i18next JSON, Locize stays the hosted TMS on the same files, and nothing migrates.

https://www.locize.com/blog/i18next-cli-localize 2026-06-11T00:00:00.000Z

npx i18next-cli localize takes a mono-lingual app (often AI-generated) through instrumenting, key extraction, Locize setup, and AI auto-translation in a single run, ending with confidence-scored translations and CDN delivery.

https://www.locize.com/blog/ai-translation-quality-estimation 2026-06-10T00:00:00.000Z

Locize now scores every AI translation with an AI confidence estimate, surfaces low-confidence segments in the editor, and can route them straight into your review workflow.

https://www.locize.com/blog/mcp-context-tools 2026-06-09T00:00:00.000Z

New read-only Locize MCP tools give your AI agent the project glossary, style guide, translation memory, and screenshot context, so it can translate, review, and lint terminology right in your IDE.

https://www.locize.com/blog/10-years-of-locize 2026-05-27T00:00:00.000Z

A short note to mark ten years of running Locize. Where we started, what we built, who carried us, and a slice of pistachio cake from home.

https://www.locize.com/blog/i18next-monorepo-typescript 2026-05-26T00:00:00.000Z

In v26.3.0, i18next ships a new module-augmentation surface for monorepos: ResourceNamespaceMap. Each package can declare its own type-safe namespaces without colliding on CustomTypeOptions.resources.

https://www.locize.com/blog/astro-i18n 2026-05-21T00:00:00.000Z

Step-by-step ✅ Astro 6 localization using built-in i18n routing + Locize as the translation backend: build-time JSON sync via locize-cli, the build-it-yourself t() recipe, and where framework islands fit when you need live updates or in-context editing.

https://www.locize.com/blog/nuxt-i18n 2026-05-20T00:00:00.000Z

Step-by-step ✅ Nuxt 4 localization with @nuxtjs/i18n, vue-i18n, and Locize, including build-time translation sync via locize-cli, optional client-side saveMissing, and the Locize InContext editor.

https://www.locize.com/blog/react-router-i18next 2026-05-19T00:00:00.000Z

Step-by-step ✅ React Router v7 (framework mode) localization with i18next, remix-i18next 7.x, and Locize — including SSR-friendly language detection, in-context editing, and saveMissing.

https://www.locize.com/blog/in-context-translation-editor-tools-comparison 2026-05-12T00:00:00.000Z

An in-context translation editor (ICE) lets translators edit strings directly on a live website or app. Four architectural patterns exist: SDK / script injection, proxy-based, browser extension, and iframe embed. This guide compares how Locize, Lokalise, Crowdin, Phrase, SimpleLocalize, Tolgee, Localazy, and Transifex approach in-context editing, and which pattern fits which use case.