Burned-In vs Closed Captions: Choose the Delivery

The Add Subtitles tool creates an MP4 with text permanently rendered into the picture. It does not create a selectable closed-caption channel. Follow a fictional seed-library induction video through display, web, language, and revision decisions to choose an appropriate delivery package.

Start with where and how the video will be watched

A fictional seed library has made a short induction explaining how members reserve a packet and return a record card. The same recording has three intended uses: a silent reception display, an online member resource, and an internal approval copy. Those uses do not necessarily need the same caption treatment. The display needs words visible without a viewer finding a control. The member resource may need selectable languages and viewer preferences. The approval copy needs a way to identify wording changes before release. Write those requirements down before deciding that one captioned MP4 is the complete answer to all three requests.

Ask who controls playback, whether sound is available, how large the video appears, and whether the receiving system supports a separate caption track. A looping display operated by staff is different from a personal player with caption settings. Likewise, an email attachment may be opened in several players whose controls you cannot predict. These are delivery questions, not reasons to declare one caption format universally better. A permanent viewing copy can be practical when reliable immediate visibility is the priority. A clean video with supported closed captions can offer options that a fixed layer of text cannot reproduce on its own.

Also ask what will change after release. A reservation rule may be updated, a name corrected, or another language requested. If the only retained asset is the video with English text baked in, every later version starts from a compromised master. Keep the clean recording and editable timed text even when the first request only mentions an MP4. This is not unnecessary duplication: the clean media preserves visual flexibility, while the caption file preserves wording and timing. A useful brief names the intended viewing copies and the editable sources that must remain available for maintenance after those copies leave the production folder.

Distinguish subtitle pixels from a caption channel

Burned-in subtitles are part of the video image. The renderer draws the words over each relevant frame, and the exported file carries those pixels wherever that image is shown. A viewer does not need to activate a caption track to see them. The trade-off is permanence: ordinary player controls cannot remove them, enlarge just the text, change its language, or choose a different placement. The phrase open captions is often used for text that remains visible, but describe the actual artifact in the handoff. Here it is an H.264 MP4 with rendered text, not a selectable caption stream hidden inside the container.

Closed captions remain separately represented as timed text that a suitable player can expose through its caption controls. Depending on the receiving workflow, that text may be supplied as a sidecar file or carried in a supported embedded track. Those arrangements are not interchangeable everywhere. A recipient asking for an MP4 has not necessarily specified how captions should accompany it. Ask which caption format and delivery method their system accepts. This utility does not embed a selectable track, even though it can download a separate normalized SRT describing the words used in the clip. That SRT needs its own supported receiving workflow.

Text-based captions can support functions such as language selection, styling preferences, or text search when the player implements them; the presence of an SRT alone does not guarantee every function. Burned words are not a searchable caption layer. A visible subtitle also does not become translated just because a player offers another interface language. Keep these distinctions concrete when reviewing requests. If the seed-library coordinator asks for larger captions for one member, determine whether the web player can adjust a caption track or whether another rendered version is needed. Editing the MP4 filename or toggling a nonexistent channel cannot change the pixels already exported.

Evaluate access beyond whether words appear on screen

Caption delivery and caption content are separate decisions. A permanent layer can still omit a speaker change, an important sound, or an instruction spoken while the camera shows something else. Conversely, a selectable track can contain accurate, well-timed information but be hard to discover in a poorly configured player. Review both dimensions. In the seed-library example, a sentence such as “Put it here” may need the recording’s visual context to make sense. A faithful text rendering of that sentence does not explain the destination to a viewer who cannot identify what the presenter is pointing at during the demonstration.

Include relevant speaker identification and meaningful non-speech information when the material requires them. A sound description should communicate an actual event that helps comprehension, not decorate every pause with guessed ambience. Preserve clear wording and useful punctuation while checking that viewers have time to read and watch. Visible text can compete with labels on a packet or the presenter’s hands. Selectable captions may allow some viewer preferences, but those controls depend on the player. Burned captions fix the size and contrast for everyone. Neither a chosen font percentage nor a clean validation result establishes that the finished recording meets every viewer’s access needs.

