Locale review, without the spreadsheet

Your strings speak code.Your team shouldn't have to.

Bring locale JSON into one calm review space. QA and product owners refine the words; developers keep valid keys, placeholders, and export-ready files.

checkout.json
live review

key path

cart.title

cart.items

cart.pay

EN · source

Your basket

{count} items

Proceed to checkout

DE · review

Ihr Warenkorb

{count} Artikel

Zur Kasse

3 keys · placeholders intactready → de.json

The broken handoff

Spreadsheets erase the structure developers need.

On a multilingual project, developers often generate a first translation file with AI. Clients then ask for wording changes. Converting JSON to a spreadsheet, waiting for edits, and rebuilding the mapping by hand is slow and error-prone. i18n Manager keeps the source of truth as structured keys and values so everyone edits the same file you will ship.

Built around locale files

One review loop, from import to commit.

Core features match the product: projects, languages, import with conflict review, roles, search, history, and JSON export.

  • Import locale files

    Upload .json or .js (module.exports) files. Nested objects become dot-notation keys. Conflicts are reviewed before anything is overwritten.

  • Share with QA and owners

    Add registered teammates by email and assign Owner, Developer, QA, or Read-only access so copy review happens in the same project.

  • Export in one click

    Download a language as JSON, or export every language at once, and drop the files straight back into your application.

  • Multiple projects

    Keep each product or client in its own project with its own languages, keys, members, and history.

  • History and restore

    See who changed a key and when. Soft-deleted keys live in Deleted Keys until an owner or developer restores them.

  • Placeholder safety

    Edits that drop or rename {variable} tokens are blocked so interpolation in your app stays intact.

A real sequence, in three moves

File in. Review together. File out.

  1. 01 / 03

    Create a free account

    Sign up with name, email, and password. Create a project for the app you are localizing.

  2. 02 / 03

    Add languages and import

    Add codes such as en and de, then import your existing translation file. Resolve conflicts if values already exist.

  3. 03 / 03

    Collaborate, then export

    Invite QA or the product owner. They edit wording in the grid. You export JSON and ship it.

Full walkthrough of every screen

Clear editing boundaries

Give everyone the right pen.

Only the project owner can add members. Teammates must already have an i18n Manager account.

  • Owner

    Languages, keys, members, and project deletion.

  • Developer

    Add, edit, and delete keys. Import files. Cannot manage languages or members.

  • QA

    Edit existing translation values only — ideal for copy review.

  • Read-only

    View translations without changing them.

Before you import

Questions, resolved.

Pricing, file formats, roles, and how to use the software with your team.

Bring your next locale file.

Create an account, import a file, and invite your first reviewer. There is no paid tier.

Create a free account