What file formats does i18n Agent support?

i18n Agent supports 9+ file formats including JSON, YAML, CSV, XML, Markdown, Properties, and more. The service preserves structure and formatting automatically.

How much does i18n Agent cost?

i18n Agent costs €0.01 per word, which is significantly more affordable than traditional translation services that typically charge €0.15-0.25 per word.

What is MCP integration?

MCP (Model Context Protocol) integration allows i18n Agent to work directly with AI development tools like Claude Code, Cursor, and other AI-powered development environments for seamless translation workflows.

What translation file formats does i18n-convert support?

i18n-convert supports 32+ formats including Android XML (strings.xml), iOS Strings (.strings), iOS Stringsdict (.stringsdict), Flutter ARB, JSON (flat and nested), YAML, Rails YAML, XLIFF 1.2 and 2.0, Gettext PO/POT, TMX, TBX, Java Properties, CSV, TSV, and Excel (.xlsx).

Will I lose data when converting between formats?

It depends on the format pair. Converting between equally expressive formats (JSON to YAML, XLIFF 1.2 to 2.0) is lossless. Converting from a rich format to a simpler one (PO with plurals to CSV) will lose information. i18n-convert warns you about every piece of data that would be lost and lets you cancel with --dry-run.

Can I convert multiple files at once?

Yes. Pass a directory instead of a single file, and i18n-convert will process all recognized translation files in that directory. Use --out-dir to specify the output directory. You can also use shell loops for more control over individual file naming.

How do I integrate i18n-convert into my CI/CD pipeline?

Install via npm in your CI environment, then add a step that runs i18n-convert after your source translation files change. Use --force to skip interactive prompts in CI. Pair it with i18n-validate to ensure the converted files are complete and well-formed.

i18n Converter

Name: i18n Agent
Price: 0.01 EUR
Rating: 4.8 (127 reviews)
Author: i18n Agent

Convert between 32+ i18n file formats. Android XML, iOS Strings, XLIFF, PO, JSON, YAML, and more. Lossless where possible, with clear data loss warnings when not.

The Problem

Every platform speaks a different translation format. Android uses strings.xml. iOS uses .strings and .stringsdict. Web apps use JSON or YAML. Translators and TMS platforms want XLIFF or PO. When you need to share strings between platforms, you end up copy-pasting between formats, writing one-off scripts, or manually restructuring files. It's tedious, error-prone, and breaks every time a new format shows up.

A single mobile + web project can easily involve 5+ different translation file formats. Keeping them in sync manually is a losing battle.

The Solution

i18n-convert is a single CLI tool that converts between 32+ i18n file formats. It auto-detects the input format, preserves as much structure as possible, and warns you when a conversion would lose data (like plurals in CSV).

Terminal

# Auto-detect input format, convert to Android XML
i18n-convert en.json --to android-xml -o strings.xml

# iOS Strings to Gettext PO
i18n-convert Localizable.strings --to po -o messages.po

# XLIFF to Rails YAML
i18n-convert translations.xliff --to yaml-rails -o en.yml

# Pipe to stdout
i18n-convert messages.po --to json

Auto-Detection

Input format is detected automatically from file extension and content. No flags needed.

Lossless Where Possible

Metadata, comments, and plural forms are preserved when the target format supports them.

Data Loss Warnings

When a conversion would lose information, you get explicit warnings before any file is written.

Installation

Install via npm for the easiest setup, Homebrew on macOS, or build from source with Cargo.

Terminal

npm install -g @i18n-agent/i18n-convert

The npm package includes prebuilt binaries for macOS, Linux, and Windows. No Rust toolchain required.

Common Conversions

Most teams need a handful of conversions repeatedly: JSON to Android XML for mobile, PO to JSON for web, XLIFF round-trips for translator handoff. Here are some common patterns.

Batch conversion

# Convert all PO files to JSON
for f in locales/*.po; do
  i18n-convert "$f" --to json -o "${f%.po}.json"
done

# Convert entire directory
i18n-convert locales/ --to json --out-dir locales-json/

Supported Formats

i18n-convert supports 32+ formats across mobile, web, localization standards, and data exchange categories.

Mobile

Format	Extension	Flag
Android XML	.xml	--to android-xml
iOS Strings	.strings	--to ios-strings
iOS Stringsdict	.stringsdict	--to ios-stringsdict
Flutter ARB	.arb	--to arb

Web

Format	Extension	Flag
JSON (flat)	.json	--to json
JSON (nested)	.json	--to json-nested
YAML	.yml	--to yaml
YAML (Rails)	.yml	--to yaml-rails
Properties	.properties	--to properties

Localization Standards

Format	Extension	Flag
XLIFF 1.2	.xlf	--to xliff
XLIFF 2.0	.xlf	--to xliff-2
Gettext PO	.po	--to po
Gettext POT	.pot	--to pot
TMX	.tmx	--to tmx
TBX	.tbx	--to tbx

Data Exchange

Format	Extension	Flag
CSV	.csv	--to csv
TSV	.tsv	--to tsv
Excel	.xlsx	--to xlsx

Data Loss Warnings

Not all formats are equal. XLIFF supports notes, contexts, and plural forms. CSV supports none of those. When you convert from a rich format to a simpler one, i18n-convert tells you exactly what will be lost.

Terminal

$ i18n-convert plurals.po --to csv
Data loss warnings:
  [ERROR] 3 entries use plurals (not supported by CSV)
Proceed? [y/N]

# Skip prompts
i18n-convert plurals.po --to csv --force

# Preview warnings without writing
i18n-convert plurals.po --to csv --dry-run

Always use --dry-run before converting to a simpler format in production. This shows you every warning without writing any files.

CI Integration

Automate format synchronization in your CI/CD pipeline. When your source translation file changes, automatically regenerate all derived formats so mobile, web, and translator files stay in sync.

.github/workflows/format-sync.yml

# .github/workflows/format-sync.yml
name: Sync Translation Formats
on:
  push:
    branches: [main]
    paths: ['locales/en.json']

jobs:
  sync-formats:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install i18n-convert
        run: npm install -g @i18n-agent/i18n-convert

      - name: Convert JSON to Android XML
        run: i18n-convert locales/en.json --to android-xml -o android/res/values/strings.xml

      - name: Convert JSON to iOS Strings
        run: i18n-convert locales/en.json --to ios-strings -o ios/en.lproj/Localizable.strings

      - name: Commit synced formats
        run: |
          git config user.name "github-actions"
          git config user.email "[email protected]"
          git add android/ ios/
          git diff --cached --quiet || git commit -m "chore: sync translation formats"
          git push

Combine i18n-convert with i18n-validate in your CI pipeline. Convert formats first, then validate that all target files are complete and well-formed.