Blog
Product updates, guides, and customer stories.
One command from hardcoded strings to a localized app
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.
Quality Estimation: confidence scores for AI translations
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.
Context tools for AI translation: glossary, style guide, memory & screenshots
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.
10 years of Locize
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.
Type-Safe i18next in Monorepos: Introducing ResourceNamespaceMap
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.
How to internationalize an Astro site with Locize
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.
How to internationalize a Nuxt 4 app with @nuxtjs/i18n and Locize
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.
How to internationalize a React Router v7 app with remix-i18next
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.
In-context translation editor: how it works and how the major TMS platforms compare
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.