JSON translation that only touches what should change
Upload a JSON file, and DeepL translates only the string values. Your keys, numbers, booleans, and null values stay exactly as they were—no schema rewrites, no broken payloads, no manual cleanup after translation.
Trusted by over 200,000 businesses globally
Why translate JSON files with DeepL?
Maybe you're localizing app strings, translating structured content from a CMS, or handling metadata payloads. DeepL translates JSON the way your schema expects: string values only, with your structure intact.
Only string values translated at any nesting depth
DeepL file translation leaves keys, numbers, booleans, and null alone, and it traverses nested objects and arrays at every depth. Deeply structured payloads translate correctly without flattening.
Embedded HTML and Markdown, preserved
DeepL translates the natural-language text inside rich-text string values, common in CMS payloads like Contentful, keeping the surrounding markup intact.
Large content set translation, one batch
You can translate multiple JSON files into multiple target languages at once, so you don’t have to process files one at a time.
Enterprise-grade encryption, compliance, and privacy
DeepL encrypts files in transit and at rest, and they’re deleted after translation on Pro plans. DeepL AI is GDPR, ISO 27001, SOC 2 Type II, HIPAA, and BSI C5 Type 2 compliant. Learn how DeepL secures your data.
Commitment to quality
Read about DeepL's quality scores, including 90% faster translation cycles.
What to know before you upload JSON files
Because of JSON's structure, there are some best practices to keep in mind when translating your file:
- Files must be strict, parseable JSON without trailing commas and comments: JSONC-style extensions aren't supported
- The upload limit is 1 MB, regardless of plan: large metadata payloads may need to be split or translated string-by-string via the text-translation API instead
- Review complex rich-text values after translation: DeepL attempts to preserve embedded HTML or Markdown inside string values. Still, check complex rich-text content before publishing
- Encode a value as a non-string to protect it from translation: Numbers, booleans, and null are never translated. Converting a value to one of these (or pre-processing it out of the file) is how to exclude it.
How do I translate JSON files with DeepL?
Visit the web translator then follow these steps:
- Log in to your DeepL Pro or DeepL API account
- Select the "Translate files" tab
- Upload or drag-and-drop your JSON file
- Set your source language, or let DeepL detect it
- Select your target language.
- Click Translate
- Download your translated file
Translation tailored to developers and localization teams
JSON carries the strings behind your app, your CMS, and your data, without any of the surrounding presentation. DeepL translates it without breaking what holds it together.
- Developers and API integrators: translate JSON payloads programmatically, with nested structures, arrays, and non-string values handled automatically
- i18n and software localization teams: translate locale files and app string tables directly, without extracting strings into a separate format first
- Content teams using structured CMS platforms: translate rich-text fields from Contentful and similar CMS apps, with embedded markup preserved.
How DeepL Pro drives JSON translation
Structured content rarely comes in one file or one language. We engineered DeepL Pro to cover the batch.
- Translate multiple files and into multiple target languages at once
- Use a glossary so tech and brand terms stay the same across files
- Activate formal or informal tones, fine-tuning your translation to different audiences
- Take advantage of maximum data security
Translate consistently across media formats
Need to translate PDFs, images, and other file types? DeepL’s Language AI adapts visual content to match, so your translations stay consistent and correctly formatted no matter which file you're working with.
Read success stories from dozens of the 200,000 companies around the world that trust DeepL for their translation demands.
Ready to translate JSON files?
Start your free 30-day trial of DeepL Pro and translate JSON files, alongside Word, PDF, PPT, and more.
Need this built into your company’s pipeline, from localization workflows to CMS integrations? Contact our Sales team for powerful enterprise plans.
FAQs
Yes, via the DeepL API. A Pro or API plan is required to translate JSON files on the web translator.
No. Only string values are translated; keys, numbers, booleans, and null values are untouched. To exclude a specific string from translation, encode it as a non-string or remove it before upload. Learn more about translating JSON files with DeepL.
Yes. Like SRT, TXT, and XLIFF, JSON translations through the API aren't subject to the per-file character billing minimum that applies to Word, PowerPoint, Excel, and PDF files. See the API documentation.
JSON file size and character limits by plan
You need a DeepL Pro Advanced or DeepL API Free plan at minimum to translate JSON files. This table outlines the max file size and character count per file per plan.
Plan | Max file size | Max characters |
DeepL Account (Free) | Not available | Not available |
DeepL Pro Starter | Not available | Not available |
DeepL Pro Advanced | 1 MB | 1,000,000 |
DeepL Pro Ultimate | 1 MB | 1,000,000 |
DeepL Pro Individual | Not available | Not available |
DeepL Pro Team | 1 MB | 1,000,000 |
DeepL Pro Business | 1 MB | 1,000,000 |
DeepL API Free | 1 MB | 500,000 |
DeepL API Pro | 1 MB | 1,000,000 |
DeepL API Developer | 1 MB | 1,000,000 |
DeepL API Growth | 1 MB | 500,000 |