Consider companion resources when the video contains information captions cannot carry alone. A reviewed transcript can make the spoken explanation easier to consult, while meaningful visual actions may need a separate description or a revised presentation. Do not call a review PDF an accessible substitute merely because it contains some text about the project. Its job here is documenting settings and review notes, not certifying access or replacing the media experience. Ask representative reviewers about the actual delivery when feasible, including how they activate captions and follow the explanation. Treat their observations as evidence about that context, not a guarantee for every device or person.

Plan language versions before the English copy becomes permanent

Suppose the library later needs the induction in another language. With a clean master and editable caption tracks, the team can commission a reviewed translation and attach it through a receiving player that supports language choice. The image does not need to carry English underneath every other language. If only the English burn survives, adding translated text creates two competing layers or requires another editing workflow to conceal the original. Neither option restores the clean image. Preserve that clean version at the first delivery, even when the second language is only a possibility rather than a confirmed production request.

A translated track needs its own language review and timing review. The same idea can require more words, different line divisions, or a different reading rhythm. A sentence that fits three lines in one language may overflow at the same size in another. Do not assume that replacing the strings preserves a successful layout. The Add Subtitles utility does not translate text or judge whether a translation is faithful. Supply the reviewed track yourself, test its longest cues, and inspect any shortened boundary cues again. A changed term can also alter the best moment to show a sentence relative to the demonstrated action.

Choose between selectable languages and separate rendered copies according to the delivery system, audience, and maintenance capacity. A staff-controlled display may need one approved language per scheduled loop, while a web resource may benefit from a caption menu. Showing two languages at once is another editorial choice, not an automatic feature promised by a basic burn-in workflow. It can consume too much of a small frame and reduce room for the actual demonstration. Use a clear language label on every delivered asset and review record. A folder containing several files named captions-final is an invitation to pair the wrong track with the right video.

Treat each destination as a delivery requirement to verify

Do not assume every social video placement has the same caption attachment field. Native caption options can differ by account, placement, and the workflow used to upload. Confirm the receiving interface before promising that a particular sidecar will be usable there. A burned viewing copy carries visible words with the picture, but that convenience does not establish platform acceptance, ideal cropping, or a complete accessibility solution. The preparation labels in this tool identify context only. They do not inspect a destination account or validate its current upload requirements, and selecting a label does not publish anything to that service.

For the seed library’s online member page, ask the person responsible for the player to confirm the accepted track format, language label, and caption controls. For its reception display, test the actual screen from a realistic viewing distance and verify that the loop does not hide the final instruction during a transition. For a social excerpt, inspect the uploaded preview for interface overlays and unexpected framing. These are distinct reviews, even if they begin from one clean recording. The local subtitle preview is useful evidence about the chosen render, but it is not a simulation of every app, display, or physical viewing environment.

Take care when a destination also creates or displays its own captions. If the delivered video already has burned words, an additional visible track can duplicate the explanation and cover more of the frame. Choose the intended presentation deliberately and verify it in the receiving player rather than reflexively disabling useful caption options everywhere. A clean video with a separate reviewed track may be the clearer choice for one destination, while the permanent copy remains appropriate for another. Document that distinction in the handoff. Avoid telling the next person simply to upload the final video when several correctly prepared versions serve different audiences and interfaces.

Make corrections against a named source revision

Imagine an approval reviewer notices that the induction says reservations last seven days, while the newly approved fictional policy says fourteen. First decide whether the recording itself also needs revision. Replacing only the visible caption would make the text disagree with the spoken explanation. A subtitle file is not a place to quietly rewrite an inconvenient claim while leaving contradictory audio intact. Record the change request, correct the relevant source material, and approve the wording before exporting another copy. The distinction between source correction and caption correction matters more than whether the final text is burned in or selectable.

