On most indie productions, subtitles come last. They follow the grade and the mix, and they usually get done a few days before a submission deadline. That’s when the expensive mistakes happen. Someone burns English subtitles into the only finished master. Nobody proofreads, so the programmer’s first impression includes a typo in the opening scene. One subtitle file goes to every territory, whatever they actually asked for.
You don’t need a big budget to avoid any of this. You need a bit of planning. Here’s what to deliver, what you can do for free or nearly free, and where it’s worth paying a professional.
1. Know the deliverables before you start
Festivals and sales agents want different things, so find out who needs what before you touch a subtitle. A festival’s selection team usually wants a screener they can watch straight away. That might have the subtitles already visible, or come with a separate file. If you’re selected, the screening copy may need subtitles in a cinema-ready format. A sales agent is thinking about many territories at once. They’ll typically want a clean, textless master plus separate subtitle files they can replace or translate.
Requirements differ between festivals and can change from year to year, so don’t guess. Read each festival’s technical specifications. Note the format, frame rate, language and delivery method they ask for, and keep those notes in one place. If anything is unclear, email the festival’s technical team. They would rather answer a question now than reject a file later.
2. Keep subtitles separate from the picture
The most useful habit is to keep your picture clean and your subtitles in their own file. With a clean master and a subtitle file, you can make a burned-in screener whenever you need one, switch languages, fix a typo in minutes, and give a sales agent what they expect. A burned-in export gives you one version for one audience, and every correction means another render.
For screeners, online platforms and most review links, SRT is the common format. It’s a plain-text file of numbered lines with timecodes, and almost everything can read it. Cinema DCPs use their own subtitle formats, in Interop and SMPTE versions. Your DCP maker or mastering facility can build those from your timed file. Keep one master SRT as your source and create the other formats from it.
What if the only copy of your subtitles is burned into an old export? You can still recover them. A desktop app such as GeekLink can OCR burned-in subtitles back into an editable file, which beats retyping them.
3. Get a transcript cheaply
Typing out dialogue by hand is slow, and free speech recognition can do the first draft for you. Whisper is an open-source speech recognition model that runs on your own computer. That matters for unreleased work, because your footage never has to be uploaded to anyone else’s server. Several free subtitle editors can run Whisper for you and produce a timed draft.
Treat that draft as a starting point. Speech recognition can get names, overlapping speech, accents and mumbled lines wrong, and it hasn’t read your script. A person, ideally someone who knows the film, should check every line against the picture. Check it against the script or dialogue list as well, if you have one.
4. Spotting and readability
“Spotting” means deciding when each subtitle appears and disappears. A few principles go a long way:
– Leave each subtitle up long enough to read. If a line flashes past, viewers either miss it or stop watching the picture. Many style guides set a maximum reading speed in characters per second. Pick one and stick to it.
– Use two lines at most, and keep each line reasonably short.
– Break lines at natural phrases. Split after a clause, not between “the” and its noun or in the middle of a name.
– Respect the cuts. A subtitle that hangs over a shot change is distracting. End it just before the cut, or start the next one just after.
You don’t have to check all of this by eye. Subtitle Edit flags lines that are too fast, too long or overlapping, and it can fix many of them in one go. Aegisub is excellent for precise timing and can snap subtitles to shot changes using the video’s keyframes. Both are free.
5. Translation: where not to save money
Machine translation is useful early on. A quick machine draft lets a co-producer or editor follow a rough cut in a language they don’t speak, and it costs next to nothing.
The version a programmer or buyer watches is different, though. It’s your film’s first impression, so pay a native-speaking subtitler. At the very least, have a native speaker check the machine draft against the picture. Cheap translation shows in the places where your film is most alive: jokes, slang, swearing, how characters address each other, cultural references and names. A good subtitler also knows how to shorten dialogue to fit the reading time, which a literal translation rarely does. If money is tight, spend it here before anything else on this list.
6. A final QC pass on the real screener
Before anything goes out, watch the exported file from start to finish. Don’t watch your editing timeline or a different render. Use the kind of screen the programmer is likely to use, whether that’s a laptop, a TV playing a streaming link, or a projector if you can borrow one.
Look out for:
– subtitles that are missing or out of sync
– characters that show up as boxes or question marks, which often means accented letters weren’t encoded properly
– text that’s hard to read over bright shots
– subtitles that clash with on-screen text or credits
It’s tedious, but it’s the cheapest insurance you’ll ever buy.
7. A one-page subtitle checklist
Print this and keep it with your delivery documents:
- Each festival’s and sales agent’s tech specs read; format, frame rate, language and delivery method noted
- Clean, textless master archived and backed up
- Master subtitle file (SRT) kept separately, with version and date in the filename
- Transcript checked line by line by a person
- Reading speed, line length and line breaks checked; two lines maximum
- No subtitles hanging across cuts
- Translation done or reviewed by a native speaker
- Names, jokes and slang checked by someone who knows the film
- Separate files for each language and each destination, not one file for everyone
- DCP subtitles made by your DCP maker and checked on cinema-style playback if possible
- Final screener watched end to end on a realistic screen
- Fonts, special characters and encoding display correctly
Flora is the founder of GeekLink, a Mac and Windows app for extracting, transcribing, translating and editing subtitles (OCR for hardcoded subtitles, local Whisper transcription, AI translation, a bilingual editor, SRT/ASS export; free plan available). She writes about practical, low-budget ways to get independent films ready for festivals and international audiences.


