Key Takeaways
Converting text to SRT means doing two jobs: breaking plain text into readable subtitle cues and assigning start/end timecodes to each cue. If you already have the words, you do not need full transcription software—you need a text-to-SRT workflow that creates clean timing, readable line breaks, and valid subtitle formatting. The fastest route is to paste your script into a browser-based text to SRT converter, auto-split it into cues, set timing, then make a quick manual pass for readability. If you are new to subtitle files, it also helps to understand what an SRT file is so you know what players and editors expect.
If you have a transcript, script, lecture notes, lyrics, or any other plain text and need subtitles, the hard part is not the file extension. It is timing. A valid .srt file is just numbered subtitle blocks with timecodes and text, but for those subtitles to feel professional, each block has to be short enough to read and timed long enough to follow naturally.
That is why “txt to srt” is not simply copy, paste, and save. You need to split text into subtitle-sized chunks, estimate or assign duration, and then adjust the timing so it matches how a person would actually speak. Below is the practical step-by-step process, plus the rules that prevent the most common subtitle mistakes.
What Text to SRT Conversion Actually Involves
When people search for “script to srt” or “convert text to subtitles,” they usually mean one of two things:
- I already have the words. You have text and need to turn it into subtitle cues with timing.
- I only have audio or video. You still need transcription before subtitle conversion.
This article focuses on the first case: you already have text. In that case, conversion involves two core tasks.
1. Split the text into subtitle cues
Subtitles are not paragraphs. A good subtitle cue usually contains one short sentence or one meaningful phrase. If you cram too much text into a single cue, viewers either miss the line or stop watching the video to read.
For example, this plain-text sentence is too long as one subtitle:
“Before we start, I want to explain how this tool works, what timing it generates automatically, and what you should still check manually before exporting the final file.”
A better subtitle split would be:
Before we start,
I want to explain how this tool works.
What timing it generates automatically,
and what you should still check manually.
Before exporting the final file.
2. Assign start and end timecodes
Every SRT cue needs a start time and an end time in this format:
00:00:12,500 –> 00:00:15,200
If your text came from a script, not from exact speech, you need to estimate timing based on reading speed or the actual pace of the speaker. That is why auto-timing is useful as a first draft, but not as the final answer for important videos.
A rough professional target is 15 to 17 characters per second for comfortable reading in English. Faster than that, many viewers cannot keep up. Much slower than that, subtitles can feel laggy or hang on screen too long.
Step by Step: Convert Plain Text to SRT in Your Browser
If you want the fastest path, use a browser tool built for txt to srt conversion. The workflow below is simple, practical, and works well when you already have the script ready.
Step 1: Paste your script or transcript
Open the converter, paste the plain text, and review it before generating cues. Clean input matters. Remove things that should not appear on screen, such as speaker notes, scene directions, timestamps from another format, or repeated headers.
Good source text:
- Plain spoken sentences. “Welcome back. Today we’ll cover pricing, setup, and exports.”
- Light punctuation. Periods and commas help the tool find natural breakpoints.
- One language per subtitle track. Mixed-language text often creates awkward cue splitting.
Poor source text:
- Walls of text. Huge paragraphs with no punctuation.
- Formatting noise. Bullets, timestamps, emojis, stage notes, or copy from PDFs with broken line wraps.
- Transcript filler. Excessive “um,” “uh,” or duplicated words you do not want in captions.
Step 2: Auto-split the text into subtitle-sized cues
Use the auto-splitting feature to break the text into chunks that fit subtitle reading limits. This saves time because it turns a block of text into numbered cues instead of forcing you to create each subtitle manually.
The goal is not just “smaller chunks.” The goal is readable chunks. As a starting point:
- Keep lines short. Aim for no more than 42 characters per line.
- Use two lines max. More than two lines covers too much of the frame.
- Split on meaning. Break at commas, conjunctions, or natural pauses when possible.
If one cue says “We analyzed customer interviews and found three common problems with onboarding,” do not split it as:
We analyzed customer interviews and found
three common problems with onboarding
That is acceptable. But this is worse:
We analyzed customer
interviews and found three common problems with onboarding
The second version breaks the phrase in an awkward place. Readability matters more than mechanical length.
Step 3: Apply auto-timing
Once the text is split, generate timing. A good text to SRT converter estimates cue duration from text length so each subtitle stays on screen long enough to read. This is ideal for script-based projects, rough cuts, internal review videos, or when you are preparing captions before final voiceover timing is locked.
One practical advantage here: processing happens in the browser, so your text is not uploaded while you build the SRT. That is useful for private scripts, client drafts, and internal meeting material.
Use these timing guardrails:
- Minimum duration: About 1 second per cue.
- Maximum duration: About 7 seconds per cue.
- Reading speed: Roughly 15 to 17 characters per second.
For example, a 30-character subtitle often needs around 2 seconds. A 70-character two-line subtitle may need 4 to 5 seconds. Auto-timing gets you close, but you should still review long cues, very short cues, and places where speech pace changes.
Step 4: Adjust breaks and wording
Before downloading, scan every subtitle block and fix anything that feels heavy or unnatural. This is where average-looking subtitles become professional-looking subtitles.
Watch for:
- Overlong cues. Split them into two subtitles if they read too slowly.
- Bad line breaks. Keep names, verbs, and short phrases together.
- Unnecessary filler. Remove repeated words if your use case allows clean captions instead of verbatim captions.
If your source is a formal script, this step is usually fast. If it came from a rough transcript, expect a few minutes of cleanup.
Step 5: Download the .srt file
After checking the cue text and timing, export the file as .srt. Then test it in your video platform, editor, or player. If a platform rejects the file or the subtitles display oddly, validate the format with an SRT validator before troubleshooting anything else.
Subtitle Craft Rules That Make Results Look Professional
Auto-conversion saves time, but subtitles still need craft. These rules are the difference between “technically valid” and “easy to watch.”
Keep lines readable
- Maximum 42 characters per line. This is a reliable target for most video layouts.
- Maximum 2 lines per cue. If a subtitle needs 3 lines, it almost always needs to be split.
- Prefer balanced lines. Two lines of similar length usually read better than one very long line plus one tiny word.
Respect reading speed
Professional subtitlers often work from characters per second, not just gut feeling. Around 15 to 17 CPS is a strong baseline for general audiences. Faster pacing may work for short social clips, but if you push beyond that consistently, readability drops fast.
Example:
- 50 characters at 2 seconds = 25 CPS, too fast for most viewers.
- 50 characters at 3.5 seconds = about 14 CPS, much better.
Time to natural speech pauses
Even when timing starts as an estimate, cue boundaries should align with how speech flows. End subtitles at punctuation, pauses, clause boundaries, and speaker changes where possible. If a subtitle cuts off mid-thought and the next cue appears instantly, it feels mechanical.
Stay within sane duration limits
As a rule of thumb, keep each subtitle visible for 1 to 7 seconds. Under 1 second is often unreadable. Over 7 seconds can feel frozen unless the line is very short.
How to Fine-Tune Timing After the First Export
Most script-to-SRT jobs need one more pass after export, especially if you now have the actual video or voiceover. Fine-tuning is straightforward when you know what to look for.
Shift the entire subtitle track
If every subtitle appears consistently early or late by the same amount, do not edit each cue one by one. Shift the whole file. A dedicated subtitle time shift tool is the fastest way to add or subtract a fixed offset across the full SRT.
Example: if every line appears 1.2 seconds too early, apply a +1.2 second shift to the entire file.
Retime only the problem sections
If the beginning is correct but later sections drift, your source script and the actual speech likely differ in pace. In that case:
- Shorten dense cues. Split long subtitles that force fast reading.
- Extend key lines. Increase duration for important or technical content.
- Realign transition points. Move starts and ends to pause boundaries.
Test inside the target platform
Not all players render subtitles the same way. Always preview in the real destination: YouTube, a course platform, a media server, or your editing software. If your destination prefers WebVTT instead of SRT, read this direct comparison of VTT vs SRT before exporting the final version.
Common Text-to-SRT Mistakes and How to Fix Them
| Mistake | What It Looks Like | Fix |
|---|---|---|
| Walls of text | One cue contains full sentences or paragraph-length blocks | Split by meaning into shorter cues, keep to 2 lines max, and target 42 characters per line |
| Cues too fast to read | Subtitles flash by in under 2 seconds with dense text | Increase duration or divide into more cues until reading speed is near 15–17 CPS |
| Comma vs. dot milliseconds | Timecodes use 00:00:05.500 instead of 00:00:05,500 | SRT requires commas for milliseconds, not dots |
| Missing blank lines | Subtitle blocks run together and fail to parse | Each cue needs a number, a timecode line, subtitle text, then a blank line |
| Wrong encoding | Accents or non-English characters appear broken | Save the file as UTF-8 and recheck special characters before upload |
When You Should Transcribe Instead of Convert
Text-to-SRT works only if you already have the words. If what you actually have is audio or video, conversion alone will not solve the problem. You need transcription first, then subtitle formatting.
Common signs you need transcription instead:
- You only have a recording. No script, no transcript, no captions.
- The speaker improvised. The written script does not match what was said.
- You need exact sync. Wording and timing must reflect the actual media, not an estimated read.
If your source is a YouTube video, pulling the spoken text first is often the most practical starting point. This guide on getting a YouTube transcript can help you extract the words before converting them into subtitles.
And if you regularly move between recording, transcription, and subtitle cleanup on mobile, the Soz AI app is a simple companion option for capturing speech and preparing text before you turn it into captions.
Frequently Asked Questions
Can I convert text to SRT without installing software?
Yes. If you already have the script or transcript, a browser-based text to SRT converter is enough for many jobs. You paste the text, split it into subtitle cues, apply timing, review the result, and download the .srt file. For privacy-sensitive work, browser-side processing is especially useful because the text can be handled locally rather than uploaded.
How do I time subtitles to the video exactly?
Start with auto-timing if needed, then preview the subtitles against the real video. Adjust cue starts and ends to match speech pauses, sentence endings, and speaker changes. If the entire track is early or late by the same amount, shift the whole file by a fixed offset. If only some sections drift, retime those sections manually because the speech pace differs from the source text.
Should I use SRT or VTT?
SRT is the safest default because it is widely supported by video platforms, editors, and players. Use VTT when your platform specifically asks for it or when you need web-oriented features tied to WebVTT support. If you are unsure, export SRT first, test it, and only switch if your platform prefers VTT.
How many characters should a subtitle line have?
A solid professional target is 42 characters or fewer per line, with no more than 2 lines per subtitle. That is not a universal law for every platform, but it works well in most real-world subtitle layouts. Also check reading speed, because a short line can still be too fast if it is displayed for too little time.
