Subtitle workflows
Separate subtitle files or burned-in captions: which should you keep?
Choose a subtitle workflow based on where the video will play, whether viewers need language choices and whether you plan to edit the text later.
Keep a separate subtitle file when you want editable text or selectable languages. Consider burned-in captions when visible text must remain part of the picture in the destination workflow. Before choosing, test the actual player and sharing destination.
This is a format and workflow guide, not a hands-on test of a particular WarpFetch release. Source availability, output options and player support still need to be checked for your media.
What a separate subtitle file contains
A subtitle file stores text and timing separately from the video image. WebVTT, commonly saved with a .vtt extension, is a text-based format for timed tracks. MDN documents its use for captions, subtitles and other synchronized text.
For browser video, the HTML track element can associate a WebVTT file with a media element and identify its language and purpose. Desktop players have their own supported formats and ways of selecting a subtitle file; browser support does not establish support in every player.
What changes when captions are burned in
Burned-in captions are part of the video image. A viewer cannot switch off that text through the player's subtitle selector. Correcting the wording requires another output from editable source material rather than just replacing a sidecar text file.
This makes the intended destination important. If an upload workflow discards separate files, delivering only a video and a subtitle sidecar may not produce the result you expected. Verify the destination before committing to a full batch.
| Your next task | A practical starting point |
|---|---|
| Correct words or timings later | Keep the separate subtitle file and original video |
| Offer a choice of languages | Keep separate language tracks and test selection in the player |
| Deliver a clip whose text must stay visible | Test a burned-in copy at the final viewing size |
| Archive material for future uses | Preserve source video and available text before making delivery copies |
A small test that avoids a large rework
- Choose a short item you are permitted to save and confirm that the desired subtitle language exists.
- Save the video and available subtitle output. Use file names that make their relationship clear, such as a shared title plus a language suffix.
- Open them in your intended player. Check a line near the beginning and another later in the video for synchronization.
- If your destination needs visible text in the image, create and inspect a short delivery copy before processing everything.
- Keep the original materials until you have confirmed the final result.
An illustrative archive might keep lecture.mp4 beside lecture.en.vtt. That naming convention helps you organize files; it is not a guarantee that a player will load subtitles automatically.
Diagnose the actual subtitle problem
No subtitle track at the source: changing the file extension does not create one. Subtitle extraction and speech transcription are different tasks.
A saved file does not display: check player format support and whether the correct file was selected before concluding that the video download failed.
Text appears at the wrong time: record whether the offset is constant or changes during playback. That distinction gives support more useful information than “subtitles do not work.”
WarpFetch's plan page distinguishes VTT extraction from Pro burn-in tools. Confirm availability for your source and version before selecting a plan solely for subtitles. For a problem report, include the language, file type, player and observed behavior using the support checklist.
In WarpFetch 1.2.1, the subtitle controls are scoped to eligible YouTube tasks. A single-video task must have returned subtitle tracks and must not be live or audio-only. The available choices are Save as file (.vtt) and Embed into video; the latter requires Pro. These conditions were checked against the matching application's interface logic, not an end-to-end subtitle download test.