Troubleshooting
Page translation does nothing
Refresh the page after installation or an update. Check that FluentRead is enabled and the target language is correct. Browser settings and extension store pages cannot be translated; try a regular article.
Check the connection in service settings. If the free service is busy, retry later or choose another provider.
Only part of the page is translated
The default mode translates as you read. Scroll down, or change the full-page range to process everything at once. For missing menus or unusual layouts, see Website reading area. Use image or area translation for text drawn in pictures.
Why does Japanese appear in a Chinese translation?
A provider can occasionally return a paragraph in the wrong language. When a result is clearly a full Japanese paragraph, Free Translation tries another enabled provider. A provider selected directly gets one retry. If it still returns the wrong language, FluentRead reports a failure instead of displaying or caching that result. Short Japanese names, terms, and quotations within Chinese text remain allowed.
If mixed languages still appear, check the target language, restore the page, and retry. Include the selected provider, extension version, and a redacted screenshot when reporting it.
How do I restore the original?
Open the extension menu and choose restore original. Restore before retrying with a different language, service, or display setting.
Selection works, but whole-page translation fails
The page may not be recognized correctly, or too many requests may be reaching a busy service. Try one paragraph, then check page recognition and the connection.
Can webmail messages be translated?
FluentRead has a dedicated message-frame path for legacy QQ Mail and the JS6 reading pages of NetEase 163, 126, and yeah free mail. Open an individual message and try page or selection translation; refresh the mailbox if needed. Compose editors are excluded. Mailbox versions can use different layouts. If it still fails, report the mailbox domain, the page path with sid and other parameters removed, the browser version, and a redacted screenshot. Do not share a full message or login details.
Why is there no AI explanation?
Regular selection translation gives a translation. The reading card must be enabled separately with a configured AI service and model. Choose an action after selecting text to start it.
Image translation is still preparing
First use needs recognition language packs. Follow the download prompt and check that the source language matches. Use a clear image or a smaller area if recognition fails.
No subtitles appeared
Check that video translation is enabled and the video has subtitles. X AI transcription requires a downloaded model, and some videos cannot be read. See Video subtitles.
Where does my API key go?
Enter it in the corresponding service’s connection settings. Check address, key, model, and allowance. Web chat memberships may not include API use. For Ollama, confirm the local server is running and the model is downloaded. See Translation services.
Duplicate translations or broken layout
Restore the original. Check whether another extension or the browser’s own translation is active, then try with one translator. If the issue remains, record the URL and steps.
Why do translations disappear when Font Rendering is enabled?
Some older FluentRead versions mistake Font Rendering's bold-correction markers for rewritten translations and remove the translation after repeated repair attempts. The compatibility fix preserves these font markers while still checking actual content and structure changes. Update to a version containing the fix and reload the page. Until your store version includes it, temporarily disable bold correction in the font script.
Can I import an older backup?
Older configuration JSON files and full backups are supported through backup and restore in settings. Fields introduced after a backup was created receive compatible defaults, and existing API keys are migrated.
If you see an invalid exact credential snapshot error, keep the original file. Some versions incorrectly required a newly introduced credential field in older backups; this compatibility issue has been fixed. If it persists after updating, report your extension version and the error message without sharing the full backup.
Still need help?
Open a GitHub issue with browser and extension versions, a public URL, reproduction steps, and a redacted screenshot. Do not include keys, cookies, account details, or private text.