AI Glot websiteOpen AI Glot
File formatsSubtitles
File formats

Translate subtitle files

Translate SRT, WebVTT, SBV, ASS, SSA, TTML, DFXP and LRC files up to 4 MB. Timecodes, cue order and styling stay untouched. Includes a per-format table and example instructions.

Subtitle and lyric files keep their timing and styling while the spoken text is translated. AI Glot supports SubRip, WebVTT, YouTube SBV, Advanced SubStation, TTML and DFXP, and LRC synchronized lyrics. One cue goes in and one cue comes out: nothing is merged, split or dropped, so the file plays back exactly as before.

The formats

FormatExtensionsCeilingWhat stays as it was
SubRip.srt4 MBCue numbers and timecodes
WebVTT.vtt4 MBTimestamps, cue settings, NOTE and STYLE blocks, <v Speaker> labels
YouTube.sbv4 MBTimestamps and cue order
Advanced SubStation.ass, .ssa4 MBStyles, override codes such as {\i1} and {\pos(10,20)}, timings, layers, \N breaks
TTML.ttml, .dfxp8 MBTimings, regions and style references. xml:lang is updated
LRC lyrics.lrc4 MB[mm:ss.xx] time tags, [ar:] and [ti:] tags, empty timed lines, word timings

In ASS, only the text of Dialogue lines is translated. Styles, script info and editor comments are copied across.

What you can ask

Readable lines

For SRT or WebVTT: asks for short lines. It is a request, not a check, so skim the result.

Translate the subtitles into French. Keep each line under 42 characters and use at most two lines per cue.

Keep speaker labels

For WebVTT: protects the labels that say who is talking.

Translate into German. Keep the speaker labels and the italics, and leave brand names in English.

A fansub release

For ASS: keeps the styling work and the glossary of names.

Translate the dialogue into Spanish. Keep all override codes in curly braces, and keep character names unchanged.

Song lyrics

For LRC: keeps the time tags and asks for singable lines.

Translate the lyrics into Italian. Keep every time tag and the artist and title tags, and keep each line short enough to sing.

Only the changed cues

For SRT: returns just the cues that were written.

Translate the cues into Portuguese and return only the cues you changed.

Good to know

  • One target language per upload for every subtitle format, LRC included. If you ask for two, the plan translates one and says so. Run the file once per language: your glossary carries over, so names and terms stay identical across tracks.
  • A series at once. Put the files in a ZIP to translate a whole season or an album as one job.
  • Timing never changes. Timecodes are copied byte for byte. If a translation runs longer, ask for short lines and review the result before delivering. A line-length limit is a request that guides the wording: the plan may list it as not enforced, so skim the result.
  • Output filter. Available for SRT only. The other formats return the whole file.
  • Enhanced LRC. Word timings travel with the translated line. Word order differs between languages, so check the result in your player.
  • Not supported. .scc and .stl are refused: export the captions to SRT or WebVTT first.
  • YouTube. Export the .sbv from YouTube Studio, translate it, then upload the result as a new language.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search AI Glot Docs documentation and read it in full, instead of answering from memory.

https://ai-glot.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://ai-glot.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.