A correction to a misspelled coordinator name is narrower, but it still needs version control. Update the reviewed working track, retain the original if the change history matters, and create a new rendered copy from the clean video. Do not feed the old burned MP4 back into the tool and expect the new caption to erase the old one. The previous lettering is already part of its frames. If the delivery uses a separate caption track, changing that track may avoid video re-encoding, but the receiving system’s replacement and caching behavior still need verification. Do not assume a local file change has updated every published copy.

Use approval notes that identify the video edit, caption language, track revision, and the exact sentence or cue needing attention. “The last line is wrong” becomes ambiguous when different excerpts end on different instructions. If the selected clip changes, recheck its new first and last cues even when the middle is unchanged. A formerly complete sentence may now be clipped to a short flash. Ask the reviewer to approve the actual deliverable after the correction, not only a screenshot of the amended words. Keep the decision record close to the media package so a later maintainer can distinguish a superseded file from the approved replacement.

Create the permanent viewing copy only after the choice is clear

When permanent subtitles suit the request, bring the clean local video and existing basic UTF-8 track to the tool. This workflow accepts supported MP4, MOV, or WebM sources up to 150 MiB and five minutes, with a selected interval of 0.25 to 120 seconds. The track is limited to 64 KiB, 200 ordered nonoverlapping cues, and 500 characters per cue. Unsupported structured blocks are rejected, while reported markup or layout losses need explicit acknowledgement. These are this utility’s preparation boundaries, not a general definition of valid captions or a set of upload limits supplied by the eventual video destination.

Choose a readable treatment over the actual content. Font size ranges from three to eight percent of the shorter output edge, with color, bold, background opacity, top or center or bottom placement, and margin controls. Text can wrap to three lines; overflow is rejected instead of truncating the instruction. Preview the packet labels and hand movements throughout the seed-library sequence so the subtitle background does not conceal the thing being explained. The preview and export share a renderer, but the encoded MP4 still needs its own playback check. Browser support and a successful local review do not guarantee identical behavior on every physical device.

Export is H.264 MP4 up to thirty frames per second, with a maximum 1920-pixel edge, 2,073,600 pixels, and 64 MiB output. It does not crop or enlarge the source. If audio is requested, the tool retains it as AAC at 128 kbps and 48 kHz or fails rather than silently dropping it; mute must be explicit. Review the downloaded file with sound and without relying on sound. Confirm the complete selected explanation, not only the style. The result is one approved permanent viewing copy. It should sit beside the retained clean source, not become the only master from which future versions are made.

Hand over a package that preserves both purpose and choice

For the reception display, deliver the approved burned-in MP4 with its language and revision clearly identified. For the member resource, deliver the clean matching video and the reviewed track in the format confirmed by the player owner. For internal review, include notes naming any limitations or unresolved questions rather than treating the presence of captions as blanket approval. These example roles can share source material without sharing a single final file. If an excerpt is involved, ensure its sidecar is relative to that excerpt’s zero point. A full-source SRT paired with a shortened video is not a useful closed-caption package simply because both files contain the right sentences.

The tool’s used SRT contains the visible cues after the offset and trim decisions, with boundaries clipped to the selected interval and timestamps starting from clip zero. Retain the original track as well. Settings JSON includes transcript text, style, and time choices but not the video or its source filename. Review text, CSV, and PDF can support a handoff; the PDF contains settings and notes, not video, and is not a searchable or tagged certification. Use the Subtitle Editor when the editable track needs another wording or timing pass, then repeat the appropriate media and destination checks.

Finally, give responsibility for each next step to a real person: who uploads the media, attaches a track where supported, verifies the visible presentation, and replaces an outdated copy later. This utility performs no account connection, native publishing, or direct SMTasker import. Local files are processed in the browser, but downloaded settings and review records can contain the caption text and should be shared intentionally. There is no autosave to preserve the session for the next reviewer. A durable delivery leaves the team with a useful viewing copy today and enough clean, editable material to answer tomorrow’s language, access, and correction requests without starting over.

Questions about Burned-In vs Closed Captions

Continue with another subtitle preparation guide

Prepare your own clip with the Add Subtitles to Video, or continue with a focused guide. Find more utilities in all free tools.