Subtitle Editor

This subtitle editor opens an SRT, VTT, SBV, ASS/SSA or plain text file, lets you fix the timing and wording against your actual video, and exports it back out in the format you need. Everything runs in your browser - your subtitle file and your video both stay on your device, and nothing is uploaded.

Why use this editor

How to edit a subtitle file

1. Click Open subtitle file and choose an SRT, VTT, SBV, ASS/SSA or TXT file.
2. Optionally click Open video so you can check timing against the real footage.
3. Fix text and timing: edit a line directly, drag a waveform block's edges, or nudge start/end.
4. Use Shift, Scale or Sync to a point to fix timing problems across the whole file at once.
5. Check the validation panel for warnings, then pick a format and click Download or Copy to clipboard.

Common subtitle problems and fixes

• Subtitles are out of sync from the start: if every line is early or late by roughly the same amount throughout the video, that's a constant offset. Use Shift all timings to move everything by the same number of seconds.
• Subtitles drift further out as the video plays: if the sync looks fine early on but gets worse toward the end, that's almost always a frame-rate mismatch, not an offset. Use Scale, not Shift - the common case is a file timed for 23.976fps played against a 25fps video (or the reverse), and the editor has a preset for exactly that.
• Accented characters show as garbage: older SRT files are frequently Windows-1252 or Latin-1, not UTF-8, so letters like é, ñ or ü render as odd symbols. Use the Encoding dropdown next to the file picker to re-read the file with the correct encoding - the text updates live.
• The player won't load the file: the editor tries to repair what it can (missing sequence numbers, blank lines, backwards timestamps) rather than rejecting the file outright - check the import report for exactly which line failed and why, then fix that line and re-import.
• Subtitles overlap each other: the validation panel flags every overlap - click one to jump straight to it, then either shorten the earlier cue's end time or nudge the later cue's start.
• Text disappears too fast to read: this is a reading-speed problem - the validation panel flags any cue above roughly 20 characters per second. Either shorten the text or extend the cue's duration.
• Converting between SRT and VTT: the cue text and timing are identical - what changes is the header (VTT needs a WEBVTT line), the timestamp separator (a comma in SRT, a period in VTT), and VTT's optional extras like cue settings and styling, which SRT doesn't support at all.
• Styling is lost when converting from ASS: ASS/SSA supports fonts, colours, positioning and animation that SRT and VTT simply have no way to represent. This editor keeps your ASS style catalog intact for re-export to ASS, but inline style overrides are stripped from the plain text you edit - exporting to SRT or VTT will always be plain, unstyled text.

Got a raw recording instead of a subtitle file? Run it through the free subtitle generator first to generate captions with AI, previewed live over your video, then bring the export in here to fix the timing. Just want a plain transcript? Use audio to text instead. You can also browse all Meetrix features, or read how Meetrix's self-hosted Jitsi platform handles closed captions and live transcription.