
Table Of Content
To add subtitles to a video, decide how viewers should receive them, then choose a tool, generate or enter the text, review every caption, and export. The key decision is whether you need burned-in text, a toggleable track, a separate file, or platform-native captions.
My editorial rule is simple: choose the delivery format before the software. That prevents a polished edit from becoming unusable on the viewer's player, TV, website, or social platform.

Subtitles make dialogue easier to follow, while captions add speaker labels and meaningful sound cues for caption accessibility. If you add captions to video, treat the transcript as a draft that still needs a human review.
As of July 2026, WHO reports that 430 million people require rehabilitation for disabling hearing loss and projects that more than 700 million may do so by 2050. Clear captions can support more viewers, but text alone does not address every accessibility need.

Subtitle file formats determine whether viewers can turn text off, whether the video must be encoded again, and how easily the wording can be revised later. Decide among burned-in subtitles, soft subtitles, sidecar files, and platform-native tracks before editing.
| Output | Can viewers turn it off? | Video re-encoding? | Typical compatibility | Future editing | Accessibility use | Best-fit scenario |
| Separate SRT or VTT | Yes, when the player loads the file | No | Depends on player or platform support | Easy to replace or revise | Good when the platform exposes caption controls | Web publishing, YouTube, and editable delivery |
| Embedded soft track | Yes | Usually not for the video image itself | Good on players that support the embedded track | Replaceable with the right container tools | Useful when controls and metadata are supported | Local libraries with known player support |
| Burned-in captions | No | Yes | Visible wherever the video plays | Requires editing the source and exporting again | Always visible, but not equivalent to a selectable caption track | Social clips, TVs, or unknown playback environments |
| Platform-native captions | Yes | No | Limited to the hosting platform | Editable in the platform interface | Often the strongest choice for platform accessibility features | YouTube and other hosted-video publishing |
Burned-in subtitles become part of the video image, so they remain visible in an MP4 even when the player has no subtitle controls. This broad compatibility costs flexibility because changing the text requires another export.
For MP4 subtitles intended for social feeds, presentation screens, or an unfamiliar TV, burned-in text is often the safer delivery choice. Keep a reviewed subtitle file and editable project so later corrections do not start from scratch.
Soft subtitles and toggleable captions let viewers show or hide the text. A separate SRT subtitle file is widely useful, while a VTT subtitle file is common in web workflows.
Sidecar files are easy to revise, but the recipient must keep the video and subtitle file together, and the player must support the format. An embedded track reduces file-management mistakes, though compatibility still depends on the container and playback device.

