JsonTranslate · Multilingual File Translation Workspace

Built for modern product teams

Translate multilingual files
faster, safer, and with less work

JsonTranslate is an online JSON translator for localization workflows. Translate JSON, Markdown, and TXT files, preserve keys and nested paths, and manage multilingual output for i18n projects.

Input methods
Upload / Drag / Paste

Bring JSON, Markdown, TXT, and other plain-text content directly into the workspace.

Translation modes
Incremental / Full / File / Project

Cover single-file edits, project-scale delivery, and full re-translation workflows.

Sync flow
Web Studio + CLI

Keep one continuous translation loop from the hosted workspace to your local repository.

Workspace preview

Preview the latest responsive Web Studio

Hosted by us / Bring your own key
Six capabilities

Six capabilities built around real translation workflows

From incremental translation and path mapping to task management and CLI sync, every block maps to an actual localization workflow instead of generic marketing language.

Multi-format input and smart incremental translation

Built for real i18n workflows, not just structured language files. It also handles docs and plain-text content.

Upload, drag, or paste JSON, Markdown, and TXT files.
Support file-level incremental translation, full-file translation, project incremental translation, and full-project translation.
Use Git-diff-like change detection so only added or edited content gets translated.

Project path mapping and path rules

This is not a single text box translator. Source files, target files, and directory conventions are managed together at the project level.

Map project directories and generate corresponding locale files automatically after translation.
Support common patterns such as locale folders, module folders, and locale suffixes.
Import or export full projects and deliver zipped results with directory structure preserved.

Language coverage and model usage options

Use the default hosted workflow out of the box, or plug in your team's own model resources and cost strategy.

Cover 20+ common languages including English, Chinese, Japanese, Korean, French, German, and Spanish.
Extend to 100+ languages for both core markets and long-tail localization needs.
Support hosted usage and BYOK to balance unified workflows with flexible configuration.

Responsive Web Studio design

File management, parameter setup, and translation results stay in one UI so review and comparison are easier.

The top action bar brings translation triggers, project settings, model settings, and upload entry points together.
The left source pane handles source locale, file path, file type, and original content editing.
The right result pane shows multiple target locales through tabs for quick comparison.

Task center

For project-level and batch translation workflows, task status, progress, and exceptions are displayed in a dedicated view.

Track running, queued, paused, completed, and failed tasks in one place.
Show progress, chunk-level processing state, and exception details for long-running work.
Pause or resume tasks to improve operational visibility for teams.

Full CLI support across the workflow

The CLI is not a side entrance. It is the full sync bridge between local codebases and the online workspace.

Provide the `jsontranslate` npm package for engineering workflows and local development.
Support init, login, API key setup, upload, translation, status checks, and pull-back of results.
Create one connected workflow between the Web Studio and the CLI.
Project path mapping

Import by project, generate by rule, deliver in the original structure

JsonTranslate manages file flows at the project level. Translation results no longer need manual path cleanup and can be generated directly into your existing i18n directory conventions.

Import project-level source files and organize target locale directories according to the original rules after translation.
Preserve original keys, nesting, and content structure as much as possible during translation so existing i18n organization is not broken.
Download the full project as a ZIP with the original folder hierarchy preserved for direct engineering write-back or team handoff.
Path patterns
Locale folder
i18n/messages/{locale}/{module}.json
Module folder
i18n/messages/{module}/{locale}.json
Locale suffix
i18n/messages/{module}.{locale}.json

Batch delivery and ZIP export

Export a full directory archive after project translation finishes without flattening the original folder structure. It fits engineering write-back, release delivery, and cross-role collaboration.

Languages and models

Cover 20+ common languages and support both hosted usage and BYOK

Use the hosted JsonTranslate workflow by default, or connect your own API keys and multi-provider models. Teams with existing model budgets, cost controls, or stricter compliance needs can plug in their own strategy.

Language coverage

Built-in support for 20+ common languages including English, Chinese, Japanese, Korean, French, German, Spanish, Portuguese, Russian, and Arabic, with expansion to 100+ languages.

Hosted workflow

Use the hosted JsonTranslate workflow by default for a unified experience that suits teams who want to start quickly and manage multilingual work in one place.

BYOK

Connect your own provider, model, and API key. When you use your own model resources, you can align with existing team cost strategy instead of relying on platform credit consumption.

