Embed SRT Subtitles in MP4 Locally

To embed SRT subtitles in MP4, you need two separate assets: an MP4 video and a timed SRT text file. This page does not draw captions onto the pixels. Instead, browser-based FFmpeg writes the SRT as an MP4 mov_text subtitle stream alongside the copied video and audio streams. A compatible player can expose that track in its captions or subtitle menu, which means viewers can turn it on, turn it off, or select it according to their preferences. Choose the video first, add the UTF-8 SRT file, name the track, select its language, and decide whether it should be marked as default. Keep the tab open during processing, then download and inspect the finished MP4 in the player that matters. This is a practical single-track packaging tool, not a subtitle editor, transcription service, translation engine, or hard-caption renderer.

1. 1

   Prepare a clean SRT that describes the exact video edit

   An SRT is a sequence of numbered cues with start and end timecodes and the caption text. Its timing must match this particular MP4 export, including any revised opening slate, shortened pause, or inserted end card. Before using the tool, play the source and spot-check the first cue, a middle transition, and the final cue. Export or save the subtitle as UTF-8 so accented names, CJK characters, and punctuation have a predictable encoding. Remove comments or draft notes that are not intended for viewers. Packaging a subtitle stream does not repair overlapping cues, compensate for a different frame rate, or infer who is speaking. If the source has changed since captions were approved, retime the SRT first and keep the prior version as a record.

2. 2

   Choose language and track metadata deliberately

   The language selector writes language metadata for the new subtitle stream. Pick the language viewers will actually read, not the language of the editing interface. A short title is useful when a player lists tracks, especially for distinctions such as English, English SDH, or Chinese Simplified. Marking the track as default expresses a preference to compatible players; it does not force captions to display in every browser, television, or mobile app. Some players also use their own language preferences and accessibility settings. One MP4 created by this page receives one newly embedded subtitle track, so use a dedicated multilingual authoring or muxing workflow when you must arrange several subtitle tracks, forced captions, chapters, attachments, or detailed per-track flags.

3. 3

   Package, download, and test the selectable track

   Start the conversion after both files appear in the workbench. The tool maps video streams and audio streams from the original MP4, maps the SRT as a subtitle input, converts that subtitle text to mov_text, and places it in a new MP4. The media packets are copied rather than re-encoded, so there is no new picture-quality setting to tune. That also means the source streams still need to be acceptable in the output container. After downloading, open the MP4 in the receiving player, enable subtitles, select the named track, and jump to several difficult cues. Check timing, line breaks, non-Latin characters, and the expected default behavior. Keep the source MP4 and SRT separately; the packaged file is a delivery asset, not the only editable subtitle source.

Soft subtitles live as their own stream in the container. They preserve the distinction between the video image and the caption text, which is useful when one audience needs captions and another does not. A viewer can usually change caption visibility, choose among tracks, or let a player apply language preferences. The downloadable MP4 stays one file, but the text remains separate enough to be disabled. That is valuable for review copies, learning material, product demos, and internal handoffs where a captioned picture would be too restrictive. It also keeps the video pixels untouched because this tool does not decode and re-encode them merely to add text.

Hard subtitles solve a different problem. They are rendered into every frame and therefore appear even in players that ignore subtitle streams. In exchange, they cannot be hidden, changed, or selected later without making another video. MP4 mov_text is a relatively simple text-subtitle representation, not a full visual layout format. It is well suited to ordinary dialogue captions but does not carry advanced ASS typography, positioned karaoke effects, or a branded subtitle design as a guaranteed result. Choose stream embedding when optional, selectable captions are the deliverable; choose burn-in when the visual text itself is part of the picture requirement.

The subtitle-file control accepts one SRT because MP4 mov_text packaging is intentionally narrow and broadly practical. Language writes a stream tag that helps players identify the content. Track title supplies the human-readable label shown by many player menus. The default switch sets the default disposition for that one track, but playback software may honor device, account, accessibility, or preferred-language settings first. Video and audio are copied into the output instead of being re-encoded; this protects their existing quality and keeps the job fast, but it cannot make an incompatible source codec valid for MP4. The tool also writes fast-start placement for ordinary progressive downloads. It does not add chapters, translate text, validate every cue, preserve subtitle styling, or merge several existing caption tracks.

Confirm that the output has the expected runtime and that video and sound still play before looking at captions. Open the subtitle menu, verify the track title and language, then test a cue with punctuation, a long line, and non-ASCII characters. Turn subtitles off and back on to confirm they are truly selectable rather than burned into the image. Test the default-track expectation in the intended desktop app, browser, learning platform, or device, because defaults are advisory metadata rather than a universal command. Keep a copy of the original SRT beside the project so wording, timing, and future language changes remain editable.

• Save the SRT as UTF-8 and open it once before packaging. Broken timing, malformed sequence numbers, or the wrong text encoding will travel into the new subtitle track.
• Use a concise track title such as English, English SDH, or Chinese Simplified. The title identifies the stream; it does not translate or proofread the captions.
• Test the downloaded file in the target player with subtitles enabled. A correct file may still appear silent until the viewer chooses the track or turns captions on.

The normal conversion path runs in the browser-side FFmpeg workspace. The chosen MP4 and SRT are read locally and the resulting download is created locally, without an account or an upload queue. That is useful when captions contain employee names, customer references, interview content, product plans, or material that should not be handed to a remote media-processing service just to add one subtitle track. Keep the browser tab open until the job completes and handle the downloaded file according to the sensitivity of the underlying recording.

Local processing does not remove the privacy or rights implications of the content. An SRT can make spoken names, private details, confidential terminology, or copyrighted dialogue easier to search and reuse. Check the text as carefully as the video, control who receives the packaged MP4, and follow your organization's consent, retention, accessibility, and distribution rules. If the video is under legal hold, subject to a client agreement, or needs a formal caption-approval trail, keep the source, approved subtitle version, reviewer notes, and final delivery file in the appropriate controlled system.

Use a full subtitle authoring, quality-control, or professional muxing workflow when you need multiple languages in one file, forced or hearing-impaired flags beyond a basic default, chapter markers, subtitle extraction, closed-caption standards, TTML, advanced ASS layout, broadcast delivery, DRM packaging, or frame-accurate conformance against an edit decision list. Also use a transcoding workflow when the MP4's existing video or audio codecs cannot be copied into a compatible MP4. Very long source videos can be demanding in a browser because local processing still needs memory and time. This tool is deliberately focused on one compatible MP4, one clean SRT, one labeled subtitle stream, and a quick player-side review.

• The captions must be permanently visible in every player, in a social upload, or in a screen recording. Use a subtitle burn-in workflow for that requirement.
• The source MP4 uses video or audio codecs that the MP4 container cannot accept with stream copy, or the subtitle uses ASS styling that must remain intact.