The Complete Guide to Translating Anime Subtitles (SRT & ASS)

Translation craft · 6 min read · Updated 21 October 2026

A start-to-finish workflow for translating anime subtitles in SRT and ASS: clean sources, safe timing and styling, consistent names, and a proper review.

Translating anime subtitles looks simple from the outside: take the English (or Japanese, or Chinese) lines, translate them, save the file. Anyone who has tried it on a full episode knows it isn't. A 24-minute episode has three to four hundred lines, the timing has to survive untouched, the signs and songs in an ASS file carry styling that breaks easily, and the same character has to be called the same thing in episode 1 and episode 12.

This guide walks through a workflow that holds up across a whole season, whether you translate by hand, with AI, or with a mix of both.

Step 1: Start from the best source you can get

Translation quality is capped by the source file. Before you translate anything, check three things.

Is the timing right for your video? Play a few scenes with the subtitles loaded - one near the start, one in the middle, one near the end. If lines appear early or late, fix the timing first. Translating a mistimed file just gives you a mistimed translation. Our guide on fixing subtitle timing and sync drift covers how.

Which format is it? Most anime subtitles come as SRT (plain, timed text) or ASS (styled text with positions, fonts and effects). Fan releases are usually ASS; streaming rips are often SRT or VTT. If you're not sure which you need, read SRT vs ASS vs VTT.

Is the text clean? Look for leftover OCR errors ("l" instead of "I", broken words), duplicated lines and lines that are really two speakers merged together. Five minutes of cleanup here saves an hour of confusion later.

Step 2: Know what must not change

A subtitle file has two kinds of information: the words, and everything else. "Everything else" is the part beginners break.

• Timestamps. Every line has a start and end time. They must come back exactly as they went in - same values, same number of lines, same order.
• Line count. If line 214 in the original becomes line 213 in the translation because two short lines were merged, every line after it is now attached to the wrong moment.
• Inline tags. SRT files may carry <i> for italics; ASS files carry override tags in braces such as {\an8} (top of the screen), {\pos(640,50)} (exact position) or {\i1} (italics). These belong to the line, not the words, and should survive translation.
• Signs, songs and drawings. In ASS releases, typesetters place translated signs over the video, animate karaoke for the opening and closing songs, and sometimes draw shapes with vector commands. These lines are delicate - more on them in translating ASS subtitles without breaking styles.

If you translate by pasting text into a general chat assistant, these are exactly the things that go wrong: lines get merged or split, tags get "cleaned up", and long files get cut short. A subtitle-aware tool sends only the dialogue text for translation and rebuilds the file around it, which is how SubFly works: every cue keeps its original start and end time, and each batch has to come back with the same number of lines or it's retried.

Step 3: Build a glossary before you start

Anime is full of words that must be translated the same way every time: character names, places, techniques, organisations, ranks. Decide on them up front:

• Names - romanisation (Ryuu, Ryu or Ryū?), and whether family names come first.
• Honorifics - keep -san, -kun, -chan, -senpai, or adapt them? Pick one approach for the whole show.
• Terms of art - a "Jutsu" stays a Jutsu in most fan translations; a cultivation novel's "Qi" or "Sect" usually stays too.
• Recurring phrases - catchphrases and attack names that fans will recognise.

Put these in a glossary (SubFly calls it the word list) so every episode uses the same choices automatically. Our guide to building a subtitle glossary goes into detail.

Step 4: Choose a tone and stick to it

Anime dialogue ranges from formal court speech to the rough slang of a delinquent. A good translation keeps those differences instead of flattening every character into the same neutral voice. Before translating, decide:

• How casual is the show overall?
• Which characters speak formally, and which don't?
• Will you keep cultural references, explain them, or adapt them?

Write those decisions down as a short style note. In SubFly, this is what a style preset or a custom prompt is for - the instructions travel with every batch, so episode 9 sounds like episode 2. See the fansub style guide for common choices.

Step 5: Translate in context, not line by line

The single biggest quality jump in subtitle translation comes from context. A line like "Leave it to me" can be heroic, sarcastic or reluctant depending on the scene. Translating each line in isolation loses that.

When you translate - by hand or with AI - work in scenes: read a block of lines together, then translate them together. Modern AI models are good at this when they're given a batch of consecutive lines with instructions, rather than one line at a time. Speaker information helps too: knowing that a line is spoken by a woman, or by a child, changes word choice in many languages.

Step 6: Keep lines readable

Subtitles are read in a few seconds while someone is also watching the picture. A perfect translation that's too long to read is a bad subtitle. As a rule of thumb, keep lines to about 42 characters, use no more than two lines per subtitle, and aim for a reading speed most viewers can manage. If a translated line is much longer than the original, shorten it - meaning first, word-for-word second. Our guide on subtitle readability has the numbers.

Step 7: Review against the video

Never publish a translation you haven't watched. A review pass catches what no tool can:

• jokes that don't land, or puns that need a different joke;
• a character's name misspelled in one episode;
• a line whose meaning depends on what's on screen;
• typos and missing punctuation.

Watch at normal speed with the translated subtitles loaded. Note problems by timestamp, then fix them in the file. SubFly's side-by-side review shows the original and translated line together, with find and replace across a whole file, so these fixes are quick.

Step 8: Export in the right format

Export in the format your viewers' players handle best. ASS keeps all the styling and works in mpv, VLC and most dedicated players; SRT is the safest choice for TVs, phones and upload sites; VTT is the format for web players and HTML5 video. If you started from ASS, export ASS - converting styled subtitles to SRT throws away the positions and effects.

A checklist for every episode

1. Timing checked against the video.
2. Source text cleaned.
3. Glossary and style note up to date.
4. Translated in scene-sized batches with context.
5. Line length and reading speed checked.
6. Watched in full with the translation.
7. Exported in the right format.

Follow it every time and a season-long project stays consistent from the first episode to the last. If you'd like the mechanical parts - timing, tags, batching and consistency - handled for you, try SubFly free and spend your time on the part that needs a person: making the translation good.