App translations, in one shared workspace.

Bring your app’s strings. Draft with people or agents, review each language, and return translations to your repository.

Lingvo translation editor with English source text, German plural drafts and separate approval controls.
Example: reviewing German plural forms before approval.View the full editor example
How it works

From source strings to reviewed translations.

  1. Bring your strings

    Push from the CLI or import a file. Keep the formats your app already uses.

  2. Create draft translations

    Write translations yourself or let an agent propose them with your project context.

  3. Review before approval

    Inspect the source and suggested wording. Accept agent drafts, then approve translations separately.

  4. Export into your app

    Pull approved translations, inspect the diff and run the checks configured for your release.

Follow the CLI setup

Your agent drafts. Your team reviews.

Your coding agent can draft translations. Lingvo keeps your glossary, string context and translation status together.

You or your team review the suggestions and approve translations separately.

See what Lingvo adds
Plural checks

The right forms for each language.

Russian uses the singular form for 21, but not 11. Try the counter to see the form change.

Lingvo checks required plural forms and placeholders. Add the QA command to CI to stop on configured errors.

lingvo qa --locale ru --fail-on error
checkout.items_countru
21
  • one21 товар
  • few21 товара
  • manynot translated yet
  • other21 товара
21 → one → "21 товар"
Supported imports and exports
eleven supported formats

Keep your app’s resource formats.

  • Android XML
    values-ru/strings.xml
  • Apple
    ru.lproj/Localizable.stringsdict
  • JSON · nested
    locales/ru.json
  • YAML
    config/locales/ru.yml

and seven more

  • iOS .strings
  • JSON (flat)
  • Java properties
  • CSV
  • XLIFF 1.2
  • Gettext PO
  • Apple String Catalog

Start with one file.

Translate one language, review the changes, and export the result back into your app.

Start your project

Use your existing localization files.