Turn a plain text file into SRT subtitles in your browser: paste the script, get timed cues. If your text has no timings they are estimated from the text length — and labelled as such.
Paste your file below and pick the format you want out. Nothing is uploaded, nothing is charged — the conversion runs inside this page.
Time codes are preserved exactly when the input has them. If you paste plain text with no time codes, the tool lays it out as evenly spaced subtitles and labels the timing as estimated — read them before publishing. Works offline; your file never leaves the browser.
Manual translation, hired voice actors, days of waiting. Creators and teams lose time and money on every single video.
Skip the old workflowI have the script as plain text and need it as a subtitle file to start from.
I do not want to hand-number and hand-time every cue from a blank file.
Some tools produce timings that look exact even though they were invented — I need to know which is which.
Upload, pick languages, and let the AI handle the rest. No software to install.
A few clicks, that is all.
A few clicks, that is all.
A few clicks, that is all.
A few clicks, that is all.
Going from plain text to subtitles is the one conversion where something has to be invented: if your text carries no time codes, any tool that outputs SRT is deciding when each line appears. Some tools hide that and hand you timings that look authoritative; this one tells you plainly what it did. Paste the text, choose Convert to SRT, and each line becomes a cue. If your text already contains time codes — the common [00:01:12] marker, or full SRT-style ranges — those are used exactly as given. If it has none, the tool estimates a duration for each line from its length (longer lines get longer cues) and lays the cues end to end from the start, and the status line tells you the timing is estimated. Either way the result is a valid, editable .srt: open it in your editor, drag the cues onto the waveform and fix the few that need it, which is far less work than building the file from scratch. It runs in the page, so no upload and no credits.
When the text has no time codes, the cues are laid out by estimated reading length and the tool says so. You get a starting point, not a fake certainty.
If your text already carries markers like [00:01:12] or full ranges, those values are kept as they are — the estimator only runs when there is nothing to keep.
The output is standard SRT, so any editor can open it. And because the conversion never leaves your browser, a draft script can become a subtitle file without being sent anywhere.
Paste the text into the input box and click Convert to SRT. Each line becomes a cue in order. If the text contains time codes they are used as given; if it does not, the tool estimates a duration for each line and lays the cues out from the start, and the status line marks the timing as estimated.
They are estimated from the length of each line — a longer line gets a longer cue — and the cues are placed one after another from zero. That is an approximation of reading speed, not a measurement of your audio, and the tool labels it as estimated so you know which cues to check. It is meant to save you the mechanical part, not to replace the review pass.
Yes. If your text contains markers such as [00:00:12] at the start of a line, or conventional SRT time ranges, those values are used exactly as written and no estimation happens. That is the fastest route if you already know roughly where the lines belong.
Yes — standard SubRip, openable by any video editor or player. What it is not is a verified one: if the timing was estimated, check it against the audio before publishing. The page states clearly which of the two situations you are in.
No. The conversion runs in JavaScript inside your page, so your script or transcript is never sent to a server. Nothing to sign up for, and no credits are spent.
Yes. Nothing to install, no account, no upload and no credits — the conversion runs inside the page, in your browser.
We use local storage only to keep you signed in — no tracking cookies, no third-party ads. See Privacy Policy
SpeakVid does not use tracking or advertising cookies. The only storage used is listed below.