# localize.dev > localize.dev finds the hardcoded UI text in a web, mobile or desktop app, gives each string a key, rewrites the code to use your i18n library and translates the messages with the app's context. It runs as a CLI (`npx localize-dev run`), as a GitHub Action that opens one pull request per push, and as an MCP server that coding agents call while they write code. - Edits are made in the source (AST), and a change that doesn't validate is skipped and reported instead of written. - Placeholders, plurals and markup are kept in each language's own syntax. - Teams review machine translations on the Review tab; the model flags the ones it isn't sure of, and a project glossary keeps brand names and preferred terms consistent. - Pseudo-localization (`--pseudo`, en-XA or ar-XB) finds clipped and still-hardcoded text for free, with no model call. ## Docs - [Docs](https://uselocalize.dev/docs): install, configuration, CLI commands, the GitHub Action, review and glossary - [MCP server](https://uselocalize.dev/mcp): use localize.dev from Claude Code, Cursor and other coding agents, local or hosted - [Playground](https://uselocalize.dev/playground): paste a component or page and see it translated, no account needed - [Demo](https://uselocalize.dev/demo): a 72-second film of one real run on a demo React storefront: the strings found, the code changed, the locale files and the app in Spanish, French and Arabic ## Framework guides - [React i18n, automated](https://uselocalize.dev/docs/react): Move hardcoded copy in a React app into react-i18next t() calls, with semantic keys, translations and the i18next setup, in one command or one pull request. - [Next.js i18n for the App Router, automated](https://uselocalize.dev/docs/nextjs): Localize a Next.js App Router app: server components get an awaited translator, client components useTranslation, and the language follows a cookie. One command or one pull request. - [React Native and Expo localization, automated](https://uselocalize.dev/docs/react-native): Translate a React Native or Expo app: Text, placeholders and accessibility labels become t() calls with react-i18next, set up without browser-only APIs. - [Vue i18n, automated](https://uselocalize.dev/docs/vue): Move hardcoded copy in Vue single-file components, HTML or Pug templates, into vue-i18n $t() calls, with plurals, sentences around links via , and the vue-i18n setup. - [Nuxt i18n, automated](https://uselocalize.dev/docs/nuxt): Localize a Nuxt app: templates become $t() calls and @nuxtjs/i18n is added to nuxt.config with every locale bundled and the language kept in a cookie. - [Svelte and SvelteKit i18n, automated](https://uselocalize.dev/docs/svelte): Localize Svelte and SvelteKit apps with svelte-i18n: markup becomes $_() calls, plurals become ICU messages, and SvelteKit pages render in the visitor’s language on the server. - [Angular i18n with ngx-translate, automated](https://uselocalize.dev/docs/angular): Move hardcoded copy in Angular templates into the ngx-translate pipe, with control flow, bindings and aria attributes handled, for standalone and NgModule apps, older Angular versions included. - [Astro i18n, automated](https://uselocalize.dev/docs/astro): Localize an Astro site: .astro pages get t() from the URL’s language, every static page gets a copy per language for search engines, and React, Vue or Svelte islands follow along. - [SolidJS i18n, automated](https://uselocalize.dev/docs/solid): Localize a SolidJS app: JSX gets useTranslation() from a generated i18next module whose language is a signal, so text updates in place when the language changes. - [Qwik i18n, automated](https://uselocalize.dev/docs/qwik): Localize a Qwik app: components get useTranslation() reading the language from the URL with Qwik City, and every route gets a copy per language. - [Lit localization, automated](https://uselocalize.dev/docs/lit): Localize Lit web components: text in html`` templates becomes t() calls, and an I18nController re-renders components when the language changes. - [Ember i18n with ember-intl, automated](https://uselocalize.dev/docs/ember): Localize an Ember app: Glimmer templates (.hbs, .gjs, .gts) become ember-intl {{t}} calls, with plurals, and an application route that picks the language. - [Flutter localization with ARB files, automated](https://uselocalize.dev/docs/flutter): Localize a Flutter app: Text() and hintText-style strings become AppLocalizations lookups with ARB files, ICU plurals and placeholder metadata, and gen-l10n is set up. - [Translate a static HTML website, automated](https://uselocalize.dev/docs/html): Translate a static HTML site: copy gets data-i18n markers, a small i18n.js swaps in each language, and optional translated pages per language with hreflang for SEO. - [Rails i18n for ERB views, automated](https://uselocalize.dev/docs/rails): Move hardcoded copy in Rails ERB views into t() calls with config/locales YAML, plurals with count:, available locales and a locale switch, in one command or pull request. - [Django template translation, automated](https://uselocalize.dev/docs/django): Wrap hardcoded copy in Django templates in translate and blocktranslate tags, fill the gettext .po catalogs, and switch on LocaleMiddleware, in one command or pull request. - [Laravel localization for Blade, automated](https://uselocalize.dev/docs/laravel): Move hardcoded copy in Laravel Blade views into __() calls with lang/.json translations keyed by the text, in one command or pull request. - [Android string resources, automated](https://uselocalize.dev/docs/android): Move hardcoded text in Android layouts, Jetpack Compose and View code (Kotlin or Java) into string resources: strings.xml per language, stringResource() calls, and the per-app language list. - [iOS and macOS localization with String Catalogs, automated](https://uselocalize.dev/docs/ios): Find hardcoded text in SwiftUI and UIKit, translate it into Localizable.xcstrings for every language, and wrap UIKit strings in String(localized:), in one command or pull request. ## Translating locale files - [Translate JSON locale files](https://uselocalize.dev/translate/json): Fill in missing translations in i18next, react-intl, vue-i18n, ngx-translate and Transloco JSON files, with placeholders, ICU messages and every plural form each language needs. - [Translate Rails YAML locale files](https://uselocalize.dev/translate/yaml): Fill in config/locales/.yml for Rails and other YAML dictionaries, with %{name} interpolation kept and one/other plural maps expanded to each language’s forms. - [Translate gettext .po files](https://uselocalize.dev/translate/po): Fill in empty and fuzzy entries in Django, WordPress, PHP and Python .po files, with msgstr[n] slots from each language’s Plural-Forms and msgctxt and translator comments as context. - [Translate Flutter ARB files](https://uselocalize.dev/translate/arb): Translate lib/l10n/app_en.arb into app_.arb for Flutter’s gen-l10n, with {placeholders}, ICU plural and select messages, and @key descriptions used as context. - [Translate Android strings.xml](https://uselocalize.dev/translate/strings-xml): Translate res/values/strings.xml into values- folders, with %1$s arguments, , and apostrophe escaping handled, and translatable="false" strings skipped. - [Translate Xcode String Catalogs](https://uselocalize.dev/translate/xcstrings): Fill in Localizable.xcstrings for SwiftUI and UIKit apps, with %@ and %lld specifiers, plural variations, %#@name@ substitutions and comments as context. Legacy .strings files too. - [Translate extension messages.json files](https://uselocalize.dev/translate/extension-messages): Translate _locales/en/messages.json for Chrome, Edge and Firefox extensions into every language, with $PLACEHOLDER$ tokens kept and descriptions used as context. ## Coding agents - [Localize an app with Claude Code](https://uselocalize.dev/agents/claude-code): Add the localize.dev MCP server and after-edit hook to Claude Code, so new UI text gets translation keys and translations while Claude writes the code. - [Localize an app with Cursor](https://uselocalize.dev/agents/cursor): Add the localize.dev MCP server and a Cursor rule, so Cursor's agent gives new UI text translation keys and fills in every language as it edits. - [Localize an app with Codex](https://uselocalize.dev/agents/codex): Add localize.dev to ~/.codex/config.toml so OpenAI Codex can find hardcoded UI text, give it keys and translate it, in the CLI and the IDE extension. - [Localize an app with GitHub Copilot](https://uselocalize.dev/agents/vscode): Add the localize.dev MCP server to .vscode/mcp.json, so Copilot's agent mode can give hardcoded UI text keys and fill in every language's translations. - [Localize an app with Devin (formerly Windsurf)](https://uselocalize.dev/agents/devin): Add localize.dev to Devin's mcp_config.json, the editor formerly called Windsurf, so its agent gives UI text translation keys and translates it as it codes. - [Localize an app with Gemini CLI](https://uselocalize.dev/agents/gemini-cli): Add localize.dev to Gemini CLI's settings.json so Google's terminal agent can check, localize and translate your app's UI text. - [Localize a Lovable app](https://uselocalize.dev/agents/lovable): Connect Lovable to the hosted localize.dev MCP server, and its agent finds the hardcoded text in your app, gives it keys, sets up react-i18next and translates it. The translations stay in your code as locale files, with no script or proxy in front of the site. - [Localize a Bolt app](https://uselocalize.dev/agents/bolt): Add the hosted localize.dev MCP server to Bolt's connectors, so Bolt's agent can localize the project in the editor into any language. - [Localize a v0 app](https://uselocalize.dev/agents/v0): Connect v0 to the hosted localize.dev MCP server, so it can add languages to the app it generates and fill in their translations. ## Product - [Pricing](https://uselocalize.dev/pricing): a free plan, and Pro and Team plans billed monthly or yearly - [Pricing in Markdown](https://uselocalize.dev/pricing.md): every plan with its price and limits, generated from the live plans table - [Setup skill for coding agents](https://uselocalize.dev/SKILL.md): load it in Claude Code, Cursor or Codex to set localize.dev up in a repository - [FAQ](https://uselocalize.dev/faq): what leaves your machine, translation quality, offline runs and other first questions - [Changelog](https://uselocalize.dev/changelog): every release - [Open source](https://uselocalize.dev/open-source): the Team plan free for public open-source repositories, and how to apply ## Optional - [npm package](https://www.npmjs.com/package/localize-dev): the localize-dev CLI - [GitHub](https://github.com/ufortstephen/localize-dev): the Claude Code and Cursor plugins and the MCP server listing - [Full text](https://uselocalize.dev/llms-full.txt): the guides, locale file formats, agent setup, pricing and questions in one file --- # Full text The text of the pages linked above. # Framework guides ## React i18n, automated Source: https://uselocalize.dev/docs/react Move hardcoded copy in a React app into react-i18next t() calls, with semantic keys, translations and the i18next setup, in one command or one pull request. localize.dev reads every `.tsx` and `.jsx` file, finds the copy people see (text, attributes like `placeholder` and `aria-label`, strings rendered from ternaries) and rewrites it to `t()` calls with keys named after what the copy does. Plurals become one message with every form each language needs, and sentences around links stay whole with ``. A sentence with two counts (“3 files in 2 folders”) gets a plural per count, and ordinals (`ordinal(place)` → “1st”, “2nd”) become i18next ordinal plurals in each language’s own forms. Dates, numbers and prices hardcoded to one locale (`toLocaleDateString('en-US')`, `` `$${price}` ``) are rewritten to follow the app’s language too. Setup adds: - `i18next` and `react-i18next` added to package.json (the GitHub Action updates the lockfile too) - `src/i18n.ts`, which loads every locale file and picks the language from a saved choice, then the browser - An import of it in your entry file, and a `` you can place in your header ## Next.js i18n for the App Router, automated Source: https://uselocalize.dev/docs/nextjs Localize a Next.js App Router app: server components get an awaited translator, client components useTranslation, and the language follows a cookie. One command or one pull request. Files under `app/` without `'use client'` are server components, which can’t call hooks. They get `const { t } = await getTranslation()` instead, from a generated `i18n.server` module that reads the `lang` cookie, then `Accept-Language`. Client components keep `useTranslation()`, and the root layout passes them the same language, so a page renders in one language on the server and the client. Setup adds: - `i18next` and `react-i18next`, `src/i18n.ts` and `i18n.server.ts` - An `` around the root layout, and `` that follows the language - A language switcher that sets the cookie and refreshes, so server components re-render - A `proxy.ts` serving `/es/about` with the `/about` page in Spanish, and `hreflang` links between languages, so search engines index each one ## React Native and Expo localization, automated Source: https://uselocalize.dev/docs/react-native Translate a React Native or Expo app: Text, placeholders and accessibility labels become t() calls with react-i18next, set up without browser-only APIs. Copy in ``, `placeholder`, `accessibilityLabel` and `accessibilityHint` is translated, so screen readers speak the user’s language too. The generated setup reads the device language with `Intl` instead of browser APIs, and works with Expo Router (`app/_layout`) or a classic `App` entry. Setup adds: - `i18next` and `react-i18next` - `src/i18n.ts`, imported from `app/_layout`, `App` or `index` ## Vue i18n, automated Source: https://uselocalize.dev/docs/vue Move hardcoded copy in Vue single-file components, HTML or Pug templates, into vue-i18n calls, with plurals, sentences around links via , and the vue-i18n setup. Template text and `{{ }}` become `{{ 'key' }}`, attributes become `:placeholder="'key'"`, and strings shown from `