In-depth review: i18n Web

226 words · Editorial

i18n Web positions itself as a specialized localization tool for developers and content creators who need to translate JSON and Markdown files with high accuracy and structural integrity. Unlike general-purpose translation services that often mangle code-like formats, i18n Web leverages state-of-the-art LLM models to handle context-dependent phrases while preserving the original file structure—keys, indentation, code blocks, and front matter remain intact. This makes it particularly useful for localizing React or Vue apps that rely on JSON i18n files, or for translating Markdown documentation sites without breaking formatting. The tool also offers in-editor file checking and editing, allowing users to review and tweak translations before export, which reduces post-processing overhead. Batch translation capabilities further streamline workflows for small teams managing multilingual content, though the credit-based system on paid plans requires careful planning: the $7.9/month Basic plan provides 30 credits, while the $29.9/month Pro plan offers 250 credits with faster processing and larger file limits. The free tier is severely limited—only 2 files, 30 key-value pairs per JSON, and 2000 characters per document—making it suitable only for evaluation or tiny projects. Notably, i18n Web does not support YAML or XML files, which may be a dealbreaker for some developers. For its target audience, the tool delivers focused value, but potential buyers should assess their typical file sizes and translation volume against the tiered limits to avoid unexpected costs.

Who it's built for

Developers localizing web or mobile apps
Why it fits
i18n Web handles JSON key-value pairs with structure preservation, ensuring that keys and nested objects remain intact after translation. This is critical for app localization where file format integrity is non-negotiable.
Best value
The Pro plan's ability to translate up to 300 key-value records per JSON file and support for all languages in one go makes it suitable for medium-sized app projects.
Caution
The free tier only allows 30 key-value pairs per file, which may be insufficient for even small apps. Developers on a budget should evaluate the Basic or Pro plans.
Content creators translating Markdown docs
Why it fits
LLM accuracy ensures that context-dependent phrases in documentation are translated naturally, while structure preservation maintains code blocks, links, and formatting.
Best value
The in-editor file checking and editing feature allows content creators to review and tweak translations before final export, reducing manual post-processing.
Caution
Document length limits per file (2000 characters on free, 40000 on Pro) may require splitting large docs. Also, no explicit support for YAML or XML front matter.
Freelancers or small teams managing multilingual content
Why it fits
Batch translation capabilities allow uploading multiple files and translating them into several languages simultaneously, streamlining workflow for multilingual projects.
Best value
The credit system on paid plans provides predictable usage: 30 credits on Basic for occasional needs, 250 on Pro for regular batch jobs.
Caution
Credits are consumed per translation job; heavy users may need to monitor usage to avoid running out mid-month. No rollover of unused credits mentioned.

Key features

Accurate Translation with LLMs
Uses state-of-the-art LLM models to translate text, improving quality over traditional engines by understanding context and nuance.
Benefit
Produces more natural and contextually appropriate translations, especially for idiomatic expressions or technical jargon.
Limitation
LLM translation can be slower than traditional engines, and the free tier requires waiting; Pro plan offers fast translation.
Structure Preservation
Maintains the original structure of JSON and Markdown files, including keys, indentation, code blocks, and formatting.
Benefit
Eliminates manual re-structuring after translation, saving time and reducing errors in file format.
Limitation
Only guaranteed for JSON, Markdown, and TXT; other formats like YAML or XML may not preserve structure.
In-Editor File Checking and Editing
Allows users to review and edit translated content directly within the tool before downloading.
Benefit
Enables quick corrections and quality assurance without switching to another editor, streamlining the workflow.
Limitation
Editing capabilities may be basic (no syntax highlighting or advanced find/replace); complex edits might require external tools.
Batch Translation Capabilities
Supports translating multiple files and multiple target languages in a single operation.
Benefit
Significantly reduces time for large localization projects by processing all files at once.
Limitation
Batch translation consumes credits per file/language combination; the free plan does not support batch (only 2 files, 2 languages).

