Blog
How to Create an SRT File From Video, Audio or Text
Author: Hushscript Published: Last reviewed:
To create an SRT file, transcribe the audio of your video or recording and export the transcript as SRT. Every spoken line becomes a numbered cue with its start and end time already filled in. The subtitle generator does this online, in your browser, so you never type a timestamp. If all you have is text, you can also write an SRT by hand, and there is a section on that below. This guide covers what the format contains, how to make an SRT file from a video, audio or text, and how to clean the result up so the captions read well.
What you need before you start
You need the video file and a few minutes. Any common container works: MP4, MOV, MKV, WebM, AVI, and the rest. You do not need editing software to create the SRT, and you do not need to convert the video first. A subtitle editor is optional and only useful later, if you want a timeline view while you fine-tune timing.
For full transcription, you need an account and enough available minutes. Eligible personal accounts can receive 30 free minutes once after successful card verification, or with their first purchase if not already granted. The 5-minute preview that renders first needs no account, so you can see the quality before committing to anything.
What an SRT file is
SRT stands for SubRip Text. For a fuller explanation, see what an SRT file is and how it compares with VTT. The format is deliberately simple: a sequence of numbered blocks, each made of three parts stacked on separate lines. First an index number, then a start --> end timestamp, then one or two lines of subtitle text. A blank line separates one block from the next.
1
00:00:02,340 --> 00:00:05,810
The audio is extracted in your browser.
2
00:00:06,100 --> 00:00:09,440
Only the audio reaches the server, not the video.
A few details matter when you read or hand-edit a file. The timestamp format is HH:MM:SS,mmm, hours through milliseconds, and the separator before the milliseconds is a comma, not a period. The arrow between the two times is exactly two hyphens and a greater-than sign. The index numbers should run in order from 1 with no gaps. Get any of those wrong and some players will silently drop the affected cue, which is the single most common reason a hand-edited SRT “stops working” partway through.
SRT support is broad across desktop players, editors, and hosting platforms, but it is not universal. The Library of Congress format description documents SRT as a simple sequence of numbered, timed text cues; each destination still decides which caption formats it imports. The native HTML <track> element uses WebVTT for timed text, as defined in the WHATWG living standard, which is a quick conversion covered further down.
How to create an SRT file from a video
Hushscript works as an SRT generator and SRT file maker: it transcribes the audio, times each line, and exports the result as .srt. To generate an SRT file from a video, you need the video, an account and enough minutes for its length. The flow has three stages, and the order is the part people get backwards. You drop the file first and preview it before any account exists.
- Drop your video to get a free preview. Go to video to text, or MP4 to text if your file is an MP4, and drop the video onto the upload area. The audio track is extracted in your browser using a local processing library, then the first 5 minutes come back as a speaker-labeled preview. No account is needed for this step, and the video itself never leaves your device.
- Sign up to transcribe the rest. Once the preview looks right, create an account to run the full file. Eligible personal accounts can receive 30 free minutes once, after card verification or with their first purchase. Use a payment method shown at checkout. A card is not required to start. Transcription is paid because it runs on top-tier AI, so it is pay-as-you-go with no subscription. For a longer video that exceeds the free minutes, see the pricing page; you pay per minute of audio, not per file.
- Get the transcript and export SRT. When the transcript is ready, open it in the editor, make any corrections, then click export and choose SRT. Each spoken utterance becomes one cue with its start and end timestamp already in place. The download is a plain
.srtfile with no watermark.
Speaker labels appear in the editor before you export. If you want names in the captions, useful for interviews, debates, or panels, rename “Speaker 1” and “Speaker 2” to the real names first; the export then writes those names at the start of the matching cues.
A worked example
Say you have a 12-minute recorded interview, founder-chat.mp4, with two people. You drop it on the page, the 5-minute preview confirms both voices are picked up cleanly, and you sign up. When the full transcript is ready, you rename the two speakers to “Maya” and “Devin,” fix one misheard product name, then export as SRT. The opening of the file looks like this:
1
00:00:01,120 --> 00:00:04,460
Maya: Thanks for making the time today.
2
00:00:04,800 --> 00:00:08,210
Devin: Of course. I have been looking forward to this.
3
00:00:08,540 --> 00:00:12,900
Maya: Let us start at the beginning. How did the idea come about?
Two things are worth noticing. Each cue maps to one natural utterance, so the timing follows the conversation rather than a fixed clock. And the gaps between cues, here a few hundred milliseconds, reflect the real pauses between speakers. That is usually exactly what you want, with one caveat covered next.
Create an SRT file from audio
A video is not required. If you have only a recording, such as an MP3, WAV, or M4A file, the steps are the same: drop the file, check the free preview, sign up to run the full transcript, and export as SRT. The result is a captions file you can pair with a video you edit later, or use as a timed transcript on its own. The audio to text page lists the supported formats.
Create an SRT file from text
You can also make an SRT file with no software beyond a plain-text editor, because the format is only text. Use this route when you already have the wording and the timings, for example a short script you timed yourself.
- Open a blank file in a text editor and type
1on the first line. - On the next line write the start and end time, such as
00:00:02,340 --> 00:00:05,810. - On the following line or two, type the caption text.
- Leave a blank line, then repeat with
2,3, and so on. - Save the file with the
.srtextension, not.txt.
The slow part is the timestamps: you have to read them off the recording one cue at a time. Hushscript generates captions from the audio itself, not from a script you already have, so for a long recording it is the faster way to get timed cues. For short clips, doing it by hand is fine.
Is there a free SRT file generator?
Partly. What costs nothing:
- The preview. Drop a file and the first 5 minutes come back as a speaker-labeled transcript, with no account. It shows you the quality; the SRT download comes from the full transcript.
- Your first 30 minutes. Eligible personal accounts get 30 free minutes once, after card verification or with the first purchase. For an eligible account, a recording of up to 30 minutes can go from file to SRT at no charge.
- Writing the file by hand, as above.
- Converting a file you already have. The subtitle converter is free and runs in your browser, but it only converts an existing caption file. It does not make captions from audio or video.
Past the free minutes, you pay per minute of audio, with no subscription. See the pricing page. Anyone searching for an SRT file creator that is free for every file will not find that here, and it is better to know before you start.
Packs are prepaid, so a month without video costs nothing. The pay-as-you-go transcription page explains how the per-minute pricing works.
Edit timing and line length
Most exports are usable as-is, but two quick checks make captions noticeably easier to read. This short pass is what separates auto-generated captions from ones that feel professional.
Line length and number of lines. Style guides vary, and the SRT format itself does not enforce a universal line length or line count. A long cue can still become a wall of text. Follow the destination’s current rule when it has one; otherwise, keep each cue compact, split at a natural phrase boundary, and check the result on the final frame size.
Reading speed. Length on screen has to match how long the cue is shown. If a cue shows a lot of text for a very short time, split it at a natural pause or retime it without covering later speech. Preview the captions at normal playback speed instead of judging timing from the text file alone.
Timing gaps and overlap. A gap shorter than about 80 milliseconds between two cues can make some players hold the previous line too long or skip the next one, so leave a small breath between back-to-back cues. The opposite problem is overlap: when two people talk over each other, the engine assigns each speaker a separate cue, and those cues can collide in time. No automatic tool resolves true overlap perfectly, so for dialogue-heavy footage, scan for overlapping timestamps and nudge one cue earlier or later by hand.
You can do all of this in any plain text editor, since the format is human-readable. The export workspace also has subtitle re-segmentation controls if you want to change how the lines are split. If you would rather work visually, a dedicated subtitle editor such as Subtitle Edit on Windows or Aegisub on any platform adds a waveform timeline and can auto-fix common spacing and reading-speed issues in bulk.
SRT vs VTT: which one to export
The two formats are close cousins, and the right choice comes down to where the captions will play. If you want the full comparison before you commit, SRT vs VTT: which subtitle format to use breaks down each format’s strengths.
Reach for SRT for desktop players, video editors, and the great majority of hosting platforms, which is most of what people need. Reach for WebVTT when the captions go on a custom web page using the HTML5 <video> element, because that is the only format browsers read natively for the <track> element. The content is identical between them. VTT just adds a WEBVTT line at the top of the file and uses a period instead of a comma before the milliseconds in each timestamp.
Because the difference is that small, you do not need to re-transcribe to switch. Export SRT, and if you later need VTT, run it through the free SRT to VTT converter. It works in your browser with no account, and nothing uploads.
Add the SRT to a player, editor, or platform
Once you have the file, attaching it depends on where the video lives.
Desktop players. VLC, mpv, and most desktop players auto-load a sidecar SRT when it shares the video’s base name and folder. Rename your file so interview.mp4 is paired with interview.srt, drop them in the same directory, and the captions appear on playback. If a player misses it, its subtitle menu has a manual “load subtitle file” option.
Video editors. In DaVinci Resolve, Premiere Pro, or Final Cut, import the SRT as a subtitle or caption track. The editor drops each cue onto the timeline at the right timecode, and from there you can restyle the font, change the position, and burn the captions into the final export if you want them hardcoded.
Hosting platforms and social video. YouTube accepts SRT directly in its subtitle workflow. Other platforms may accept a sidecar file, require their built-in caption editor, or expect captions burned into the video. Keep the reviewed SRT as your source of truth, then use the destination’s current publishing flow rather than assuming one upload method works everywhere.
Burning the captions in. If you need the text permanently part of the picture rather than a toggleable sidecar, that is a separate encoding step. HandBrake can burn an SRT into a video for free: load the video, add the SRT under the Subtitles tab, tick “Burned In,” and encode. Reach for this only when the destination cannot read a sidecar file, since a separate SRT stays editable while a burned-in caption does not. For a fuller walkthrough of attaching and burning in captions across each platform, see how to add subtitles to a video.
Common issues and how to fix them
Captions are out of sync from the very start. A constant offset, where every line is early or late by the same amount, usually means the player is reading a slightly different frame rate than the one the timings assume. Most desktop players have a subtitle-delay control to shift the whole track at once; nudge it until the first line lands, and the rest follows.
Sync drifts further apart over time. Drift that grows as the video plays points to a frame-rate mismatch between the source and the rendered copy, common after converting a 23.976 fps file to 25 fps or back. Re-export the SRT against the version of the video you will actually publish, rather than an earlier cut.
A speaker’s name is missing from the captions. If you renamed labels but a platform shows no names, that platform likely strips speaker prefixes from SRT on import. There is no SRT setting that forces them; the reliable fix is to burn the captions in, where the names are part of the picture.
A non-English video came back in the wrong language. Hushscript detects the spoken language automatically across about 99 languages, but a very short or noisy clip can occasionally be misread. Re-run a cleaner section, or check the languages page to confirm the language is covered.
Long stretches read as one giant cue. This happens when someone speaks for a long time without a clear pause. Split the cue manually at a sentence boundary so no single block holds more than two lines of readable text.
Accuracy tips that pay off in fewer edits
Most of the quality of your captions is set before you ever open the editor, by the audio you feed in. Clean source audio means fewer misheard words and tighter timestamps, which means a shorter edit pass.
Record or export the audio at a normal speaking level without heavy compression, and avoid loud background music under dialogue where you can. When several people are involved, a recording where each voice is reasonably distinct helps the speaker labels stay consistent, which matters if you plan to keep names in the captions. If the source is a video you have already published, the audio is whatever it is, but for anything you record yourself, a few minutes of attention to levels and microphone placement does more for caption quality than any amount of editing afterward.
After the SRT: the rest of the transcript
Creating the SRT also gives you the full transcript, so you are not limited to subtitles. From the same session you can export the text as TXT or DOCX for show notes, a blog version of the talk, or an accessible transcript posted next to the video. Exporting a clean transcript is the same product as captioning a video to text; the SRT is just one of the formats that come out of it.
For the next step, putting these captions onto the video and choosing between a sidecar file and a burned-in track, see how to add subtitles to a video.
Independent sources and standards
Hushscript consulted these independent, non-competing references. They explain research, standards, or platform behavior and do not endorse Hushscript.
Sources reviewed: