Frequently asked questions
How do I translate an SRT file? +
Open the translator, drop your .srt file in, choose the target language, and press Translate. The translated file downloads with timestamps unchanged.
Can I translate a VTT (WebVTT) file? +
Yes. Both .srt and .vtt are supported, and WebVTT cue settings such as positioning are preserved.
Is there a file size or line limit? +
No. Because your file is never uploaded, full-length films and multi-hour lectures work fine.
Do I need an account? +
No account, no email, no payment. The tool is free and unlimited.
Will my formatting be preserved? +
Yes. Italic and bold tags, positioning codes and cue numbering are preserved. Only the spoken text is translated.
Which languages are supported? +
Over 20 including Spanish, French, German, Portuguese, Hindi, Japanese, Korean, Chinese, Arabic, Russian, Turkish, Vietnamese and Indonesian.
Why does it need Chrome or Edge? +
It uses an on-device translation model that ships inside the browser itself. Google Chrome 138+ provides one, and Microsoft Edge provides its own Microsoft-built model. Both work here. Other Chromium browsers such as Brave or Opera may expose the same API without shipping a model, so translation can fail there. Desktop only for now.
Why is the first translation slow? +
The first time you use a language pair, your browser downloads that language model once. Afterwards translation is fast and works offline.
Is it AI agent ready (WebMCP)? +
Yes. In browsers that support WebMCP (navigator.modelContext), the translator page exposes a translate_subtitles tool so an AI agent can set the languages and start a translation for you. It drives the same on-page controls, you still choose the file yourself, and nothing is uploaded.
Is machine translation good enough to publish? +
It is a strong first draft. For published work we recommend a quick human review, especially for idioms and names.