How localize.dev works, from the code
How localize.dev finds hardcoded UI text, rewrites it and checks every translation, explained from the code with real output.

November 16, 2026 · 5 min read
Make Claude Code translate UI text as it writes
One feature request in a Next.js app with three languages: the setup, the hook's message, the localize call, the translations and the check, from a real Claude Code session.
Read the post
November 16, 2026 · 8 min read
Add i18n to a Next.js App Router app in one pull request
One localize.dev run on a new Next.js 16 app: what it finds, what it changes in client and server components, what you still do by hand, and how it ships as one pull request.
Read the post
November 12, 2026 · 5 min read
How localize.dev rewrites hardcoded strings without breaking your code
What the engine treats as UI text, how it edits a file without reformatting it, what it refuses to guess at, and why a second run changes nothing.
Read the post
November 11, 2026 · 3 min read
Localizing as your coding agent writes
The localize.dev MCP server and an after-edit hook let Claude Code, Cursor and other agents translate new UI text in the same change that adds it.
Read the post
November 10, 2026 · 2 min read
An i18n check for CI that needs no API key
localize-dev check finds hardcoded copy, missing plural forms and outdated translations, marks the line on the pull request, and sends nothing anywhere.
Read the post
November 6, 2026 · 2 min read
Translation keys that stay consistent across a whole app
How localize.dev names keys, reuses them for repeated text, keeps short ambiguous copy apart, and notices when source text changes after it was translated.
Read the post
November 3, 2026 · 3 min read
Checking every translation before it’s written
Placeholders, markup tags, every CLDR plural form and ICU syntax: what localize.dev checks in each machine translation, and what happens to one that fails.
Read the post