Troubleshooting

Each feature page has its own troubleshooting section. This page is the index: find the symptom, follow the link.

Nothing happens at all

Part of the page is not translated

Read Frog skips text on purpose more often than people expect.

• Navigation, headers and footers stay in the original — Translation range is set to Main Content. Change it on Page Translation.
• Short lines stay in the original — the small-paragraph filter in Translation Control has a minimum length.
• Some paragraphs stay in the original on a mixed-language page — language skipping decided they were already in the target language. Same page.
• Text inside a widget, canvas or unusual element — the content detector did not see it as text. A per-site fix belongs in Site Rules.
• Nothing new translates as you scroll — pre-translation distance, in Request Control.

The translation itself is wrong

• A name or term keeps changing between paragraphs — give it a fixed translation in the Glossary. Note that a glossary only reaches LLM providers.
• Correct but stilted — try the Polished rewrite prompt, or write your own; see Custom Prompts.
• Pronouns and references are wrong — turn on AI Smart Context on Page Translation.
• The reply contains instructions, labels or %% marks instead of a translation — the prompt lost a placeholder or contradicts the batch rules. How a Request Is Assembled explains what the model is being asked for.
• A paragraph came back empty — the model decided it was already in the target language, and an empty translation renders nothing. See How a Request Is Assembled, under "Resolve 'nothing to translate'".

It is slow, or it stops partway

• Slow, or requests failing in bursts — lower the rate and burst in Request Control. Free provider tiers are strict.
• Long pages stop translating partway — same page: the queue gave up after retries. Lower the batch size.
• Every translation is slow on a local model — raise the batch size instead; local models pay per request, not per token.
• Something changed after you edited a prompt — editing a prompt discards cached translations, so the next read re-requests everything.

Layout looks broken

• Translations overlap or push the page around — try a different preset style, or write your own; see Translation Style.
• Only on one site — Site Rules can override selectors and thresholds for that site alone.
• Subtitles sit in the wrong place or overlap the player — Subtitle Style.

Subtitles

• No translate button in the player — the video has no captions YouTube exposes, or subtitles are off in Video Subtitles.
• Lines are cut mid-sentence — turn on AI smart segmentation in AI Segmentation and Subtitles Quota.
• Lines drift out of sync after turning that on — AI segmentation sets its own timing; turn it off if drift bothers you more than the cutting did.

Account, saving and review

• The popup still says Guest after signing in on the website — reload the page you are on; the extension reads the session when a tab loads.
• No way to save a result to a notebase — the Custom AI Action has no Notebase connection, or its provider does not support structured output. See Saving from the Extension.
• A Custom AI Action returns nothing or malformed fields — the model does not support structured output well. Try another, or disable reasoning if the provider offers that control.
• An assistant cannot connect over MCP — MCP requires the Ultra plan; see Connecting.

Nothing here matches

Export your configuration without API keys from Configuration, Sync & Backups and attach it to a GitHub issue, or ask in Discord. The export says which providers, prompts and rules are in play, which is usually the whole answer.