Readable subtitles make a product demo easier to follow when someone cannot use sound, is in a noisy place, or needs the spoken words in text. The best result depends on accurate wording, timing, contrast, and where captions sit on the screen. This guide explains a practical review process and the difference between a caption file and subtitles burned permanently into the video.
Decide how the captions should be delivered
There are two common delivery choices. A separate caption track can be turned on or off in a compatible player and may be edited without encoding the video again. Burned-in subtitles are part of the picture: they appear everywhere the video plays, but viewers cannot hide them and changing them requires a new export.
Use a separate track when the platform and playback context support it and you need language options, accessibility controls, or future corrections. Use burned-in text when the video will be shown in a player that ignores caption tracks, or when a social post needs text to appear consistently in its preview. Some projects need both: a caption track for the accessible master and a burned-in copy for a specific distribution channel.
Captions and subtitles are sometimes used interchangeably, but the terms can mean different things in accessibility workflows. Captions generally include speech and relevant non-speech audio cues; subtitles often focus on spoken dialogue, sometimes translated. Follow the terminology and requirements of the platform or organization preparing the video rather than assuming a single definition applies everywhere.
Start with an accurate transcript
Timing cannot repair incorrect text. Begin with a transcript that reflects what the speaker actually says, including product names, button labels, numbers, and acronyms. A demo might say “select Export, then choose PNG”; captions that substitute “import” for “export” can send a viewer to the wrong place even if the words appear at exactly the right time.
Review the transcript against the final audio, not a script from an earlier edit. People often change wording while recording. Also check whether the speaker points to an interface label or says “this button”; if the video may be watched on a small screen, naming the control can be clearer than relying on a gesture.
For non-speech audio, decide whether a cue matters to understanding. A notification chime that signals a successful save may be useful to caption. Background music that adds no information may not need a detailed description. Avoid adding sound labels that are not present or that imply emotion the audio does not convey.
Break speech into readable chunks
A caption should be short enough to read while watching the action. Split at a natural phrase or sentence boundary instead of cutting between a verb and its object. For example, “Open the export menu” is a sensible unit; “Open the / export menu” is not.
For a tutorial, caption breaks should also respect the sequence on screen. If a speaker explains three steps while rapidly clicking through them, a single long caption forces the viewer to read while trying to locate each control. Separate the ideas, and consider slowing the demonstration or holding the relevant screen until the caption has been read.
Do not cram a full paragraph into one subtitle. A short caption can still be too dense if it contains unfamiliar technical terms. Remove filler only if doing so does not change the meaning, or re-record the line more concisely. Do not paraphrase safety, pricing, or product limitations in a way that changes what was said.
A practical timing pass
Review the video in three passes:
- Entry: Does the caption appear when the phrase starts, without arriving after the viewer needs the information?
- Reading time: Can a viewer finish reading before the next caption or visual change? A long product name or unfamiliar acronym may need more time than a short instruction.
- Exit: Does the caption disappear when the idea ends, rather than lingering over the next action?
There is no single reading-speed number that works for every audience, language, age group, or viewing situation. Use a timing guideline from your platform or accessibility standard when one applies, then review the result with the actual content and audience in mind. Mark uncertain timings for another pass rather than pretending the first estimate is exact.
Keep captions clear of interface controls
A video may be shown inside a web player with progress, volume, and fullscreen controls. A social app may add a title, account name, or buttons over part of the picture. Put captions inside a comfortable safe area, away from the very bottom and edges, and check them in the destination's actual player if possible.
For a software demo, lower captions can cover status messages or menus. Upper placement may work better during an interaction, but can cover a title or important visual. Review each scene: moving subtitles to a fixed safe area is convenient, yet it may obscure a different part of the interface later. When the subject moves around the frame, check more than one moment.
Make text readable over changing backgrounds
A white subtitle can disappear over a pale background; black text may disappear over a dark video. Add enough contrast for the full clip, not only the opening frame. An outline or a solid/semi-transparent backing can help, but heavy styling can make captions feel like a separate banner.
Use a type size that remains legible on a phone. Check a normal mobile preview rather than zooming into the full-resolution source. Avoid thin fonts, condensed lettering, and long all-caps phrases, which can be harder to read quickly. Ensure text is not clipped at the bottom or sides after the output is resized.
A quick visual check should include:
- a bright scene and a dark scene;
- a frame with detailed or moving background content;
- the smallest expected display size;
- captions near the beginning, middle, and end;
- the player's overlays, if the video will be embedded or posted.
If the caption is hard to read at phone size, do not solve the problem only by enlarging it. Try a subtle outline or background, shorten the text where meaning allows, and reserve enough screen space around it.
Keep subtitle files and burned-in exports straight
A SubRip subtitle file commonly uses the .srt extension and stores numbered entries with start and end times. Entries contain text and can include simple formatting conventions, but support differs across apps. Keep a copy of the subtitle file and name it clearly so it stays associated with the correct video.
Burning subtitles into a video requires re-encoding the picture, which can change visual quality, file size, or processing time. Keep an untouched video master. Export a separate captioned copy and compare movement, fine details, text, and audio sync. If the result looks softer than the source, check export settings and avoid repeatedly re-encoding the same file.
The Toolsnix Video Subtitles tool can burn an SRT file into a video or extract a subtitle track. Its current burn workflow accepts SRT, styles the rendered text, and exports an MP4; this is a permanent render and re-encodes video. Its extraction workflow targets the first subtitle stream, so it is not a general-purpose multi-language track editor. It does not provide a caption transcription service or an editor for correcting subtitle timing. Review the tool and the downloaded file for the specific task you need.
Check the result in context
Watch the exported file from beginning to end, or at least inspect every caption boundary and every section where the visuals change quickly. Do not rely only on a still frame. Check that the caption appears with the matching spoken line, stays long enough to read, and does not cover a button, product detail, or speaker's face.
Then test the video in the intended player. If you deliver a separate subtitle track, confirm that it loads, uses the right language, and remains synchronized after seeking. If you burn text in, confirm that it is present on the downloaded file and still fits after upload or platform resizing. Keep the original and caption file so you can correct a name or timing issue without rebuilding the video from scratch.
A useful handoff includes the video version, subtitle file or burn-in status, language, and any known limitations. If someone else will publish it, tell them whether captions are already burned into the image; otherwise they may turn on a second caption track and display duplicate text.
Frequent mistakes
- Writing captions from memory: Small wording differences can change a tutorial instruction. Check each line against the final audio.
- Leaving a long line on screen briefly: Reading time depends on text length and audience. Pause the video or split the thought when needed.
- Ignoring mobile crops: A caption can fit the source frame and still collide with a cropped version or player controls.
- Using low-contrast text: A style that works on one shot may disappear in the next. Test varied backgrounds.
- Re-encoding the only copy: Keep the source video and subtitle file; treat the burned-in render as a delivery copy.
- Assuming one caption format works everywhere: Validate the file in the destination player and follow its current instructions.
Frequently asked questions
Should I burn subtitles into a product demo?
Burn them in when the destination is likely to ignore a separate track or the words must appear in every playback. Keep a separate caption track for flexible playback or accessibility controls where supported. You may need both versions for different destinations.
How long should each subtitle stay on screen?
Long enough for the intended audience to read it comfortably while following the action. Duration depends on the text, language, reading conditions, and visual complexity. Use a relevant accessibility or platform guideline as a starting point, then review the real clip.
Can subtitles be added without reducing video quality?
A separate text track can avoid re-encoding the video stream in workflows that support it. Burned-in subtitles change video frames and require a rendered output, which can affect quality. Preserve the source and inspect the export.
Why are subtitles out of sync after upload?
Possible causes include timing errors in the subtitle file, an edited video that no longer matches the original timestamps, or player handling. Compare the subtitle file to the exact final video and test it in the destination player.
Do subtitles replace a transcript?
Not always. Captions are synchronized to video; a transcript is a readable text version that may be useful separately. Your audience, platform, and accessibility requirements determine which formats to provide.
Next step
Choose one short demo, prepare captions against its final audio, and test the exported version on a phone-sized display. Correct timing and readability before sharing. Keep both the uncaptioned source and the caption data so later edits remain possible.