Burned-In Subtitles vs SRT Files: What Is the Difference?

Both put words on screen, but they solve different problems. One becomes part of the video; the other stays editable beside it.

The short version

Burned-in subtitles become part of the image. SRT files stay beside the video as a separate text file. Burned-in captions usually travel with the video and keep their intended look, but they cannot be turned off or edited after export, and cropping or platform overlays can still affect what the viewer sees. SRT captions can be corrected, translated, and restyled later, but only on platforms and players that support them.

Most creators need both, for different destinations.

What burned-in subtitles are

Also called open captions or hardsubs. The renderer draws the text into each frame before encoding. The viewer’s player has no idea captions exist; it is just video. That is why a burned-in MP4 usually keeps its look across apps that play the file, provided the app does not crop, recompress, or overlay the frame in a way that hides the text.

• Appears in most apps that accept the video file; playback, cropping, and recompression can still change the result.
• Keeps your type, color, outline, and placement unless the app alters the frame.
• Cannot be turned off; a second language means a second render.
• Usually the right choice for social clips watched with sound off.

If the destination does not accept subtitle files, burned-in is usually the reliable option. The accessibility trade-off is real: the text is always visible, but the viewer cannot toggle it or change its size.

What an SRT file is

SRT is a plain-text file of timed cues: a number, a start and end timestamp, and the text. It contains no video and no design. The player decides how the captions look.

• Editable with any text editor.
• Easy to translate or correct without re-rendering video.
• Small and archival.
• Appearance depends on the platform.
• Unsupported players simply show nothing.

YouTube, many desktop editors, and common media players accept SRT. Social apps are more limited, and their support can change. Check the current help documentation before you build a workflow around an upload feature.

Side by side

When burned-in is the right call

Choose burned-in when the destination does not support subtitle files, when the look is part of the edit, or when the video will likely be watched with sound off. Short-form social is the obvious case. So is a client preview or a file that will be forwarded beyond the original platform.

The trade-off is permanence. If a name is wrong, you re-export. If you need Hindi and English, you export twice.

When an SRT is the right call

Choose SRT when the video will live on YouTube, when captions need to be corrected or translated later, or when the same video will be distributed through several systems. SRT is also a common format for editors and transcription tools to exchange.

The trade-off is dependence on the player. A beautifully timed SRT does nothing on a platform that does not read it.

Can you use both?

Yes, and for anything important you probably should. In Capsly, one project can export a rendered MP4 with the captions burned in, plus SRT and VTT sidecars. Upload the MP4 where the design matters; keep the SRT for YouTube, your archive, or the next translation.

If you are starting from a raw clip, the add subtitles to a video workflow covers the upload-to-export path. The format decision above still applies: burn in for control, keep an SRT for editing.

Common mistakes

• Uploading an SRT to Reels or TikTok and expecting captions. Those apps generally do not offer a standard sidecar upload; use burned-in or in-app captions, and verify current support.
• Assuming an SRT carries your font or color. It does not.
• Saving the file in a non-UTF-8 encoding and losing accents.
• Letting cues overlap or leaving blank lines inside a cue.
• Using frame-rate-dependent tools and ending up with drift.
• Forgetting that a corrected SRT does nothing for an already-exported MP4.

The SRT guide covers the file format and the usual breakages in detail.

The practical rule

Ask one question: does the destination control how captions are displayed, or do I? If you control the look, as with social video, a client cut, or a file that travels, burn them in. If the destination controls the look, as with YouTube, a player, or a translation workflow, ship an SRT. When in doubt, export both. It costs you one extra file and saves a re-export later.