SRT file generator

Make an SRT file from any video, locally.

To generate an SRT file from a video, the speech has to be transcribed, split into short timed lines, and saved as numbered cues in a plain text file. suubbs does all three on your own machine: drop the video in, press Generate, fix the few words the model misheard, and press Export .srt. The free browser version does this for the first 60 seconds of any video; the Mac app does the whole video, however long it is.

Get the Mac app — $9.99 → Try it free in your browser
1 · The steps

From a video to a .srt file in five steps.

The same five steps in the browser and in the Mac app. Only the model, the speed and the length limit differ.

  1. Drop the video into the studio. MP4, MOV or WebM. The file is read straight off your disk and the audio is decoded on your machine; nothing is uploaded, in either version. Only have the recording, not the video? The same steps work on an audio file — see audio to SRT.
  2. Press Generate. Pick the spoken language from the sixteen on the list; the Mac app can also detect it for you. In the Mac app you can also type names and jargon into Names and jargon before you start, so the transcript spells "Dr. Chen" or your product name your way instead of guessing.
  3. Read it through and fix what is wrong. Click the line and retype the wrong word. The words around it keep their measured timestamps; the corrected word's time is estimated within its line — improving subtitle accuracy explains that, and the settings that leave fewer words to fix. Lines that read faster than the reading-speed limit, or run past the line-length limit, are flagged in the list so you can find them without watching the whole video again.
  4. Pick a line layout. In Timing & layout (the ··· menu), choose Widescreen — 42 characters, 2 lines or Vertical / social — 22 characters, 3 lines. The lines re-flow and your corrections survive. If the file is going into an editing timeline, set the frame rate there and turn on Snap cue edges to frames.
  5. Press Export .srt. If the file is going into DaVinci Resolve or Premiere to be styled there, choose SubRip, unstyled from the ··· menu instead — section 4 explains why that variant exists. To carry the finished file inside an MP4 as a track viewers can switch on, see adding an SRT to an MP4.

The Mac app runs Whisper Large v3 Turbo through whisper.cpp on Apple's Metal, with word boundaries measured at about 3 ms. The browser version runs smaller Whisper models on WebGPU, and its word timings are looser, roughly 60 to 140 ms. For an SRT that is mostly invisible, since a cue's start and end are what a player shows. It matters more for word-by-word captions, where the highlight has to land on the syllable.

2 · Inside the file

What an SRT file actually contains.

It helps to know, because most problems people have with subtitle files come from one of these four parts being slightly wrong.

An SRT (SubRip) file is plain text. Each cue is a number, a timing line, one or two lines of caption, and a blank line:

1
00:00:02,100 --> 00:00:04,400
You could type all of these by hand…

2
00:00:04,600 --> 00:00:07,200
Or you could just press Generate.

Nothing in the format stops two cues from sharing time. Overlapping timestamps are how an SRT shows two subtitles at once, and the player decides how to lay them out. If the SRT you need is already inside a video file as a track, you do not have to generate one: extracting subtitles from a video shows how to copy it out, and how to tell when there is nothing to copy.

Save the file as UTF-8. Accented letters, curly quotes and anything outside English can come out as garbage in a player that guesses a different encoding, and a file that looks perfect in your editor is no evidence it will look perfect in someone else's player.

3 · Three ways to make one

By hand, in the cloud, or on your machine.

Every SRT generator is one of these three. They differ in where the work happens and who ends up holding a copy of the video.

  Typed by hand Upload to a web service Transcribed locally
Where the video goesNowhereTo the service's serversNowhere
Your effortEvery word and every timestampUpload, wait, correctCorrect the words it misheard
TimingAs careful as you areDepends on the servicePer word, about 3 ms in the Mac app
Best forA few lines, or a short clipWhen uploading the footage is fineAnything you would rather not upload

By hand is perfectly possible for a short clip. On a Mac, open TextEdit, switch the document to plain text with Format ▸ Make Plain Text, type the cues in the shape above, and save with a .srt extension. Then check in Finder that it did not quietly become captions.srt.txt. The slow part is the timestamps: for each line you scrub the video, note when speech starts and stops, and type both down to the millisecond.

Uploading to a web service is how most online subtitle generators work: the video goes to their servers, their speech model transcribes it, and you download the result. That is fine for plenty of footage. It is not fine for client work under NDA, unreleased material or interviews you promised to keep private, which is the case an offline subtitle generator is built for.

Transcribing locally is what suubbs does. The speech model runs on your own hardware, so there is no upload, no queue and no per-minute charge. You can also run whisper.cpp from Terminal yourself, which is free and produces an SRT; what you give up is the editor afterwards, which Whisper on a Mac, without the terminal lays out line by line.

4 · Styling

Can an SRT carry colour? A little.