Web Studio

A responsive workspace keeps files, parameters, and results in one interface

JsonTranslate Studio uses a translation-first responsive workspace layout. Whether you edit one file or run project-scale batch translation, the whole workflow stays in one interface.

Top action bar

Centralize translation triggers, project settings, model settings, upload, and import operations.

Start translation
Project settings
Model settings
Upload and import

Left source pane

Configure source locale, file path, and file type, then edit or inspect original content and change details.

Source locale
File path
Edit / inspect source
Change detection

Right target pane

Switch across target locales through tabs and compare results side by side before exporting or syncing.

Locale tabs
Side-by-side review
Export / sync next
Project-level actions

Task center

Status management and scheduling entry point for batch translation

Running

Show current progress, processed chunks, and remaining locale tasks.

Queued

Useful for project-scale batch work with one shared execution queue.

Paused

Interrupt long-running tasks and resume them later when needed.

Failed

Keep exception details and task context so issues are easier to investigate.

Pause running or queued tasks
Resume paused tasks
CLI

Web and CLI stay connected as one localizable delivery loop

JsonTranslate does not treat the CLI as a side feature. It is designed as the full synchronization path between your local repository and the online translation workspace.

$ jsontranslate login
$ jsontranslate auth:apikey
$ jsontranslate init
$ jsontranslate push
$ jsontranslate translate
$ jsontranslate status
$ jsontranslate pull
npm package
https://www.npmjs.com/package/jsontranslate-cli
Step 01

Initialize the local project

Configure project name, source locale, target locales, root directory, and path pattern to create a syncable translation context for the codebase.

Step 02

Upload local files and start translation

Push source files to the server for unified comparison and processing, then run incremental or full translation by file or by project.

Step 03

Check status and manage tasks

Use the CLI or task center to track queued, running, paused, and completed states so execution cadence stays visible.

Step 04

Pull the latest translation results

Sync server-side results back into the local project tree and keep the Web and CLI workflow aligned.

Plans

Choose the setup that fits your team

Start quickly with the hosted platform mode, or combine custom models, project path mapping, and CLI sync to match your team's resources.

Pricing

Simple, Transparent Pricing

Choose the plan that works best for you. All plans include access to our core features.

Annual Billing Offer
Save 50% with Annual Billing

Free

For individuals and indie developers getting started.

$0/mo
  • 50 translations / month
  • JSON Studio
  • CLI
  • Single project management
  • 3 file version history
  • 10+ languages supported
  • Custom AI models (BYOK)
  • Free forever
Most Popular

Pro

For growing teams that need faster translation workflows.

$8.80/mo
  • 500 translations / month
  • JSON Studio
  • CLI
  • 10 projects
  • 30+ languages supported
  • Custom AI models (BYOK)
  • Media asset cloud sync
  • Fast translation queue
  • 20 file version history
  • Export submission reports (CSV/PDF)
  • Priority technical email support

Max

For organizations that need scale, API access, and priority service.

$49.00/mo
  • 5,000 translations / month
  • JSON Studio
  • CLI
  • Unlimited projects
  • 100+ languages supported
  • Custom AI models (BYOK)
  • API access
  • Media asset cloud sync
  • Fastest translation queue
  • 20 file version history
  • Export submission reports (CSV/PDF)
  • Dedicated customer success manager
  • Priority response for custom feature requests
  • Early access to new features
FAQ

Frequently asked questions

These answers map directly to the current JsonTranslate workflow, including incremental translation, project path mapping, task scheduling, and CLI sync.

Rated 4.8 from 76 creator reviews
Who it is for

Built for engineering and localization teams that maintain multilingual projects over time

If you care about more than one-off translation and need structure, incremental updates, batch delivery, and local synchronization, this workflow is better suited to long-lived multilingual collaboration.

Frontend and full-stack teams managing multilingual i18n files
SaaS teams that maintain project directory structures over the long term
Localization teams focused on incremental efficiency and batch delivery
Engineering teams that want online translation capability wired into local development workflows
Contact us

Questions about product capabilities, project workflows, CLI integration, or model support?

Talk to JsonTranslate directly. Whether you are evaluating i18n file translation, project-level path mapping, or local repository sync workflows, you can continue through the website or technical support channel.