How Translate quota and re-translation work
Translate spends daily seconds from the on-screen cue length (clamped), not characters. Cache hits for the same account, text, languages, and engine are free. Any OCR character change requests a new translation.
Prerequisites
You are signed in with Translate mode available.
Steps
What is billed
- Each successful translate that is not served from your account cache adds seconds based on how long that subtitle cue is on screen.
- Cue length is rounded and clamped (at least 1 second, at most 120 seconds per request).
What is free
- Repeating the exact same OCR string with the same languages and engine for your account hits cache — no new ledger burn.
- Looking at Settings → Translation does not spend quota.
What forces a new request
- Any change to the OCR text, source language, target language, or engine can miss cache and spend seconds again.
- Hosted Microsoft is included in plan seconds. DeepL / Google still use those same Translate-mode seconds, and your provider bills their own usage separately.
Updated Nov 4, 2026