# Lingo.dev > Lingo.dev is an AI-powered localization engine that turns LLMs into stateful translation APIs – producing consistent, production-grade translations for apps, docs, and content across every language. ## Blog - [Enterprises pay a coordination tax on localization](https://lingo.dev/en/blog/multi-team-localization-tax): Managing shared glossaries, aligning terminology across teams, and carrying the cost of ever migrating. An organization-scoped localization engine with retrieval at inference time, and forward-deployed localization engineering from the Lingo.dev team, reduce the tax. - [The Localization API](https://lingo.dev/en/blog/the-localization-api): Professional localization - source refinement, glossary enrichment, quality scoring, and optional human review - encapsulated behind a single POST. One request, any number of target locales, results via webhook. - [Introducing Lingo.dev v1.0](https://lingo.dev/en/blog/introducing-lingodotdev-v1): After proving that retrieval augmented localization reduces LLM terminology errors 17-45%, we built Lingo.dev v1.0 - a localization engineering platform where teams create stateful localization engines with per-locale models, glossaries, and quality scoring. ## Changelog - [W22 – The Lingo.dev GitHub App: continuous localization, straight from git](https://lingo.dev/en/changelog/2026-w22): The Lingo.dev GitHub App runs continuous localization on any repository, straight from git — install it, commit a config, and every push runs through your engine's async localization pipeline. AI Reviewers now run on every plan, with unlimited usage. - [W21 – Audit logs](https://lingo.dev/en/changelog/2026-w21): Audit logs land in the dashboard. Glob patterns in i18n.json. Organization invites through the MCP server. Last-used timestamps on API keys. - [W18 – Credit balance auto top-up](https://lingo.dev/en/changelog/2026-w18): Auto top-up replenishes credits when your balance dips below a threshold. New Reports charts for instruction adherence and terminology coverage. Credit balance alerts and ISO 5060 classification in triage land alongside. - [W17 – Pipeline: pre-edit, human review, AI review, back-translation as optional stages](https://lingo.dev/en/changelog/2026-w17): The localization pipeline wraps the core translate step with optional stages – pre-edit, human review, AI review, back-translation. Toggle them per engine or override per job. - [W15 – Engine provisioning API: a fresh engine, auto-configured](https://lingo.dev/en/changelog/2026-w15): The provisioning API takes a fresh engine plus a few URLs or content samples and auto-configures brand voice, glossary, and instructions. Multi-step manual setup becomes one call. - [W14 – Built-in glossary and instructions reviews](https://lingo.dev/en/changelog/2026-w14): Two built-in AI Reviewers check every glossary term and every instruction on every translation. Turn them on with a toggle instead of configuring a custom reviewer per criterion. - [W13 – Triage Jira tickets with an agent that knows your glossary](https://lingo.dev/en/changelog/2026-w13): Jira triage workflow uses an agent that suggests glossary items, instructions, and model config tweaks. AI reviewers gain access to engine context. Translation logs gain review filters. - [W12 – One POST, every locale: the async localization API ships](https://lingo.dev/en/changelog/2026-w12): Async localization API delivers any number of target locales via webhook. Glossary terms now bulk-import from CSV. Jira and GitHub integrations move to OAuth. - [W11 – v1.0 is live: configure a localization engine once, call it from anywhere](https://lingo.dev/en/changelog/2026-w11): Lingo.dev v1.0 introduces localization engines – stateful translation APIs configured once with models, brand voice, glossaries, and instructions, then called from code, MCP, or CI/CD. - [W16 – Inspect every localization job, per language, end to end](https://lingo.dev/en/changelog/2026-w16): Localization Jobs UI ships end-to-end – inspect job groups, per-language progress, payload, and webhooks. - [W20 – API keys split: personal keys, or service keys with their own role](https://lingo.dev/en/changelog/2026-w20): API keys split into Personal (inherit your role) and Service (own role, own engine scope). Sync localize returns model and cost per call. Engines gain an enable/disable toggle. - [W19 – RBAC lands: roles, per-engine access, ownership transfer](https://lingo.dev/en/changelog/2026-w19): RBAC ships – roles, per-user engine access, ownership transfer. Claude Desktop logs into the MCP server via browser OAuth. Async API gains lockedKeys; logs show retrieved context per request. ## Customers - [SoSafe replaced their translation agencies – more languages, fewer complaints](https://lingo.dev/en/customers/sosafe): How a German cybersecurity company stopped managing translation vendors and started engineering localization infrastructure. - [Laurel added a language to their product in a day – without an engineering sprint](https://lingo.dev/en/customers/laurel): How a Staff Product Manager at a legal AI company turned localization from a roadmap item into a product decision. - [How Truely Replaced 32 Uncontrolled Languages with a Localization Engine](https://lingo.dev/en/customers/truely): Truely started with raw OpenAI calls across 32 languages and no way to control terminology or quality. After switching to a localization engine on Lingo.dev, Dutch reads naturally, Russian fits the UI, and brand voice is consistent across every locale. - [How Cal.com Automated Localization for 36 Languages](https://lingo.dev/en/customers/cal-com): Cal.com was always behind on i18n despite agency spending. After deploying a localization engine on Lingo.dev, engineers stopped thinking about localization entirely – translations happen automatically in 36 languages with every push. - [How Jarvi Kept 300+ Agencies in Sync Across Languages](https://lingo.dev/en/customers/jarvi): Jarvi serves 300+ recruitment agencies across France and Europe. Translation quality and keeping content synchronized with rapid product development were the two blockers to expansion – until AI translations beat their human translations in head-to-head testing. - [How Papermark Automated Docs Localization with Lingo.dev](https://lingo.dev/en/customers/papermark): Papermark tried every i18n package and automation tool to localize their Next.js docs platform. Nothing worked until they deployed a localization engine that handled MDX files, edge cases, and 80 pages on day one. ## Docs – Api - [Localize](https://lingo.dev/en/docs/api/localize): API reference for the Lingo.dev localize endpoint - translate key-value pairs from one locale to another using a configured localization engine. - [Async Localization Pipeline](https://lingo.dev/en/docs/api/pipeline): Optional stages that wrap the core translate step in the Async Localization API - AI pre-edit, human review, AI post-edit, and back-translation drift check. Configured per engine. - [Async Localization API](https://lingo.dev/en/docs/api/localization): Submit content for translation to multiple languages in a single request - create jobs, poll status, receive results via webhooks and real-time WebSocket streaming. - [Async Provisioning API](https://lingo.dev/en/docs/api/provisioning): AI-powered engine configuration - submit links and content, receive a fully configured localization engine with brand voice, glossary, and instructions extracted automatically. - [Recognize](https://lingo.dev/en/docs/api/recognize): API reference for the Lingo.dev language recognition endpoint - detect the language of arbitrary text and get structured locale metadata. ## Docs – Cli - [Supported Formats](https://lingo.dev/en/docs/cli/supported-formats): The Lingo.dev CLI supports 25+ file formats - JSON, YAML, Markdown, MJML, Android XML, Xcode strings, Flutter ARB, PO, CSV, and more - each with a dedicated bucket type. - [Monorepos](https://lingo.dev/en/docs/cli/monorepo): Four patterns for localizing monorepos – a single recursive config that auto-discovers packages, a single config with shared locales, per-package configs with different locales, or per-package configs with separate engines. - [Extract Keys with AI](https://lingo.dev/en/docs/cli/extract-keys-with-ai): AI-assisted i18n setup for React projects via the Lingo.dev React MCP server - locale-aware routes, language switcher, and locale detection from a single prompt. - [Adding Languages](https://lingo.dev/en/docs/cli/adding-languages): Add new target languages to your Lingo.dev CLI project by updating the targets array in i18n.json - the CLI generates complete translation files for new locales in a single run. - [Automatic Retranslation](https://lingo.dev/en/docs/cli/automatic-retranslation): The Lingo.dev CLI automatically retranslates content when source text changes - it detects modified fingerprints in the lockfile and sends only the affected keys through the translation pipeline. - [i18n.json Configuration](https://lingo.dev/en/docs/cli/configuration): Complete reference for the i18n.json configuration file - locale settings, bucket patterns, provider configuration, engine connection, and advanced options. - [Existing Translations](https://lingo.dev/en/docs/cli/existing-translations): The Lingo.dev CLI integrates with projects that already have translation files - it detects existing content, fills in missing keys, and preserves your previous work. - [Key Ignoring](https://lingo.dev/en/docs/cli/key-ignoring): Exclude specific translation keys from processing so they never appear in target files - designed for debug strings, internal flags, and test data. - [Key Locking](https://lingo.dev/en/docs/cli/key-locking): Lock specific translation keys so their values are copied from source to all target files without translation - designed for brand names, technical identifiers, and values that must stay consistent. - [Key Preserving](https://lingo.dev/en/docs/cli/key-preserving): Preserve specific translation keys so they are initialized once from source and then protected from automatic updates - designed for legal text, compliance content, and copy that requires manual translation. - [Key Renaming](https://lingo.dev/en/docs/cli/key-renaming): The Lingo.dev CLI detects when translation keys are renamed and carries existing translations forward - no retranslation needed when only the key identifier changes. - [Large Projects](https://lingo.dev/en/docs/cli/large-projects): Strategies for scaling the Lingo.dev CLI to projects with thousands of keys and dozens of languages - parallel processing, targeted runs, CI/CD integration, and bucket organization. - [i18n.lock](https://lingo.dev/en/docs/cli/lockfile): The i18n.lock file tracks content fingerprints so the Lingo.dev CLI only translates new or modified strings - reducing cost, time, and unnecessary retranslation. - [Overrides](https://lingo.dev/en/docs/cli/overrides): Manually edit translations in target files and the Lingo.dev CLI preserves your changes - overrides persist across runs until the source content changes. - [Parallel Processing](https://lingo.dev/en/docs/cli/parallel-processing): The Lingo.dev CLI processes translation tasks concurrently using a worker pool - distributing locale/file combinations across multiple workers with file-system locking and automatic caching. - [Quick Start](https://lingo.dev/en/docs/cli/quick-start): Get up and running with the Lingo.dev CLI in under 5 minutes with step-by-step installation and setup. - [Remove Translations](https://lingo.dev/en/docs/cli/remove-translations): The purge command removes translations from target files by bucket, file, key, or locale - designed for cleaning up obsolete content or preparing for retranslation. - [Retranslation](https://lingo.dev/en/docs/cli/retranslation): Force retranslation of specific keys, languages, buckets, or files - designed for refreshing translations after model changes, prompt updates, or quality improvements. - [Setup](https://lingo.dev/en/docs/cli/setup): Install the Lingo.dev CLI, create an i18n.json configuration, connect a translation backend, and generate your first translations in under 5 minutes. - [Supported Locales](https://lingo.dev/en/docs/cli/supported-locales): Complete list of 100+ supported languages and regional variants with ISO 639-1 locale codes. - [Translation Keys](https://lingo.dev/en/docs/cli/translation-keys): The Lingo.dev CLI provides four key-level controls - locking, ignoring, preserving, and renaming - that determine how individual keys behave during translation. - [Translator Notes](https://lingo.dev/en/docs/cli/translator-notes): Add comments to JSONC and XCStrings files that provide context to the AI model - disambiguating terms, specifying tone, or describing where content appears in the UI. ## Docs – Cli-async - [Other commands](https://lingo.dev/en/docs/cli-async/commands): Reference for login, logout, link, unlink, whoami — the setup and identity commands that surround push and pull. - [Configuration](https://lingo.dev/en/docs/cli-async/configuration): Reference for .lingo/config.json (committed), .lingo/lock.json (committed), and the per-machine run state file at ~/.lingo/runs/.json. - [lingo pull](https://lingo.dev/en/docs/cli-async/pull): Fetch outputs from the most recent push — works across machines and across terminal sessions. Reference for conflict detection, --force, and --dry-run. - [lingo push](https://lingo.dev/en/docs/cli-async/push): Send source files to the localization engine, wait for the run to complete, write translated outputs. Reference for scoped patterns, --force, --backfill-missing, and retry behavior. - [Quickstart](https://lingo.dev/en/docs/cli-async/quickstart): Install @lingo.dev/cli, authenticate, link a project to an engine, and run the first push/pull cycle in a few minutes. ## Docs – Mcp - [Capabilities](https://lingo.dev/en/docs/mcp/capabilities): Full reference of what your AI assistant can manage through the Lingo.dev MCP server - engines, glossaries, brand voice, instructions, model configuration, AI reviewers, and API keys. - [Expand to New Locales](https://lingo.dev/en/docs/mcp/extend): Add a target language to an existing localization engine with the right model chain, brand voice, and instructions - one prompt to full locale coverage. - [Compare Engines](https://lingo.dev/en/docs/mcp/compare): A/B test two engine configurations on the same content - verify a tune improved output before promoting changes to production. - [Review Localizations](https://lingo.dev/en/docs/mcp/review): Spot-check localizations against your engine's glossary, instructions, and brand voice - get a pass/fail report with specific violations per string. - [Tune Engine Configuration](https://lingo.dev/en/docs/mcp/tune): Apply feedback to your localization engine - update glossary, brand voice, and instructions based on translation quality signals. - [Triage Localization Bugs](https://lingo.dev/en/docs/mcp/triage): Reproduce a localization issue, inspect engine state, and identify root cause - all from your AI assistant without leaving the editor. - [Debug Localization Quality](https://lingo.dev/en/docs/mcp/observe): Inspect request logs, AI Reviewer verdicts, glossary matching, and instruction compliance directly from your AI assistant - the post-mortem workflow for localization engineers. - [Localize from the Editor](https://lingo.dev/en/docs/mcp/localize): Run localization and language detection directly from your AI coding assistant - test your localization engine on real content without switching context. - [Import from Legacy Vendors](https://lingo.dev/en/docs/mcp/import): Migrate glossaries and translation memory from legacy vendors into your localization engine - parse TMX, CSV, or TBX files and seed your engine's glossary and instructions. - [Provision Engines with AI](https://lingo.dev/en/docs/mcp/provision): Create a fully configured localization engine from links and content - submit your website, docs, or style guide and receive brand voice, glossary, and instructions extracted automatically. - [Setup](https://lingo.dev/en/docs/mcp/setup): Connect the Lingo.dev MCP server to your AI coding assistant - Claude Code, Codex, Cursor, Claude Desktop, or ChatGPT - with OAuth sign-in or static API key. ## Docs – Platform - [Team](https://lingo.dev/en/docs/platform/team): Manage who has access to your Lingo.dev organization, invite members, and control permissions. - [LLM Models](https://lingo.dev/en/docs/platform/llm-models): Choose which LLM handles each locale pair in your localization engine, with ranked fallback chains for production reliability. - [Instructions](https://lingo.dev/en/docs/platform/instructions): Add named linguistic rules to your localization engine that handle specific translation patterns for each target locale. - [Glossaries](https://lingo.dev/en/docs/platform/glossaries): Enforce exact term translations or prevent translation entirely using glossary rules matched by semantic similarity. - [Brand Voices](https://lingo.dev/en/docs/platform/brand-voices): Define per-locale tone, formality, and style rules that your localization engine applies to every translation. - [AI Reviewers](https://lingo.dev/en/docs/platform/ai-reviewers): Configure built-in and custom AI reviews that evaluate translation quality - glossary compliance, instruction adherence, and custom criteria - with pass/fail verdicts or percentage scores after each localization engine request. - [Localization Engines](https://lingo.dev/en/docs/platform/engines): Build and configure a stateful translation API on Lingo.dev that combines LLM models, brand voice, glossaries, instructions, and AI reviewers. - [API Keys](https://lingo.dev/en/docs/platform/api-keys): Create and manage Personal and Service API keys that authenticate requests to the Lingo.dev localization API and MCP server. - [Audit Logs](https://lingo.dev/en/docs/platform/audit-logs): Review an append-only, tamper-evident history of state-changing actions in your organization — who did what, when, from where. - [Roles & Permissions](https://lingo.dev/en/docs/platform/rbac): Define custom roles and assign granular permissions to control who can manage your Lingo.dev organization, engines, and billing. - [Reports](https://lingo.dev/en/docs/platform/reports): Monitor translation volume, token usage, locale coverage, glossary depth, codebase change rates, and AI-reviewer quality metrics across your localization engines. - [Connect Your Engine](https://lingo.dev/en/docs/platform/connect-your-engine): Connect the Lingo.dev CLI to your localization engine so every translation run applies your brand voice, glossary, and model configuration automatically. - [Playground](https://lingo.dev/en/docs/platform/playground): Test and compare translations interactively by running your localization engines and raw LLM models side by side. ## Docs – React - [Formatting](https://lingo.dev/en/docs/react/i18n/formatting): Locale-aware number, currency, percent, date, time, relative, list, and file-size formatters — thin wrappers over native Intl APIs. - [Plurals and select](https://lingo.dev/en/docs/react/i18n/plurals-and-select): Handle count-dependent ('1 item' vs 'N items') and category-dependent ('he/she/they') translations via the runtime's plural and select helpers. - [useLingo](https://lingo.dev/en/docs/react/i18n/use-lingo): The hook that returns the active Lingo object. Translate strings, render rich React subtrees, and read locale metadata. - [LingoProvider](https://lingo.dev/en/docs/react/i18n/provider): The React context provider. Pass a locale and a messages bag; descendants read both through useLingo(). - [Quickstart](https://lingo.dev/en/docs/react/i18n/quickstart): Install @lingo.dev/react, wrap your app, write your first translation, and see it render. - [@lingo.dev/react](https://lingo.dev/en/docs/react/i18n): The runtime i18n library for React. Hash-keyed translations, ICU plurals, locale-aware formatting, and zero compile-time magic. - [Automatic Pluralization](https://lingo.dev/en/docs/react/compiler/automatic-pluralization): The Lingo.dev Compiler automatically detects plural forms in your JSX text and converts them to ICU MessageFormat, supporting all CLDR plural categories across languages. - [Best Practices](https://lingo.dev/en/docs/react/compiler/best-practices): Recommended patterns for using the Lingo.dev Compiler in production - build mode strategy, version control, model selection, text placement, and testing with pseudotranslator. - [Build Modes](https://lingo.dev/en/docs/react/compiler/build-modes): The Lingo.dev Compiler has two build modes - translate mode generates missing translations via LLM, cache-only mode uses only pre-generated translations from .lingo/metadata.json. - [Configuration Reference](https://lingo.dev/en/docs/react/compiler/configuration-reference): Complete reference for all Lingo.dev Compiler configuration options - core settings, dev tools, locale persistence, pluralization, environment variables, and per-locale model mapping. - [Custom Locale Resolvers](https://lingo.dev/en/docs/react/compiler/custom-locale-resolvers): Override default locale detection and persistence by creating custom resolver files in the .lingo/ directory - supports URL-based, cookie, localStorage, and header-based patterns. - [Development Tools](https://lingo.dev/en/docs/react/compiler/development-tools): Development tools included with the Lingo.dev Compiler - pseudotranslator for instant fake translations, local translation server for on-demand generation, and the upcoming dev widget. - [Lingo.dev Compiler](https://lingo.dev/en/docs/react/compiler): A free, open-source build-time translation system that makes React apps multilingual without modifying components - translations are extracted, generated, and embedded in per-locale bundles at build time. - [Locale Switching](https://lingo.dev/en/docs/react/compiler/locale-switching): Build a language switcher using the useLingoContext() hook - access the current locale, change it with setLocale, and configure persistence via cookies or custom resolvers. - [Manual Overrides](https://lingo.dev/en/docs/react/compiler/manual-overrides): Use the data-lingo-override attribute to provide hand-crafted translations for specific elements - overrides take precedence over AI-generated translations. - [Migration Guide](https://lingo.dev/en/docs/react/compiler/migration-guide): Migrate from lingo.dev/compiler to @lingo.dev/compiler - updated package name, simplified imports, async Next.js config, Vite plugin, and new .lingo/ directory. - [Next.js Integration](https://lingo.dev/en/docs/react/compiler/nextjs): Integrate the Lingo.dev Compiler with Next.js App Router using the withLingo() config wrapper - supports React Server Components, Webpack, and Turbopack. - [Optimization](https://lingo.dev/en/docs/react/compiler/optimization): Advanced compiler optimization techniques including tree shaking to reduce translation bundle size by 40-60%. - [Output Formats](https://lingo.dev/en/docs/react/compiler/output-formats): The Lingo.dev Compiler supports multiple output formats including TypeScript, JavaScript ESM, and JSON. - [Project Structure](https://lingo.dev/en/docs/react/compiler/project-structure): How the Lingo.dev Compiler organizes translation files - the .lingo/ directory, metadata.json cache, sourceRoot scanning, and the opt-in 'use i18n' directive mode. - [Compiler Quick Start](https://lingo.dev/en/docs/react/compiler/quick-start): Get started with the Lingo.dev Compiler in three steps: install, configure, and compile your translations for production. - [Setup](https://lingo.dev/en/docs/react/compiler/setup): Add multilingual support to a React app in under 5 minutes - install the compiler, configure your framework, add LingoProvider, and generate your first translations. - [Translation Providers](https://lingo.dev/en/docs/react/compiler/translation-providers): Configure translation providers for the Lingo.dev Compiler - use the Lingo.dev localization engine, direct LLM providers like OpenAI and Anthropic, or local models via Ollama. - [Troubleshooting](https://lingo.dev/en/docs/react/compiler/troubleshooting): Solutions for common Lingo.dev Compiler issues - missing modules, async config errors, missing translations, pseudotranslator artifacts, port conflicts, and slow builds. - [Vite + React](https://lingo.dev/en/docs/react/compiler/vite-react): Integrate the Lingo.dev Compiler with Vite and React using the lingoCompilerPlugin - full HMR support with translations injected at build time. - [Claude Code](https://lingo.dev/en/docs/react/mcp/claude-code): Set up the Lingo.dev i18n MCP server in Claude Code - one command to connect, then prompt 'Set up i18n' to implement internationalization in your project. - [Codex (OpenAI)](https://lingo.dev/en/docs/react/mcp/codex): Set up the Lingo.dev i18n MCP server in OpenAI Codex - add a TOML config entry, then prompt 'Set up i18n' to implement internationalization. - [Cursor](https://lingo.dev/en/docs/react/mcp/cursor): Set up the Lingo.dev i18n MCP server in Cursor - add a JSON config file to your project, then prompt 'Set up i18n' to implement internationalization. - [GitHub Copilot Agents](https://lingo.dev/en/docs/react/mcp/github-copilot): Set up the Lingo.dev i18n MCP server in GitHub Copilot Agents - configure the MCP and agent definition, then assign an i18n setup task. - [I18n MCP](https://lingo.dev/en/docs/react/mcp): The Lingo.dev i18n MCP server gives AI coding assistants the tools to set up internationalization in your codebase - locale-aware routes, language switcher, locale detection - from a single prompt. - [Setup](https://lingo.dev/en/docs/react/mcp/setup): Connect the Lingo.dev i18n MCP server to your AI coding assistant - one configuration step for Claude Code, Cursor, Codex, or GitHub Copilot Agents. ## Docs – React/compiler - [Automatic Pluralization](https://lingo.dev/en/docs/react/compiler/automatic-pluralization): The Lingo.dev Compiler automatically detects plural forms in your JSX text and converts them to ICU MessageFormat, supporting all CLDR plural categories across languages. - [Best Practices](https://lingo.dev/en/docs/react/compiler/best-practices): Recommended patterns for using the Lingo.dev Compiler in production - build mode strategy, version control, model selection, text placement, and testing with pseudotranslator. - [Build Modes](https://lingo.dev/en/docs/react/compiler/build-modes): The Lingo.dev Compiler has two build modes - translate mode generates missing translations via LLM, cache-only mode uses only pre-generated translations from .lingo/metadata.json. - [Configuration Reference](https://lingo.dev/en/docs/react/compiler/configuration-reference): Complete reference for all Lingo.dev Compiler configuration options - core settings, dev tools, locale persistence, pluralization, environment variables, and per-locale model mapping. - [Custom Locale Resolvers](https://lingo.dev/en/docs/react/compiler/custom-locale-resolvers): Override default locale detection and persistence by creating custom resolver files in the .lingo/ directory - supports URL-based, cookie, localStorage, and header-based patterns. - [Development Tools](https://lingo.dev/en/docs/react/compiler/development-tools): Development tools included with the Lingo.dev Compiler - pseudotranslator for instant fake translations, local translation server for on-demand generation, and the upcoming dev widget. - [Locale Switching](https://lingo.dev/en/docs/react/compiler/locale-switching): Build a language switcher using the useLingoContext() hook - access the current locale, change it with setLocale, and configure persistence via cookies or custom resolvers. - [Manual Overrides](https://lingo.dev/en/docs/react/compiler/manual-overrides): Use the data-lingo-override attribute to provide hand-crafted translations for specific elements - overrides take precedence over AI-generated translations. - [Migration Guide](https://lingo.dev/en/docs/react/compiler/migration-guide): Migrate from lingo.dev/compiler to @lingo.dev/compiler - updated package name, simplified imports, async Next.js config, Vite plugin, and new .lingo/ directory. - [Next.js Integration](https://lingo.dev/en/docs/react/compiler/nextjs): Integrate the Lingo.dev Compiler with Next.js App Router using the withLingo() config wrapper - supports React Server Components, Webpack, and Turbopack. - [Optimization](https://lingo.dev/en/docs/react/compiler/optimization): Advanced compiler optimization techniques including tree shaking to reduce translation bundle size by 40-60%. - [Output Formats](https://lingo.dev/en/docs/react/compiler/output-formats): The Lingo.dev Compiler supports multiple output formats including TypeScript, JavaScript ESM, and JSON. - [Project Structure](https://lingo.dev/en/docs/react/compiler/project-structure): How the Lingo.dev Compiler organizes translation files - the .lingo/ directory, metadata.json cache, sourceRoot scanning, and the opt-in 'use i18n' directive mode. - [Compiler Quick Start](https://lingo.dev/en/docs/react/compiler/quick-start): Get started with the Lingo.dev Compiler in three steps: install, configure, and compile your translations for production. - [Setup](https://lingo.dev/en/docs/react/compiler/setup): Add multilingual support to a React app in under 5 minutes - install the compiler, configure your framework, add LingoProvider, and generate your first translations. - [Translation Providers](https://lingo.dev/en/docs/react/compiler/translation-providers): Configure translation providers for the Lingo.dev Compiler - use the Lingo.dev localization engine, direct LLM providers like OpenAI and Anthropic, or local models via Ollama. - [Troubleshooting](https://lingo.dev/en/docs/react/compiler/troubleshooting): Solutions for common Lingo.dev Compiler issues - missing modules, async config errors, missing translations, pseudotranslator artifacts, port conflicts, and slow builds. - [Vite + React](https://lingo.dev/en/docs/react/compiler/vite-react): Integrate the Lingo.dev Compiler with Vite and React using the lingoCompilerPlugin - full HMR support with translations injected at build time. ## Docs – React/i18n - [Formatting](https://lingo.dev/en/docs/react/i18n/formatting): Locale-aware number, currency, percent, date, time, relative, list, and file-size formatters — thin wrappers over native Intl APIs. - [Plurals and select](https://lingo.dev/en/docs/react/i18n/plurals-and-select): Handle count-dependent ('1 item' vs 'N items') and category-dependent ('he/she/they') translations via the runtime's plural and select helpers. - [useLingo](https://lingo.dev/en/docs/react/i18n/use-lingo): The hook that returns the active Lingo object. Translate strings, render rich React subtrees, and read locale metadata. - [LingoProvider](https://lingo.dev/en/docs/react/i18n/provider): The React context provider. Pass a locale and a messages bag; descendants read both through useLingo(). - [Quickstart](https://lingo.dev/en/docs/react/i18n/quickstart): Install @lingo.dev/react, wrap your app, write your first translation, and see it render. ## Docs – React/mcp - [Claude Code](https://lingo.dev/en/docs/react/mcp/claude-code): Set up the Lingo.dev i18n MCP server in Claude Code - one command to connect, then prompt 'Set up i18n' to implement internationalization in your project. - [Codex (OpenAI)](https://lingo.dev/en/docs/react/mcp/codex): Set up the Lingo.dev i18n MCP server in OpenAI Codex - add a TOML config entry, then prompt 'Set up i18n' to implement internationalization. - [Cursor](https://lingo.dev/en/docs/react/mcp/cursor): Set up the Lingo.dev i18n MCP server in Cursor - add a JSON config file to your project, then prompt 'Set up i18n' to implement internationalization. - [GitHub Copilot Agents](https://lingo.dev/en/docs/react/mcp/github-copilot): Set up the Lingo.dev i18n MCP server in GitHub Copilot Agents - configure the MCP and agent definition, then assign an i18n setup task. - [Setup](https://lingo.dev/en/docs/react/mcp/setup): Connect the Lingo.dev i18n MCP server to your AI coding assistant - one configuration step for Claude Code, Cursor, Codex, or GitHub Copilot Agents. ## Docs – Workflows - [Setup](https://lingo.dev/en/docs/workflows/setup): Set up continuous localization with the Lingo.dev GitHub Action or CLI - configure the CLI, add your API key as a secret, and choose a workflow. On GitHub, the GitHub App is a managed alternative that needs no API key secret or i18n.json. - [GitHub Actions](https://lingo.dev/en/docs/workflows/github): Set up the official Lingo.dev GitHub Action to translate content on every push - with workflow examples for commit-to-main, PR-from-main, feature branches, and GPG signing. - [GitHub App](https://lingo.dev/en/docs/workflows/github-app): Set up continuous localization with the Lingo.dev GitHub App - install it once, add a repository config, and let translations update from pushes, pull requests, or PR comments. - [Advanced Patterns](https://lingo.dev/en/docs/workflows/advanced): Advanced CI/CD localization patterns - choosing a workflow, verifying translation completeness with --frozen, and resolving i18n.lock merge conflicts. - [Bitbucket Pipelines](https://lingo.dev/en/docs/workflows/bitbucket): Set up Lingo.dev continuous localization in Bitbucket Pipelines using the official Pipe - with workflow examples for direct commits and pull request modes. - [GitLab CI/CD](https://lingo.dev/en/docs/workflows/gitlab): Set up Lingo.dev continuous localization in GitLab CI/CD using the official Docker image - with pipeline examples for commit and merge request workflows. ## Docs - [Continuous Localization](https://lingo.dev/en/docs/workflows): Lingo.dev keeps translations in sync with your code - use the GitHub App to run localization automatically, or the GitHub Action and CLI to run it in your own pipeline. Translate changed content, commit results or open pull requests, and keep incomplete translations out of production. - [@lingo.dev/cli](https://lingo.dev/en/docs/cli-async): A CLI for the Lingo.dev localization engine: push source files, wait while the engine translates them, pull the results — works across machines via lockfile-tracked run state. - [Localization MCP](https://lingo.dev/en/docs/mcp): Give AI coding assistants direct access to your localization engine configuration through the Lingo.dev MCP server. - [Lingo.dev CLI](https://lingo.dev/en/docs/cli): The Lingo.dev CLI reads your i18n.json config, discovers translatable content, computes a delta against the lockfile, sends only changed strings through your localization engine, and writes results back to disk. - [The Localization Engineering Platform](https://lingo.dev/en/docs/platform): Lingo.dev is an AI-powered localization engineering platform. It helps product teams turn LLMs into stateful translation APIs - to produce consistent, production-grade translations for apps, docs, and content across every language. - [Localization API](https://lingo.dev/en/docs/api): API reference for the Lingo.dev localization endpoints, including key-value translation and language detection. ## Engineering - [Every RAG-based localization pipeline has the same blind spot](https://lingo.dev/en/engineering/rag-localization-glossary-retrieval): Sentence-level embeddings dissolve phrase-level glossary terms. N-gram decomposition, adaptive retrieval modes, and continuous threshold calibration fix the granularity mismatch that makes terminology drift invisible. ## Guides - [CI/CD Localization Workflows](https://lingo.dev/en/guides/ci-cd-workflows): How to automate localization in CI/CD using Lingo.dev - run it with the GitHub App, or the CLI in GitHub Actions, GitLab CI, or Bitbucket Pipelines to translate on every push. - [Translation API](https://lingo.dev/en/guides/translation-api): How to localize content programmatically using the Lingo.dev localization API - send key-value data, get translations back through a configured localization engine. - [Engine Setup with the Localization MCP](https://lingo.dev/en/guides/mcp-engine-setup): Configure a localization engine using AI coding assistants through the Lingo.dev MCP server - brand voices, glossaries, instructions, and model routing from a single conversation. - [Ruby on Rails Localization with the i18n API](https://lingo.dev/en/guides/ruby-on-rails-localization): How to localize a Ruby on Rails app using config/locales YAML files with the Lingo.dev CLI and GitHub Actions – from project setup to automated CI/CD translations. - [Next.js App Router Localization with Markdoc](https://lingo.dev/en/guides/markdoc-nextjs-localization): How to localize a Next.js App Router site that renders Markdoc content with the Lingo.dev CLI and GitHub Actions – from project setup to automated CI/CD translations. - [Android App Localization with strings.xml](https://lingo.dev/en/guides/android-app-localization): How to localize an Android app using strings.xml resource files with the Lingo.dev CLI and GitHub Actions - from project setup to automated CI/CD translations. - [iOS App Localization with Xcode String Catalogs](https://lingo.dev/en/guides/ios-app-localization): How to localize an iOS app using Xcode String Catalogs (.xcstrings) with the Lingo.dev CLI and GitHub Actions - from project setup to automated CI/CD translations. - [Jira Triage](https://lingo.dev/en/guides/triage): Automatically triage Jira tickets for localization relevance using AI - add a label, get surgical suggestions for glossary items, instructions, and brand voice updates, approve with one click. - [Emails Localization](https://lingo.dev/en/guides/emails): How to localize transactional and marketing emails using Lingo.dev - translate email templates at build time with the CLI or at runtime with the localization API. - [Localization Guides](https://lingo.dev/en/guides/): Step-by-step guides for localizing APIs, web apps, mobile apps, emails, static content, CMS platforms, and CI/CD workflows using a Lingo.dev localization engine. - [Mobile App Localization](https://lingo.dev/en/guides/mobile-app): How to localize iOS, Android, Flutter, and React Native applications using Lingo.dev - translate native resource files through a configured localization engine. - [Static Content Localization](https://lingo.dev/en/guides/static-content): How to localize Markdown, MDX, JSON, YAML, subtitles, and other static files using Lingo.dev - translate documentation, blog posts, and structured content through a configured localization engine. - [Web App Localization](https://lingo.dev/en/guides/web-app): How to localize React, Next.js, Vue, Angular, Svelte, PHP, Python, and Rails web applications using Lingo.dev - translate resource files through a configured localization engine. ## Research - [Retrieval Augmented Localization Cuts LLM Terminology Errors 17-45%](https://lingo.dev/en/research/retrieval-augmented-localization): Raw LLMs translating isolated paragraphs produce 17-45% more terminology errors without a domain glossary. Holistic quality metrics miss this entirely.