How to edit SRT files: a complete beginner guide

SRT subtitle files are simple text files. That simplicity is why they are the most widely supported subtitle format in the world — and why editing them is easier than most people expect. This guide walks through editing SRT files from a plain text editor, correcting cues, adjusting timings and validating the result before you ship it.

What an SRT file is

An SRT file (SubRip Subtitle file, extension .srt) is a text file that stores subtitle cues. Each cue has three parts: a number, a timestamp range and dialogue lines. Cues are separated by a blank line. There is no header, no styling, no metadata — just cues.

Because the file is plain text, it opens in Notepad, TextEdit, VS Code, Sublime Text or any other editor. There is no proprietary format to worry about.

What you need to edit SRT files

For most edits, a plain text editor is enough. Do not use word processors like Microsoft Word or Google Docs — they add smart quotes, may change line endings and often break the SRT structure when you save.

• Windows: Notepad, Notepad++, VS Code.
• macOS: TextEdit (in plain text mode), BBEdit, VS Code.
• Linux: any text editor including nano, gedit, Kate or VS Code.
• Browser: the tool pages on this site render and edit text without installing anything.

Understanding the SRT structure

Here is a minimal SRT file with two cues:

1
00:00:01,000 --> 00:00:04,000
Hello and welcome.

2
00:00:05,500 --> 00:00:08,750
This is a subtitle file.

Rules you should respect when editing:

• Every cue has a cue number on its own line (1, 2, 3…).
• The next line is the timestamp range, using HH:MM:SS,mmm --> HH:MM:SS,mmm.
• Milliseconds use a comma, not a period. WebVTT uses a period.
• Dialogue lines follow, one per line.
• Cues are separated by one blank line.
• Trailing spaces at the end of lines are ignored by most players but are worth removing.

Editing dialogue text safely

Dialogue edits are the most common SRT edits. Fix a typo, rephrase a line, change case. A few things to watch:

• Do not remove the blank line between cues. Doing so merges two cues into one.
• Do not add blank lines inside a cue unless you intend to split it.
• Keep HTML tags balanced if you use them — <i> needs a matching </i>.
• Avoid smart quotes. Use plain apostrophes and quotation marks.
• Respect encoding. Save as UTF-8. Non-UTF-8 encodings often produce garbled characters.

For text-only changes across many cues, the Search & Replace tool is faster and safer than manual editing.

Editing cue timings

Timing edits usually fall into one of two categories: constant shifts and per-cue adjustments.

Constant shifts

When every cue is off by the same amount (subtitles appear 3 seconds early throughout), shift every cue by the same offset. Use the SRT Time Shifter to apply a global offset — it is much faster and safer than manually editing timestamps.

Per-cue adjustments

When a single cue needs its timing tuned, edit the timestamp line directly. Keep the format identical: two digits for hours, minutes and seconds, three digits for milliseconds, comma-separated.

Validating the result

After editing, always run the file through a validator. It will catch:

• Timestamp format errors that a human eye misses.
• Cues that end before they start.
• Overlapping cues.
• Empty cues.
• Missing blank lines between cues.

Our SRT Validator does these checks in seconds and lists every issue with cue context.

Common mistakes and how to avoid them

• Saving with a BOM. Some editors add a UTF-8 BOM at the start. Most players tolerate it but a few fail. Use the Encoding Cleaner if needed.
• Using Windows CRLF line endings on macOS or Linux. Most players accept both, but a consistent LF is safer. The Encoding Cleaner normalizes this.
• Forgetting to renumber after insertion or deletion. Use Cue Renumbering to fix numbering automatically.
• Using a word processor. Word processors introduce smart quotes and sometimes change the structure. Always use a plain text editor.
• Assuming the file will load everywhere. Test it in the player you actually use. If it fails, run it through the validator.

Putting it all together

The workflow that works best is: edit in a text editor (or with our text tools), validate, then preview. Editing SRT files is not complicated — it just requires respecting the format and checking your work. The tools on this site automate the tedious parts so you can focus on the content.

Read next: How to sync subtitles or browse the full subtitle tools directory.