How to Edit an SRT File (3 Methods That Work)

SRT files look intimidating if you've never opened one. They're not. They're plain text documents with a specific structure, and any text editor can open and change them.

The tricky part is the timestamp format. Get that wrong and your video player drops the file entirely, or every subtitle fires at the wrong time. This guide covers 3 methods for editing SRT files, the most common mistakes, and how to start with a clean SRT in the first place.

To edit an SRT file, open it in a plain text editor (Notepad on Windows, TextEdit on Mac, or VS Code on any system), make your changes, and save as UTF-8. For timing-heavy edits, Subtitle Edit is a free desktop app for Windows and Linux that shows subtitles alongside a waveform. Online tools like Kapwing work for quick text fixes without installing anything.

What's Inside an SRT File

Before editing anything, understand what you're looking at. An SRT file is a plain text document built from repeating 4-part blocks:

1
00:00:02,500 --> 00:00:05,000
Hello, welcome to the channel.

2
00:00:06,000 --> 00:00:09,500
Today we're covering subtitle editing.

Each block has a sequence number, a timestamp line, the subtitle text, and a blank line to close it.

SRT files (SubRip Text) are plain text documents built from repeating 4-part blocks: a sequence number, a timestamp line, subtitle text, and a blank line. The timestamp format is HH:MM:SS,FFF, where the comma separating seconds from milliseconds is mandatory. Substituting a period breaks most video players and upload validators. Each block ends with a blank line; skipping it causes two entries to merge into a single subtitle in most parsers. SRT has no built-in character encoding specification, but UTF-8 is the accepted standard for multilingual content. The convention for line length is 42 characters per line, with a maximum of 2 lines per subtitle entry. Lines that exceed these limits get cropped by broadcast and streaming players. A standard hour-long recording generates roughly 600–900 subtitle entries. That makes a text editor practical for typo fixes and small adjustments, but tedious for re-timing an entire file.

If you're deciding between SRT and VTT for your project, SRT vs VTT: Which Subtitle Format Should You Use? covers the differences.

Method 1: Edit with a Text Editor

A plain text editor is the fastest route for fixing a typo, correcting a speaker name, or nudging a timestamp by a second.

What to use:

• Windows: Notepad (built-in) or Notepad++
• macOS: TextEdit (switch to Plain Text mode under Format first) or BBEdit
• Any OS: VS Code, Sublime Text

Steps:

1. Right-click the .srt file and select "Open with" → your text editor
2. Use Ctrl+F (Cmd+F on Mac) to find the text you need to change
3. Edit the subtitle text or timestamp values directly
4. Save as UTF-8: in Notepad, go to File → Save As and set the Encoding dropdown to UTF-8

For timing edits, the timestamp reads: HH:MM:SS,FFF --> HH:MM:SS,FFF

To push a subtitle 2 seconds later, add 2,000 milliseconds to both the start and end times:

Before: 00:00:05,000 --> 00:00:08,000
After:  00:00:07,000 --> 00:00:10,000

This works well for 1 or 2 entries. For shifting the entire file by a fixed offset, a dedicated tool is faster.

Limitation: Text editors don't show audio or video alongside the text. That's fine for typos and speaker names, but risky for multi-entry timing changes where you need to hear the audio to get it right.

Method 2: Subtitle Edit for Precision Timing

Subtitle Edit is a free, open-source desktop app for Windows and Linux. It shows each subtitle entry in a list alongside a waveform, so you can see exactly when each line fires relative to the audio rather than guessing from numbers.

Key features:

• Drag subtitle endpoints on the waveform to adjust timing without touching numbers manually
• Shift all subtitles by a fixed offset at once (Synchronization → Adjust all times)
• Auto-renumber entries after adding or deleting
• Flag overlapping timestamps and lines over 42 characters
• Export in multiple formats (SRT, VTT, ASS, and more)

How to use it:

1. Open Subtitle Edit, then File → Open → select your .srt file
2. Load your video in the video panel (optional but helpful for timing checks)
3. Click any entry in the list to edit its text in the field below
4. Drag the waveform markers to adjust start and end timing
5. File → Save to overwrite the original, or File → Save As to keep a copy

Subtitle Edit catches common errors automatically: overlapping entries, entries shorter than 1 frame, and subtitle lines over the 42-character limit.

macOS users: Subtitle Edit runs natively on Windows and Linux. On Mac, Aegisub and Jubler are the closest free alternatives. Both use the same waveform-based approach.

