SRT vs Burned-In Captions: What to Deliver to a Client
Choose SRT files, burned-in captions or both with a practical client delivery checklist covering corrections, language versions and final upload checks.
Last updated October 7, 2026. Comparison guidance is current as of 2026.
Deliver an SRT file when the client needs a separate, selectable caption track. Deliver burned-in captions when the approved text must remain visible as part of the picture. Many jobs need both, plus a clean video master. Decide this before styling begins because these deliverables are not interchangeable.
Imagine a client asking for a captioned product interview for its website, YouTube channel and sales team. Sending one captioned MP4 may satisfy the sales presentation but leave the website publisher without the separate text file it expected. Sending only an SRT leaves anyone opening the video directly unsure how to display it.
Explain the objects in plain language
An SRT is a timed text file. It travels alongside a video and relies on the receiving player or platform to display it. Burned-in captions are pixels in the rendered video. A viewer cannot turn those pixels off through a caption control.
The distinction appears in W3C's discussion of open and closed captions and in Adobe's export choices. Neither format is automatically more professional. The correct choice depends on how the audience will watch and how the publisher will maintain the asset.
Avoid promising that an SRT carries your animated brand treatment. YouTube's format documentation explicitly separates basic SRT support from richer styling behavior. A file that contains the right words can still look different after upload.
Ask for the destination and the next editor
A useful delivery brief answers two questions: where will the video play, and who will make the next text correction? If the client will replace a surname next month, a separate caption file can avoid rerendering the picture. If the text is burned in, that correction requires a new video export from a suitable source project.
Also distinguish a client who wants editable wording from one who wants editable animation. An SRT can help with the first; it is not a replacement for the second. Agree on project handoff separately, including fonts and any necessary editing tools.
For a workflow based on Znippet captions, validate the exact delivery path on your project before offering a format in the quote. The Premiere plugin page describes the editing environment, but a product description is not a client delivery specification.
Build a small delivery matrix
| Destination need | Suggested package | Approval question |
|---|---|---|
| Selectable captions on a supported player | Clean master and reviewed SRT | Can the publisher upload and select the track? |
| Fixed social caption appearance | Burned-in video | Is the placement readable in the final feed? |
| Several translated versions | Clean master and separate language files | Is each language matched to the correct video? |
| Future animated text changes | Agreed editable project plus references | Can the receiving editor revise and export it? |
This is a planning matrix, not a guarantee of support by every platform. Test the actual destination. YouTube's upload guidance is a concrete example of a publisher workflow that accepts separate caption inputs.
Prevent duplicate captions
A common delivery failure is a video with burned-in captions plus a second, independently displayed caption track. Viewers may see two versions at different positions or with slightly different timing. Review the published result with captions enabled and disabled; do not assume the preview in your editor reveals this problem.
Label the files by purpose rather than calling everything final. For example, distinguish clean video, open-caption video, and English caption file. Keep the same video version identifier across the package so a publisher does not pair yesterday's subtitles with today's shorter edit.
Our subtitle and caption automation guide provides background on the production stage before delivery. The handoff itself should include one short note explaining which file goes where.
Approve the package as a viewer
Open the clean master with its caption file in the intended player. Then watch the burned-in version on a phone. Check the first and final spoken words, a long line, any speaker identification, and a meaningful sound cue. A correct filename is not evidence that the content is correct.
Before the next client job, send a sample package containing a short clean video, its captions, and a burned-in alternative. Ask the publisher to complete the real upload. That small rehearsal resolves format confusion before a full campaign depends on the answer.
Sources and further reading
Background links used to check product details, terminology, and practical context.
- Create captions in Premiere
Adobe
Caption segmentation and native creation controls
- Auto transcribe video using Speech to Text
Adobe
Language, audio source and speaker options
- Export caption tracks
Adobe
Caption delivery formats and export behavior
- Create Linked and Track Styles
Adobe
Reusable caption presentation and style handling
- Add subtitles and captions
YouTube Help
Destination caption upload and editing workflow
- Supported subtitle and closed caption files
YouTube Help
SRT encoding and destination format limitations
- Use automatic captioning
YouTube Help
Automatic caption limitations and human correction
- Captions and subtitles
W3C WAI
Caption accuracy, sound information and presentation
Keep comparing workflows
Turn the workflow from this guide into finished clips
Use Znippet to turn long-form videos into ready-to-post clips with captions, silence removal, social formats, and high-resolution exports.