Real-world use cases

Localizing a React App with JSON i18n Files
Developer
1. Scenario
  A developer has a React app with a single JSON file containing 200 key-value pairs for English. They need to translate it into Spanish, French, and German.
2. Solution
  Upload the JSON file to i18n Web, select the three target languages, and run the translation. The tool preserves all keys and nested structure, outputting separate JSON files for each language.
3. Outcome
  Saves hours of manual translation or messy spreadsheet work; the developer can directly drop the output files into the app's i18n folder.
Translating a Markdown Documentation Site
Content Creator
1. Scenario
  A technical writer has a Markdown file with code snippets, links, and front matter. They need to translate it into Japanese while keeping formatting intact.
2. Solution
  Upload the Markdown file, select Japanese, and translate. The tool preserves code blocks (with language tags), links, and YAML front matter. The writer reviews and tweaks a few phrases using the in-editor checker.
3. Outcome
  Ensures that technical documentation remains readable and functional in the target language, with no broken formatting.
Batch Translating Multiple TXT Files for a Blog
Freelancer
1. Scenario
  A freelancer manages a multilingual blog with 10 TXT articles in English. They need to translate all articles into Italian and Portuguese simultaneously.
2. Solution
  On the Pro plan, upload all 10 TXT files, select Italian and Portuguese, and run batch translation. The tool processes each file and provides downloadable translated versions.
3. Outcome
  Completes in minutes what would take days manually; the freelancer can then review and publish with minimal effort.

Pros & cons

Pros

Accurate and localized translations using LLMs
Preserves the structure of the original content
Supports multiple file types (JSON, Markdown, TXT)
Easy to use interface
Offers both free and paid tiers
Option to skip object keys during JSON translation

Cons

Free tier has usage limits on file size, number of files, and language versions
Translation needs to wait in the free tier
Sensitive content may be blanked out in the translated output
Paid credits are required for larger files and more language versions

Pricing

Parsed from stored tiers (HTML or plain text). If a line is missing, check the notes below — confirm on the vendor site before purchasing.

Free

$0 No subscription and payment. Select up to 2 files, 2 language versions for each translation. For each json files, translate up to 30 key-value records. For each documents, translate up to about 2000 characters. Translation needs to wait.

Basic

$7.9/ credit

$7.9 Monthly Subscription. 30 credits. If you mainly translate json file a few articles, this level will meet your needs! Everything else is the same as Premium.

Pro

$29.9/ credit

$29.9 Monthly Subscription. 250 credits. Fast translation without waiting for. Select up to 10 files and all languages for each translation. For each json files, translate up to 300 key-value records. For each documents, translate up to about 40000 characters. Translated files are saved for 15 days.

Frequently asked questions

What file types does i18n Web support?Workflow

i18n Web supports JSON, Markdown, and TXT files. It does not currently support YAML, XML, or other formats. Structure preservation is guaranteed for these three types.

How does the credit system work on the Pro plan?Pricing

The Pro plan costs $29.9/month and provides 250 credits. Each translation job consumes credits based on the number of files and target languages. For example, translating 1 file into 2 languages uses 2 credits. Unused credits do not roll over to the next month.

Can I translate more than 30 key-value pairs on the free plan?Limitations

No. The free plan limits JSON files to 30 key-value records per file. For documents, the limit is 2000 characters. To translate larger files, you need a Basic ($7.9/month) or Pro ($29.9/month) subscription.

Does i18n Web preserve Markdown formatting like code blocks?Workflow

Yes. i18n Web preserves Markdown structure including code blocks, links, lists, and front matter. The LLM translates text within these elements while keeping the formatting intact.

Is there a way to try the Pro features before subscribing?Pricing

No free trial is mentioned. However, the free plan lets you test translation quality and structure preservation with small files. To evaluate batch translation or larger limits, you would need to subscribe to a paid plan.

Browse all