The format itself has no style section. What it has is a handful of tags that many players read, and nothing beyond them.

SubRip has nowhere to declare a style for the whole file. What many players do honour is a small set of HTML-like tags inside a cue: <b>, <i> and <font> with a colour, a typeface and a size. When you have styled a document in suubbs, the SRT export writes those tags for whatever differs from the default look, and only that, so an unstyled document still exports as a bare file every tool expects. A player that does not parse them shows them as literal text, which is the risk of using them at all. The size tag is written in pixels against the video's height — subtitle font size has the conversions.

What SRT cannot carry, with or without tags: the backing box, the outline or shadow, the position on screen, letter spacing, fades and word-by-word highlighting. suubbs names whichever of those you used when you export, rather than letting you find out on the upload. If they matter, export Advanced SubStation (.ass), which keeps them (a backing box currently needs a one-line override at burn-in) and is what ffmpeg uses to burn subtitles into the video, or WebVTT for a web player, which holds most of them as CSS — WebVTT styling shows what it writes. Where a caption sits is covered in subtitle position, including the {\an8} tag some players read in an SRT.

SubRip, unstyled exists for the opposite case. DaVinci Resolve treats a cue that arrives carrying its own tags as hand-styled, so the subtitle track's style stops reaching that one line while every other line takes it. A file that states nothing lets the editor style all of it at once. Use it whenever the styling will be done in the editor, as in subtitles for DaVinci Resolve and Final Cut Pro.

5 · Which export

SRT is usually right. Here is when it is not.

suubbs writes five files from the same timings, so choosing one never means transcribing again.

6 · When it will not load

The file is made and the player ignores it.

Check these in order. The first three cover almost every file that "does nothing".

  1. The extension. captions.srt.txt is a text file, not a subtitle file. Finder hides extensions by default, so check with Get Info.
  2. The milliseconds separator. A comma in SRT, a full stop in VTT. A file converted by hand often has the wrong one on some lines and not others.
  3. The blank lines. One empty line between cues, and no stray spaces on it in a strict player.
  4. The encoding. Re-save as UTF-8 if accented letters come out wrong.
  5. The timing itself. If the captions appear but early, late or drifting further out as the video plays, the file is valid and timed for a different version of the video. Fixing subtitles that are out of sync tells the three cases apart.
  6. The reading speed. If the captions are there but nobody can read them in time, the lines are too long or too fast. The usual limits, 42 characters a line and about 20 characters a second, are explained in subtitle reading speed.
SRT questions

The ones that come up every time.

Short answers, including where the format simply gives up.

How do I generate an SRT file from a video?

Transcribe the speech, split it into short timed lines and save them as numbered cues. In suubbs that is: drop the video in, press Generate, correct the words it misheard, and press Export .srt. Transcription runs on your own machine, so the video is never uploaded.

Can I make an SRT file for free?

Yes. The browser version of suubbs needs no account and transcribes the first 60 seconds of any video, with every editing and export control working on that minute. The $9.99 Mac app transcribes the whole video. Typing an SRT by hand in a plain-text editor is also free, just slow.

What is an SRT file?

A plain text file listing numbered cues, each with a start and end timestamp and one or two lines of text. It is the oldest and most widely supported subtitle format there is — every video player, every editor and every social platform reads it.

Can an SRT file hold colour or position?

Colour, typeface, size, bold and italic, partly: many players read a few HTML-like tags inside a cue, and suubbs writes them when you have styled the document. Position, outlines, boxes, fades and word highlighting have no place in the format at all. If those need to survive, export SubStation Alpha (.ass) instead.

What is the difference between SRT and VTT?

WebVTT is the web-native descendant of SubRip. The syntax is nearly identical — VTT uses a dot before milliseconds where SRT uses a comma, and adds a WEBVTT header. Use VTT for HTML video track elements and SRT for everything else.

How do I add an SRT to a video permanently?

That is called burn-in, and it re-encodes the picture. Export a styled .ass file and run ffmpeg -i input.mp4 -vf "subtitles=captions.ass" -c:a copy output.mp4. suubbs does not have a one-click burn-in button yet. The full walkthrough is in how to burn subtitles into a video.

Which languages can it generate subtitles in?

Sixteen: English, Spanish, French, German, Italian, Portuguese, Dutch, Polish, Russian, Japanese, Korean, Chinese, Hindi, Arabic, Turkish and Ukrainian. The Mac app can detect the language for you, and it is worth letting it if you are not sure: telling the model the wrong language produces a translation rather than an error.

Can I generate an SRT without uploading my video?

That is the whole point of suubbs. Transcription runs on your own machine in both the free browser version and the Mac app, so the video never leaves it.

Keep reading

Related

An SRT in about a minute.

[00:00:04,600 → 00:00:07,200]