Subtitles: Embed, Burn In, or Separate File? A Platform Comparison

You're about to add subtitles to your video and you have three options: embed them inside the video file, burn them onto the picture, or deliver them as a separate SRT/VTT file. All three count as "adding subtitles," but in terms of platform support, accessibility and SEO they produce completely different outcomes.

The three methods in brief

Embedding (soft subtitle): the subtitle sits inside the video file as a separate track. The video picture is untouched.

Burning (hardsub): the subtitle is drawn onto every frame and becomes pixels of the image.

Separate file: the subtitle sits as an SRT or VTT file independent of the video. The player loads both together.

Comparison table

| Criterion | Embed | Burn in | Separate file | |---|---|---|---| | Can be toggled on/off | Yes | No | Yes | | Multiple languages | Yes | No | Yes | | Impact on picture quality | None | Re-encoding loss | None | | Visible in every player | No | Yes | No | | Works on social media | No | Yes | No | | YouTube support | Partial | Yes | Best | | HTML5 video | No | Yes | Yes (VTT) | | Read by search engines | No | No | Yes | | Screen reader access | Partial | No | Yes | | User style settings | Partial | No | Yes | | Single-file portability | Yes | Yes | No (two files) | | Reversible | Yes | No | Yes |

Scenario 1: Instagram, TikTok, Reels

Short video content watched on mute.

Winner: burning in, there is no other option.

These platforms re-encode your uploaded video into their own formats, and they drop embedded subtitle tracks in the process. There's no option to upload a separate file either.

Subtitles are critical on these platforms: most of the content is watched with the sound off. Without subtitles a video is just a silent picture for the majority of viewers.

When burning in, watch out for two platform-specific points:

Position. Platforms place their own interface elements at the bottom of the video — like buttons, username, description text. If you leave subtitles in the standard bottom position they can end up hidden behind those elements. Nudging them upward (about 20-25% of the screen height) is safe.

Size. These videos are watched on a phone. A font size that looks fine on a computer screen ends up tiny on a phone. Be generous.

Scenario 2: YouTube

Winner: a separate subtitle file.

YouTube accepts SRT and VTT files directly, and this method has three big advantages:

SEO. YouTube indexes subtitle text. Your video becomes searchable through the words spoken in the subtitles. Burned-in subtitles are part of the picture, so machines can't read them — you lose that advantage entirely.

Automatic translation. YouTube can automatically translate the subtitles you upload into other languages. That's impossible with burned-in subtitles.

User control. The viewer can turn subtitles on and off and adjust their size and contrast to their own needs.

YouTube also has automatic subtitle generation, but its accuracy varies by language — it especially stumbles on technical terms, proper nouns and noisy recordings. Uploading your own subtitles always gives a better result.

Scenario 3: Video on your own website

Winner: a separate VTT file.

The HTML5 video element supports VTT files through the <track> element:

<video controls>
  <source src="video.mp4" type="video/mp4">
  <track src="tr.vtt" kind="subtitles" srclang="tr" label="Türkçe" default>
  <track src="en.vtt" kind="subtitles" srclang="en" label="English">
</video>

The advantages:

• Multiple languages delivered with a single video.
• Accessibility: screen readers and accessibility tools reach the text.
• SEO: search engines can read the VTT file.
• Quality: the video is never re-encoded.
• Bandwidth: subtitle files are a few kilobytes.

The kind attribute makes an important distinction: subtitles is for translation, while captions also includes sound effects for deaf and hard-of-hearing viewers ("[door slams]", "[music playing]").

Scenario 4: A personal film archive

You're organizing your own collection.

Winner: embedding (in an MKV container).

MKV carries an unlimited number of subtitle tracks perfectly. Original-language subtitles, translated subtitles, extended subtitles for the hard of hearing — all in one file.

Its advantages:

• One file, no worries about a missing subtitle file.
• The viewer picks whichever track they want.
• The video is never re-encoded.
• Different formats (SRT, ASS, even Blu-ray image subtitles) are supported.

The downside: some televisions and simple media players can't read subtitles inside an MKV. If you watch your archive directly on a TV, test it.

Alternatively, keeping a separate SRT file works too — most TVs automatically find an SRT file that shares the video's name (like movie.mp4 and movie.srt).

Scenario 5: A corporate training video

You're going to upload it to an internal learning platform.

Winner: check the platform's support.

Learning management systems (LMS) vary wildly in subtitle support:

• Some support VTT upload — the best case.
• Some only accept video — burning in is required.
• Some read embedded tracks — rare.

Check the platform's documentation before uploading, or try it with a short test video.

If you have accessibility obligations (which applies to public institutions and many large companies), text-based subtitles should be preferred. Burned-in subtitles don't count as accessible for employees using a screen reader.

Scenario 6: Sending via WhatsApp or email

You're sending a video directly to someone.

Winner: burning in.

Sending a separate file requires the recipient to download both files, put them in the same folder and use a player that supports subtitles. Most people won't or can't do that.

Embedded subtitles aren't reliable in phone players either.

Burning in gives you a single file and guaranteed visibility.

The hybrid approach: preparing two versions

If you're distributing the same content to different platforms, the best solution is to prepare two versions:

Version 1 — Social media: subtitles burned in, vertical or square format, large type, positioned to avoid interface elements.

Version 2 — Web and YouTube: the video without subtitles plus a separate VTT/SRT file.

Producing two outputs from the same subtitle source is one extra processing step, but it gives the right result on every platform.

Don't do this: burning in and also offering a separate file for the same video. When the viewer turns subtitles on, they'll see them twice.

A note on accessibility

This is an often overlooked but important topic.

Burned-in subtitles are not accessible. Because they're part of the picture:

• Screen readers can't read them.
• The user can't increase the font size.
• Contrast settings can't be applied.
• They can't be sent to braille displays.

Text subtitles are accessible. The user can set size, color and background to suit their own needs.

Preparing captions type subtitles for deaf and hard-of-hearing viewers matters too — they include not just dialogue but meaningful sound events: "[phone rings]", "[tense music]", "[distant shouting]".

Decision summary

• Instagram, TikTok, short video platforms → burn in, mandatory.
• YouTube → a separate subtitle file, for SEO and translation.
• Your own website → a separate VTT plus the <track> element.
• Personal archive → embed into MKV, or an SRT file alongside it.
• Direct sharing (WhatsApp, email) → burn in.
• Corporate platform → check the platform's support; if accessibility is required, use text subtitles.
• Multiple platforms → prepare two versions.

And whichever method you choose: burning in can't be undone, so always keep the original without subtitles.