There are four practical ways to approach how to add subtitles: a subtitle-focused generator, a browser design editor, a full timeline editor, or manual text overlays. The right choice follows the required output and review depth, not a generic ranking.
| Workflow | Best-fit workflow | Automatic transcription | Manual transcript editing | Timing controls | Subtitle-file import | Separate subtitle export | Burned-in video export | Batch suitability | Learning curve | Cost model |
| UniFab AI Subtitle Generator | Local Windows or Mac subtitle generation for repeated files. Not ideal for mobile-only work or frame-level creative editing. | Yes | Review before delivery | Correction is part of the review workflow | Generate from source media in this workflow | Subtitle download supported | MP4 and MKV output | Yes | Guided subtitle workflow | Commercial desktop software |
| Canva | Short visual projects that combine captions with templates. Not ideal for subtitle-dense batch delivery. | Available in its subtitle workflow | Yes | Visual caption adjustments | Not used in this workflow | The rendered-video workflow is covered here | Yes | Project-based | Approachable for template editing | Account-plan model |
| Adobe Premiere Pro | Projects already being edited on a full timeline. Not ideal for a quick one-video caption task. | Yes | Yes | Detailed timeline control | Supported caption workflow | SRT or VTT delivery | Yes | Project and sequence based | More setup and editing depth | Subscription |
| iMovie | Short Apple-device projects needing visible text overlays. Not ideal for toggleable captions or subtitle-file delivery. | No | Manual text entry | Title-clip duration | No dedicated subtitle-track import | No dedicated subtitle-file export | Yes, as rendered text overlays | No dedicated batch workflow | Direct for short edits | Included with supported Apple devices |
For a broader cost-focused tool comparison, keep that research separate from this workflow decision. Platform-specific social captions and video translation also deserve their own instructions rather than being compressed into this guide.
The UniFab subtitle generator is a video subtitle generator for Windows and Mac that can create subtitles, support batch subtitle processing, and deliver subtitles with MP4 or MKV video workflows. Generated text still needs editorial review.
UniFab fits teams or creators handling repeated local files when automatic video captions can shorten the first-draft stage. Batch processing is useful when review ownership is assigned, delivery format is agreed in advance, and names, speaker labels, and sound cues are checked.
A browser-based subtitle generator online is available for a lighter upload workflow. This guide does not assume that its controls or batch behavior match the desktop product.
A reliable UniFab workflow separates generation from approval: create the draft, correct the language and timing, then choose the output. My preference is to name the reviewer before starting a batch, because automation without ownership simply moves errors downstream.
30-day Free Trial for full feature, without watermark!
Download UniFab software and launch it, select the Subtitle Generator module. Then, upload the video file for which you want to create subtitles or any SRT file with subtitles.
From the 30+ available options, select the language into which you want to translate the video subtitle. UniFab will then automatically generate the subtitles in your selected language.
Select the “Start” option to auto-generate the subtitles. Then, you will have a clear and editable .srt file with subtitles. Use UniFab Video Converter to add subtitles to your desired video.
Canva subtitles suit short, design-led videos when the captions need to match a visual template. It is a practical browser workflow for creators who want transcription and styling in one project rather than a dedicated subtitle-delivery pipeline.
Use Canva when the final result is a short rendered video and visual consistency matters more than detailed subtitle-file management. It is less suitable for long, dialogue-heavy projects or batch subtitle processing that needs formal review and handoff.
The Canva workflow combines upload, caption generation, correction, and styling. Keep the text readable before adding decorative elements; the subtitle should remain clear over changing backgrounds.
Canva's strength is visual assembly, not deep subtitle operations. A long transcript can make review cumbersome, and a template-led rendered-video workflow may not fit a client who expects separate SRT/VTT files or detailed timing handoff.
If the task is really general text animation rather than dialogue captions, the dedicated guide to add text to a video keeps that separate intent focused.
Premiere Pro captions fit editors who are already finishing picture and sound on a timeline. Its value is the ability to correct the transcript, refine timing, style captions, and choose between a caption file and a rendered video in the same project.
Create Premiere Pro captions after the edit is stable enough for timing review. Major picture changes made after captioning can create avoidable synchronization work.
Subtitle timing correction is most efficient after transcript errors are fixed. Otherwise, an editor may carefully time wording that later changes and creates another pass.
iMovie subtitles are manual title overlays rather than a dedicated toggleable caption track. This method fits a short video when the editor already uses iMovie and the final text should stay visible in the rendered video.
Build the subtitles as repeated title clips, keeping placement and styling consistent. Because each line is entered and timed manually, finish the spoken edit before starting this pass.
iMovie does not turn the overlay workflow into a separate SRT/VTT delivery or a viewer-controlled caption track. Manual entry also scales poorly as dialogue length grows.
YouTube subtitles can be added as a platform-native track by uploading a file or reviewing automatic video captions. This keeps captions toggleable and editable without changing the uploaded video image.
An existing SRT subtitle file or VTT subtitle file is useful when the captions were reviewed outside YouTube. Confirm that the timing matches the final uploaded edit.
YouTube's automatic captions are a starting point, not final copy. Review names, punctuation, speaker changes, and timing at normal playback speed before publishing an edited version.
A timing error can hide the meaning of a good transcript, especially when a caption appears after the relevant action or speaker. Correct the words first, then adjust the cue boundaries.
Ordinary viewers cannot directly add a subtitle track to another channel's YouTube upload. The channel owner or manager controls subtitles and can invite an authorized Subtitle Editor.
YouTube Community Contributions ended in 2020. Today, subtitle changes must come through the channel's own permissions, so send a corrected transcript or subtitle file to the owner rather than expecting to alter the public upload yourself.
For lawful personal viewing, you can load a subtitle file beside a local copy you own, are authorized to use, or may use under applicable law and the source platform's terms. This does not change the creator's upload or grant permission to republish it.
This guide does not cover defeating encryption, subscription gates, or access controls. Responsibility for the content, rights, and permitted use remains with the user.
For a downloaded video, apply the earlier output decision: use soft subtitles when you control the player and want future edits, or burned-in subtitles when the text must appear on a TV or unknown player.
Before editing, confirm that you own the video, have permission, or are otherwise allowed to make a personal viewing or backup copy under applicable law and the source terms. Do not share or commercially reuse material without the necessary rights.
An external SRT keeps the video stream unchanged and lets the viewer turn subtitles off. Name the video and subtitle files consistently, keep them in the same folder, and select the track in a compatible player such as VLC.
This is the most editable local option, but it depends on the recipient keeping both files together and using a compatible player.
Burned-in MP4 subtitles trade editability for predictable visibility. The video must be encoded again, so keep the source project and use export settings appropriate to the original video.
Subtitle quality control should cover the words, timing, readability, accessibility details, and final playback. Automatic output is an efficient draft, but approval requires watching the delivered version from start to finish.
Correct the transcript before fine subtitle timing correction. Then review each caption in context rather than judging isolated lines.
The most common failure I would guard against is trusting the auto-caption screen without reviewing the final video. A clean transcript can still fail through timing drift, crowded lines, or poor contrast.
Captions intended for deaf and hard-of-hearing viewers should go beyond dialogue. Identify speakers when the voice is unclear and include meaningful sounds that affect understanding.
Choose by output first, then editing depth, project volume, and review responsibility. UniFab can suit Windows or Mac users handling repeated subtitle files, Canva fits short visual work, Premiere Pro fits timeline-heavy projects, and iMovie fits brief manual overlays.
UniFab is not the right fit for a mobile-only workflow or a project that needs detailed creative compositing. Whichever method you choose, assign a reviewer and test the final delivery on the device or platform the audience will use.
These answers cover common export and troubleshooting decisions without repeating the full workflows above.
Speech recognition and timing segmentation are separate steps. Correct the transcript first, then adjust caption boundaries while watching the full video at normal speed. If the video was re-edited after transcription, regenerate or retime the captions against the final cut.
A separate SRT file or toggleable soft track does not change the video image. Burned-in captions require a new video export, so aggressive encoding settings can affect quality. Keep the original and review the rendered MP4 before delivery.
Sidecar files and toggleable tracks can usually be revised or replaced. Burned-in text is part of the image, so you need to edit the source project and export the video again.
Use accessibility captions when viewers need speaker identification and meaningful non-speech audio in addition to dialogue. Dialogue-focused subtitles may be enough for translation or comprehension, but they do not cover the full caption accessibility task.