By ToolBrivio Editorial · Hands-on test of Subtitle Edit 5.3.0 (Linux x64) on October 14, 2026, plus official documentation where marked. These are ordinary source links, with no affiliate commission. Research approach · Disclosure.
We tested one job: an SRT whose cues all run 800 ms early, corrected in Subtitle Edit, saved as SRT and then saved as WebVTT. We compared the files line by line with diff afterwards.
Review basis: We downloaded SubtitleEdit-Linux-x64.tar.gz from the official GitHub release v5.3.0 (asset SHA-256 93b487e1…d44889). The release was published October 14, 2026. We ran it on Debian 13 under a headless X server with a separate home directory. We did not test video playback, waveform sync, spell check, OCR, speech-to-text or translation.
Verdict
The core timing fix works and is exact: every start and end time moved by +800 ms, the text and accented characters came through intact, and the WebVTT output used the correct . millisecond separator and WEBVTT header. The rough edges are in the Linux UI: the time box ignored typed input, the Export menu does not include WebVTT text, and the Save-as file-type list shows dozens of entries labeled “Unknown NN”. You can get the job done, but expect to hunt for it.
- Pro: Synchronization > Adjust all times… shifted all three cues by exactly 800 ms with no rounding (diff below).
- Pro: The 5.3.0 Linux build is one self-contained executable plus two native libraries. It ran directly; no Mono runtime was involved, even though
mono-completewas installed on the test box. - Pro: UTF-8 text (“café”) survived in both SRT and VTT. Neither file got a byte-order mark.
- Con: In the adjust dialog, typing
00:00:00,800into the time box changed nothing; we used the up arrow seven times (100 ms steps). - Con: File > Export lists image and binary formats (Blu-ray sup, EBU STL, WebVTT png…) but not WebVTT text. That lives under Save as with a different format.
- Con: The GTK Save-as dialog's file-type dropdown showed many “Unknown 37…Unknown 107” labels on our system, which made picking a format there impractical.
What we did
- Downloaded and unpacked the tarball, then launched
app/SubtitleEdit test_offset.srt. The grid showed three cues; cue 1 started at 00:00:01,200. - Synchronization > Adjust all times… (Ctrl+Shift+A). Set 00:00:00,800, kept “Adjust all”, clicked Show later once, then Done. Cue 1 now read 00:00:02,000 → 00:00:04,200.
- File > Save as… →
test_shifted_plus800.srtwith type SubRip. - In the main window, changed the Format combo (top right) to WebVTT, then Save as… (Ctrl+Shift+S) →
test_shifted_plus800.vtt.
Results
| Cue | Original SRT | Saved SRT (+800 ms) | Saved WebVTT |
|---|---|---|---|
| 1 | 00:00:01,200 → 00:00:03,400 | 00:00:02,000 → 00:00:04,200 | 00:00:02.000 → 00:00:04.200 |
| 2 | 00:00:04,000 → 00:00:06,500 | 00:00:04,800 → 00:00:07,300 | 00:00:04.800 → 00:00:07.300 |
| 3 | 00:00:07,100 → 00:00:09,900 | 00:00:07,900 → 00:00:10,700 | 00:00:07.900 → 00:00:10.700 |
The SRT diff shows only the three timing lines changed, plus one trailing blank line added at the end of the file (210 → 211 bytes). The WebVTT file drops the numeric cue identifiers, which is valid WebVTT, and has no final newline. ffprobe identified the outputs as subrip and webvtt respectively. If your player or a validator is strict about cue IDs or a trailing newline, check it with your own target.
Who should use it
Subtitle Edit suits someone who receives an existing SRT and needs to correct timing or convert formats locally without a subscription. It is free and open source. Video-based sync, waveform alignment and the optional speech and translation engines are where most of its depth is, according to its project page; we did not test those. If the video itself needs cutting, a video editor comes first. Then fix captions against the final cut (see fixing subtitle drift after audio edits).
Limits of this test
- A three-cue file with a constant offset. We did not test drifting offsets, frame-rate changes or point sync.
- Linux x64 build only, under Xvfb without a window manager or accessibility bus. The app logged an AT-SPI warning at startup, which had no visible effect. The “Unknown NN” labels and the ignored keystrokes may be specific to this environment; we did not check Windows or macOS.
- Released the same day we tested. Later 5.3.x builds may differ.
Sources and scope
Release URL and asset list: github.com/SubtitleEdit/subtitleedit/releases/tag/v5.3.0. Command log, screenshots of each step, input and output files, diffs, ffprobe output and SHA-256 hashes are kept in ToolBrivio's evidence archive for this review (subtitle-edit, October 14, 2026). We earn no commission from these links.