Method 3: Online SRT Editors

Online tools skip the install step. They're the right choice when you're on a work or school machine with software restrictions, or when you only need to fix a handful of entries.

Kapwing lets you upload an SRT file, edit entries in a timeline interface, and download the updated file. The free tier handles most editing tasks.

Clideo accepts SRT uploads and shows entries in a scrollable list with direct text and timestamp editing. No signup is required for short files.

Subtitle.tools is a lighter option for SRT validation and quick text edits. Paste your SRT content into the editor, fix it, and copy it back out.

When online tools make sense:

• You're on a managed machine with no install access
• You only need to fix a few text entries
• You want to validate that the SRT structure is correct before uploading to YouTube or another platform

When to skip them: For sensitive content or files over 60 minutes, a local tool keeps your data off third-party servers.

Common SRT Editing Mistakes

Using a period instead of a comma in timestamps. The format is 00:00:05,000, not 00:00:05.000. A period causes most parsers to reject the timestamp entirely, including YouTube's subtitle validator.

Missing the blank line between entries. Every block must end with a blank line. Without one, two entries merge into a single subtitle in most players. If subtitles are showing up stuck together, a missing blank line is usually why.

Wrong encoding on save. If you save with Windows ANSI encoding and the file contains accented letters, non-Latin script, or any character outside basic ASCII, those characters turn into garbled symbols. Always save as UTF-8. In Notepad, that's the Encoding dropdown in File → Save As.

Out-of-order sequence numbers after editing. Delete entry 12 without renumbering and the sequence jumps from 11 to 13. Most players ignore this, but YouTube's subtitle upload flags it as a warning. Subtitle Edit's Tools → Renumber subtitles fixes it in one click.

Overlapping timestamps. Entry 5 ends at 00:00:10,000 and entry 6 starts at 00:00:09,500. Players render only the last subtitle in the overlap, which hides a line of dialogue entirely. Subtitle Edit flags overlaps automatically in its error list.

How PixScript Fits the Workflow

If you don't have an SRT file yet and need to create one from a video, PixScript handles the transcription step. Paste a YouTube, TikTok, or Instagram Reels URL into the dashboard, or upload an audio or video file directly (MP3, MP4, M4A, WAV, and other common formats, up to 500 MB). PixScript generates a timestamped transcript and exports it as an SRT file.

Download the SRT, then bring it into your text editor or Subtitle Edit for corrections. PixScript doesn't include inline editing, so the workflow runs: transcribe → export SRT → edit externally. The SRT output includes millisecond-precision timestamps, which gives you clean, well-structured starting data rather than building a file from scratch.

For a closer look at how timecoded transcripts work and what the SRT output looks like, see Transcription with Timecode.

Frequently Asked Questions

Can I edit an SRT file in Word or Google Docs?

Technically yes, but both apps silently corrupt the SRT structure. Word converts straight quotes to curly smart quotes, and Google Docs adds invisible formatting characters. Both break subtitle parsers. Use a plain text editor instead. Notepad, TextEdit in Plain Text mode, or VS Code all work without touching the underlying structure.

Why does my SRT file show garbled characters after editing?

The file was saved in the wrong encoding. ANSI or Windows-1252 encoding breaks on accented letters and any character outside basic ASCII. Reopen the original file and save it again with the encoding explicitly set to UTF-8. In Notepad, the Encoding dropdown is in File → Save As.

How do I renumber SRT entries after adding or deleting subtitles?

In Subtitle Edit: Tools → Renumber subtitles handles it in one click. In a text editor, VS Code's multi-cursor editing makes manual renumbering faster than it sounds. For large files with hundreds of entries, Subtitle Edit is the practical choice.

What's the easiest way to shift all subtitles forward or back?

Use Subtitle Edit's Synchronization → Adjust all times. Enter the offset in milliseconds (positive to move subtitles later, negative to move them earlier). Text editors don't support bulk shifts. You'd have to update every timestamp by hand, which isn't practical for anything over 10 entries.

Start With a Clean SRT

The harder part is often getting a well-structured SRT file to edit in the first place. If you're starting from a video, PixScript takes a URL or an uploaded file and produces a timestamped, exportable SRT in under a couple of minutes. From there, the methods above let you refine timing and text until it's right. Start at pixscript.com — 10 free transcripts per month, no credit card needed.