General troubleshooting: Press F12 to open DevTools, check the Network tab and inspect the Response. Most errors can be located there.
This can happen for several reasons:
If only some content failed to translate, simply try clicking the "Translate" button again. When the translation cache is enabled, the system will skip already translated content, avoiding duplicate charges or requests.
Troubleshoot in this order:
Note: Most mainstream online 70B+ models are fine; issues are commonly due to inappropriate temperature.
The key is the “translation rate,” which is essentially the concurrency (how many requests are sent at once).
Want it faster? Increase the “translation rate” from 20 to 30/50 gradually; if you see 429 or empty results, step back a bit.
Tips:
Because DeepL's official service does not allow direct calls from a webpage, we use a "proxy channel" to send the requests for you.
This proxy interface is only used to transmit data and will not collect any of your information, so you can use it with confidence. If you have higher stability requirements, you can also set up this channel yourself.
No! Your API Key and other settings are only saved in your own browser. We do not upload or record any of your information.
The GTX Web interface puts significant pressure on the server, so it is not enabled by default.
If you are using this tool on your own computer, you can enable it manually. Please avoid using this interface in a network environment with a global proxy enabled, as it may cause translation anomalies.