This page is designed for translating i18n files using our open API. If you need to translate i18n JSON as text content, please refer to the JSON Translation page.

I18N File Translation

Source Files:

Accepts ZIP (compressed language-specific JSON files) or JSON files. Maximum size is 10 MB.

Source Language:

en-US (English, United States)

The code of the source language. Example: en, en-US, fil, zh-Hans-CN.

Translate only new strings:

Indicates whether to translate only new strings or rewrite existing strings in the target files.

Target Languages:

de (German), zh-Hans-CN (Chinese, Simplified Chinese, China)

How to translate i18n files

Translating i18n files is a straightforward process provided by our service. Follow these steps to translate your internationalization files and ensure consistency across your projects.

Upload Files: Use the "Source Files" section to upload your i18n JSON or ZIP files. If the file name contains a language code, it will be automatically used as the source language.
Set Source and Target Languages: Specify the source language (e.g., en-US). You can add multiple target languages (e.g., fr-FR, de-DE, etc.), each with customizable translation options such as contractions, shortening, terminology, and associated files. To translate only new or untranslated strings, select the corresponding target files for each language. For example, to translate only new strings into French, select the target files under the fr tab.
Start Translation: Click the "Translate" button to begin. Our service carefully manages files to preserve string order, preventing unnecessary changes. Progress is displayed in real-time.
Download Translated Files: After the translation is complete, click the "Download Translated Files" button to retrieve your translated content. The downloaded file is a ZIP archive named after the job ID (for example: 0196e881-fb54-7150-a292-5b1e8f70a8ae.zip). The archive contains translated files for each target language, organized into separate folders by language code.

Why our i18n translation service

AI-powered contextual translation: Our AI intelligently interprets i18n format placeholders, and adapts translations to cultural norms based on the language, script, and region are specified in the language code.
i18next files support: Our service ensures seamless handling of i18next format content in your JSON files. It accurately manages plural forms, preserves HTML tags, retains line breaks, and keeps the structure of your i18n JSON file.
Locale-specific adjustments: Numbers and dates in text are automatically converted to match the target locale format.
Error handling: We detect AI errors and retranslate if necessary, ensuring high-quality results.
Cost-effective: Our service is more affordable than other machine translation solutions. New users receive a 3-day free trial. See pricing.
Optimized for large files: Our system efficiently processes large i18n files by dividing them into manageable chunks, ensuring each segment fits within the AI's output window. This approach maintains translation consistency by leveraging predefined terminology and context, even for large files.

Internationalization vs. Localization (i18n vs l10n)

Internationalization (i18n): This is the process of designing and preparing your application to support multiple languages and regions without requiring engineering changes. It involves abstracting text, dates, numbers, and other locale-specific elements from the codebase.

Localization (l10n): This is the process of adapting your application to a specific language and region by translating text, formatting dates and numbers, and applying cultural nuances.

While i18n lays the groundwork for supporting multiple locales, l10n customizes the experience for a specific locale.

Our service focuses on localizing your i18n files using AI-powered translation, ensuring accuracy and efficiency while managing files.