How to import SRT subtitles into Avid Media Composer

Avid Media Composer cannot import an SRT file directly. The SubCap effect — still the most dependable subtitle route in Media Composer — reads exactly two formats: Avid caption TXT (sometimes called Avid DS or SubCap format) and EBU STL. So getting SRT subtitles into Avid is a two-step job: convert the SRT into the caption TXT format SubCap understands, then import that file with Import Caption Data. This guide walks through both steps, the frame-rate trap between them, and the fixes for the usual import failures.

Just need the file? Drop your subtitles on the free SRT to Avid TXT converter — pick your timeline frame rate and every cue is rewritten into SubCap-ready caption TXT. Batches come back as one ZIP.

Why Media Composer won't take your SRT

SRT is the lingua franca of web subtitles — YouTube, Vimeo, Premiere Pro, and every media player read it — but it predates nothing in Avid's world. Media Composer's subtitle tooling grew out of broadcast captioning, where files are timecode-based and frame-accurate, so its importers speak SCC and MCC for closed captions and Avid caption TXT or EBU STL for subtitles via SubCap.

The mismatch is in the timing. An SRT cue is stamped in milliseconds (00:00:03,433); an Avid caption is stamped in timecode with a frame count in the last field (00:00:03:13). Converting between them means real frame math against your sequence's frame rate, which is why renaming the file or pasting the text never works.

The Avid caption TXT format

The file SubCap imports is plain text with two markers around the caption blocks. Each block is one caption: a start and end timecode on the first line, then one or more lines of caption text, separated from the next block by a blank line.

<begin subtitles>

00:00:01:00 00:00:03:12
Welcome back to the show.

00:00:03:13 00:00:06:00
Today we're talking about captions.

<end subtitles>

Three rules matter: timecodes are HH:MM:SS:FF (the last field is frames, not milliseconds), caption ranges must not overlap, and the file must be plain text — UTF-8 encoding for anything beyond basic Latin characters. Some tools also write an @-prefixed comment line above the markers; SubCap ignores comment lines, so files import with or without one.

Step by step: SRT into Media Composer

1. Convert the SRT with the SRT to Avid TXT converter. Choose the frame rate that matches your sequence — 23.976, 24, 25, 29.97, or 30 fps — or leave it on auto.
2. In Media Composer, create an empty video track above your picture (Timeline > New > Video Track) and make sure it has filler where the captions will live. If the effect won't land later, use Add Edit on the filler to give it a segment.
3. Open the Effect Palette (Tools > Effect Palette), find SubCap in the Generator category, and drag it onto the empty track segment.
4. Enter Effect Mode on the SubCap effect, expand the Caption Files group, and click Import Caption Data. Choose your converted .txt.
5. Play the sequence. Captions should pop on and off on the right frames; font, size, position, and background are set globally in the effect parameters.

Get the frame rate right

Because Avid caption timecodes count frames, a file converted at the wrong rate imports cleanly and then lands captions on the wrong frames — a 25 fps file dropped into a 29.97 sequence drifts further out of sync the longer the show runs. Match the converter's frame rate to the sequence you're captioning, not the source footage. If dialogue starts drifting late in the timeline, frame rate is almost always the culprit; reconvert at the right rate rather than nudging captions by hand.

Troubleshooting the import

• Import does nothing, or only some captions appear. Check for overlapping timecode ranges — SubCap skips or mangles blocks whose ranges collide — and confirm both <begin subtitles> and <end subtitles> markers survived any hand-editing.
• Accented or non-Latin characters come in as garbage. The file needs to be UTF-8. If you edited the TXT in a word processor, re-save it as plain UTF-8 text and re-import.
• The effect won't apply to the track. SubCap needs a filler segment to sit on. Add Edit at the start and end of the region on the empty track, then drop the effect on the segment between the edits.
• Captions are early or late by a consistent ratio. Frame-rate mismatch — reconvert the SRT at the sequence's rate.

Going the other way — pulling captions out of a SubCap effect for YouTube or a web player — is the mirror of this workflow: export the caption data and convert it to SRT. And if the project is moving to Premiere instead, Premiere imports SRT as captions natively; it's only the transcript panel that needs JSON.

For broadcast closed-caption deliverables (line-21/608/708), note that SubCap subtitles are open captions rendered by the effect. Media Composer's closed-captioning tools work from SCC/MCC files instead — see Avid's Media Composer documentation for that pipeline. A deeper survey of the caption options in Avid is in 3Play Media's Media Composer guide.

FAQ

Can Avid Media Composer import an SRT file directly? No. SubCap reads Avid caption TXT and EBU STL only, and Media Composer's closed-caption tools read SCC/MCC. An SRT has to be converted to caption TXT first — that's the entire reason this two-step workflow exists.

What is the SubCap effect? A generator effect that renders subtitles from an imported caption file. You drag it from the Effect Palette onto an empty video track, import the caption data in Effect Mode, and it draws every caption at the right timecode with globally controlled styling.

What frame rate should I pick in the converter? The frame rate of the sequence you're dropping the captions into — not the frame rate of the original video the SRT was made for. A mismatch imports fine but drifts out of sync over the run of the show.

Do speaker labels survive the conversion? Yes. If an SRT cue carries a speaker prefix, the converter keeps it as part of the caption text, so SARAH: We're live renders exactly that way in the SubCap effect.

Should I use caption TXT or EBU STL? TXT. Both import, but STL is a binary broadcast format with its own frame-rate and character-set constraints, while the TXT is human-readable, easy to spot-check, and what most Avid subtitle workflows standardize on.

My captions import but accented characters are wrong. What happened? Encoding. SubCap expects plain UTF-8 text; a file saved as Windows-1252 or from a word processor imports with mangled characters. Re-save the TXT as UTF-8 and re-import.