Burned-in captions

Burned-in captions that stay visible everywhere you post.

Burned-in captions are rendered into the video's own pixels, so they cannot be switched off, stripped by a re-upload or missed by a player that ignores subtitle files. CaptionFX keeps the captions as editable data while you work and renders them into the frames only when you export.

Short answer

Burned-in (open) captions are drawn into the video's own pixels, so they cannot be switched off or lost when the video is uploaded. CaptionFX generates and edits captions as data, then renders them into a new MP4 only when you export. You download a video, not a separate .srt file.

Last updated

In the pixels

The words become part of each frame. Nothing to load, nothing to enable, nothing a platform can decide not to display or a re-upload can strip away.

Editable until export

Burned in is permanent, so CaptionFX keeps everything reversible beforehand. Text, timing, styling, bleeps and cuts stay data until you choose to render.

A new file, every time

Export writes a new MP4 and leaves your upload untouched. Changed your mind about the style? Edit and render again from the same source.

What is the difference between open captions and subtitle files?

Captions reach a viewer one of two ways. A sidecar subtitle file - .srt, .vtt, .ass - sits next to the video and is drawn by the player at playback time. Burned-in captions, also called open captions or hardcoded subtitles, are drawn into the video frames themselves during encoding.

Sidecar files have genuine advantages. They are editable after the fact, they can be swapped for another language, they cost nothing in file size, and a viewer can turn them off. On a platform that handles them properly - a cinema, a broadcaster, a well-built video site - they are the better engineering answer.

Social video is not that environment. A clip posted to Reels, Shorts or TikTok is re-encoded by the platform. A clip someone downloads and re-shares arrives without your subtitle file. A clip embedded in a page, a messaging app preview, an autoplaying feed, a screen recording of your post - none of these carry a sidecar. The question is not which approach is technically cleaner; it is whether the words are on screen when a stranger scrolls past with the sound off. Burned in is the answer that holds under all of those conditions.

Why does muted autoplay favour burned-in captions?

Nearly every major feed autoplays video without sound. The first seconds of your clip are therefore silent by default, and whether a viewer stops depends on whether they can tell what is being said without hearing it. Captions are not an accessibility afterthought in that context - they are the only channel carrying your words during the window that decides whether anyone watches.

This is also why caption styling is not decoration. If the text is hard to read against your footage for the first two seconds, the captions were effectively not there. Legibility against bright, moving backgrounds at phone size is the actual requirement, which is why CaptionFX gives you outline, shadow, weight and placement controls rather than one fixed overlay.

Can burned-in captions be changed after export?

The real cost of burning captions in is that it is irreversible. Once the words are pixels you cannot restyle them, retime them or fix a typo without rendering again. A tool that burns in early makes every mistake expensive.

So CaptionFX keeps everything as data for as long as possible. Caption text, word timings, styling, emphasis, bleeps and cuts all live as a document attached to your project. The video file on disk is never touched. Nothing is rendered until you press export, and the render reads that document to produce a new file.

Which means a mistake costs you one more export rather than a re-edit. The same source video can be rendered repeatedly with different styling, different corrections or a different language, and each render is a separate output file. Your upload remains the original upload throughout.

What does the render actually do?

Burning captions in means re-encoding the video, because every frame the captions touch has to be redrawn. This is why export takes real time and scales with the length of your clip rather than finishing instantly - there is no shortcut that avoids writing new frames. Audio is copied across untouched rather than re-compressed, so you lose nothing on the sound.

The order of operations inside the render is fixed and matters. Cuts happen first, because removing a section changes where every later caption belongs, and the captions are re-timed against the shortened video. Then the captions are drawn into the frames. Bleeps are applied last, over the audio, so the video stream from the burn-in step can be copied rather than encoded twice. Each stage runs on a copy; nothing works backwards into your source.

How it works

  1. Upload and generateCaptions are produced as timed data attached to your project. The video file itself is not modified at any point in this step.
  2. Correct the textFix words, adjust line timing, and bleep or cut anything that should not reach the final cut. All of it stays reversible.
  3. Style for legibilitySet type, size, colour, outline and placement so the captions hold up against your footage at phone size with the sound off.
  4. Preview the styled resultCheck the caption layer against the real video before committing to a render, since burning in is the irreversible step.
  5. Export a new MP4The render draws the captions into the frames and writes a separate file. The original upload stays exactly as you uploaded it.

Questions people ask

What are burned-in captions?

Captions rendered directly into the video's frames, so they are part of the picture rather than a separate file the player has to load. They are also called open captions or hardcoded subtitles. They cannot be turned off, and they survive re-uploads, downloads and re-shares.

Why not just use an SRT file?

Because most social platforms will not reliably display one. A re-encoded upload, a downloaded re-share, an embedded player or a messaging-app preview all arrive without your sidecar file, and feeds autoplay muted. Burned-in captions are on screen under all of those conditions.

Can I turn burned-in captions off later?

No - that is what burned in means. Once rendered, the words are pixels. This is why CaptionFX keeps everything editable right up to export, and why you can render the same source video again with different text or styling as a new file.

Does the export keep the original video?

Yes. Export produces a new MP4 and never overwrites your upload. You can go back, change the captions or the styling, and export again as many times as you want from the same source.

Does burning in reduce video quality?

The video is re-encoded, which is unavoidable when every frame has to be redrawn, and any re-encode is lossy in principle. CaptionFX encodes at a quality setting where the difference is not visible in normal viewing. Audio is copied rather than re-compressed, so the sound is untouched.

Why does exporting take a while?

Because it writes every frame of the video again. Render time scales with clip length and resolution. A short social clip is quick; a long-form video takes proportionally longer, and there is no way to burn captions in without processing the whole file.