This tool is suitable for multilingual translation tasks for files such as subtitles and text. It supports various scenarios including batch processing, cache optimization, and multi-language export to help you complete localization work efficiently.
You can translate the same file into multiple languages simultaneously, which is ideal for multilingual subtitles or internationalization projects:
To avoid redundant requests to the translation API, this tool introduces a local caching mechanism:
Source Text_Target Language_Source Language_Translation API_Model Settings
.If you do not wish to use the cache, you can disable it in the settings by unchecking "Use Translation Cache," or you can manually clear it by clicking the "Clear Translation Cache" button in the API settings.
The tool automatically switches translation modes based on your upload action, requiring no manual selection:
JSON Translate currently only supports single-file mode.
Supports one-click export/import of current settings, making it easy to move between devices or migrate deployments:
To balance context with API limitations, you can customize the following key parameters:
For non-AI translation APIs, the tool automatically splits text into chunks before translation to handle long documents or subtitles. The Chunk Translation Size refers to the maximum character count for each chunk. Below are the maximum character limits for common APIs:
Translation Service | Max Characters per Request |
---|---|
DeepL API | 128,000 characters |
DeepLX Free | 1,000 characters |
Azure Translate | 10,000 characters |
Google Translate (Web) | 5,000 characters |
Google Cloud API | 30,000 characters |
⚠️ Note: The web version of Google Translate can break line breaks, so chunked translation is not used for it.
This controls the interval between requests for chunked translations, helping to avoid frequent request failures:
Setting the request frequency too high can trigger rate limiting or return null values (e.g., an HTTP 429 error):