Verbatimly

Text to SRT.

Paste a script, a transcript or an article and get a subtitle file. Timings are estimated from reading speed — the same way a subtitler does it by hand. Nothing is uploaded.

42 characters per line is the broadcast standard. Around 15 characters per second is a comfortable reading pace.

PLAIN TEXT2 cues
Hello world. This is a second sentence.
And a third one, with a comma in it.
SRT · TIMED2 cues
1
00:00:00,000 --> 00:00:02,600
Hello world. This is a second sentence.

2
00:00:02,720 --> 00:00:05,053
And a third one, with a comma in it.

When you have text but no timings

Subtitle files need a start and end time for every line. If you already have the words — a script you wrote, a transcript exported as plain text, meeting notes you want as captions — the missing piece is timing, not text.

Without audio there is nothing to measure, so this tool estimates: each line is given time in proportion to how many characters a viewer has to read. That is not a guess pulled from nowhere — it is the same calculation a subtitler makes when they read a line aloud and decide it needs two seconds.

When this is the right tool, and when it is not

How the estimate works

Three rules, applied in order:

  1. Split the text into sentences. Each sentence becomes one or more cues.
  2. Wrap any sentence longer than the line limit, preferring to break at a comma or semicolon rather than mid-phrase.
  3. Give each line characters ÷ reading speed seconds, with a floor of one second and a ceiling of seven. Short fragments get merged with their neighbour rather than flashing briefly.

The defaults — 42 characters, 15 characters per second — come from broadcast subtitle practice. Lower the reading speed if the audience is reading in a second language or the video is dense.

After you convert

The output is standard SRT, which every editor and platform accepts. If your player wants VTT instead, the difference is the header line and a period before the milliseconds — see the format comparison. To convert an existing file rather than generate one, use the VTT to SRT converter (it handles both directions).

Questions

How are timings calculated without audio?

From reading speed: each line gets time proportional to its character count, about 15 characters per second by default, with a one-second minimum.

Will it sync with my video?

Only if the speech is at a steady pace. If the video already exists, transcribe it instead — that measures real timings from the audio.

What line length should I use?

42 characters is the standard. Around 37 suits web video; above 50 gets hard to read, especially on a phone.

Does it work for Chinese or Japanese?

Yes — it counts characters, so any language works. For languages without spaces you may want a lower character limit, since each character carries more information.

Is my text uploaded?

No. The conversion is arithmetic in your browser. See the privacy policy.

Handwritten text in a notebook, the kind of script that gets turned into subtitles
Handwritten script. Photo by m01229 (CC BY 2.0)
A vintage-style microphone on a stand
Photo by www.ilmicrofono.it (CC BY 2.0)

Timing is the only thing missing

You have the words already. What an SRT needs is when each line appears — and without audio there is nothing to measure.

So the timing is estimated from reading speed. Record the script later and the captions will be close; already have the recording and transcribe it instead, for timings measured from the audio itself.

Related tools

SRT to TXT · VTT to SRT · MKV to SRT · Audio transcription