I work on OnePassApps, so this is our own app and our own build, and every number below was measured in it today, signed out, in one browser, in the visible Chrome on display :1: Subtitle Workbench.
The Subtitle Workbench takes subtitle files you already have and tells you what is wrong with them before you export. Its own guide promises the check is about information: unsupported markup can block conversion, and converting positioning-bearing WebVTT to SRT is refused when it would lose information.
Here is what the app actually does, measured cue by cue: the markup gate is a WebVTT rule, not a markup rule. The same tags that stop a WebVTT file sail through an SRT file unchanged, all the way into the exported file.
The same tags, two formats
I pasted one SRT with three cues (198 B). Cue 1 carries a voice tag, cue 2 carries a bold tag and a colour tag, cue 3 is plain:
1
00:00:01,000 --> 00:00:03,000
<v Roger Bingham>Voice tagged line
2
00:00:04,000 --> 00:00:06,000
<b>Bold</b> and <font color="#ff0000">coloured</font>
3
00:00:07,000 --> 00:00:08,000
Plain line
The panel read 3 cues · 0:01–0:08, then 3 cues, then No issues. Export SRT was enabled, I pressed it, and the confirmation line read Downloaded SRT for pasted-1.srt. The file that landed on disk was 198 bytes - the same 198 bytes, with the markup byte for byte intact:
<v Roger Bingham>Voice tagged line
<b>Bold</b> and <font color="#ff0000">coloured</font>
No error, no warning, nothing stripped. The file list calls that source pasted-1.srt 3 cues · 198 B · OK.
Then the same tags in a WebVTT file (221 B) are refused, one message per problem:
Error: WebVTT NOTE blocks are unsupported. Export is blocked to preserve their meaning; download the original instead.
Error: Rich WebVTT markup (voice, class, ruby, or inline timestamps) is unsupported. Download the original to preserve it.
The header counted 3 cues · 221 B and 3 errors, and the panel added a line of its own: Resolve source errors before exporting. The original file is still available. The NOTE block gets its own sentence, separate from the rich-markup one, and the rich-markup sentence names four kinds by name - voice, class, ruby, or inline timestamps. The voice tag and the ruby tag each produced one of those errors.
The cue that produced no error at all
The positioned cue was the third case, and it was the interesting one, because it raised nothing. Its WebVTT cue carried line:85% align:center position:50%, and the app printed the cue and its positioning settings on a single line in the cue list: Positioned cue line:85% align:center position:50%. The file list read 2 cues · 133 B · OK and the cue count read No issues.
The guide's sentence about positioning is conditional - refused when it would lose information - and this cue produced no refusal and no error. With the export format set to SRT, the button read Export SRT and the confirmation was Downloaded SRT for pasted-2.vtt. I did not read that file's bytes, so I am not claiming what it contains. What I can say is what the panel did: it raised nothing, and it showed the positioning joined to the cue text.
Nothing left the tab
I captured every request the tab made at the browser's own network layer, before I typed anything. The only requests were GETs and OPTIONS to app.onepassapps.com, api.onepassapps.com and clerk.onepassapps.com - the app's own runtime and feature-flag reads - and there was no POST and no request body anywhere.
What I did not test
One build, one browser, one signed-out session, one day, 11 November 2026. I pasted subtitle text rather than using the file picker, so the 5 MB per file and 20 files per batch limits are the app's own wording and not something I measured against a file that size. I edited no cue by hand and left every timing repair alone - the shift field read +0 ms throughout. The rich-markup error names four kinds; I exercised voice and ruby, so class and inline timestamps are untested. The positioning cue is the one case I did not read the exported bytes for.
The earlier write-ups
The timing and repair layers of this same app are already covered: Subtitle Timing in the Browser: Shift Cues, Repair Overlaps and Export SRT or WebVTT and The Repair Order in the Browser Subtitle Editor: Four Checkboxes, One Sequence, and a Measured Shift. The reference-media path is covered by Attach a Video to the Subtitle Workbench: What Changes, and What the Export Still Gives You, and the guide's own limits wording is quoted in What Each OnePassApps App Says It Will Not Do: The Limits Section on All 22 Guides. The markup gate itself - which format gets checked, and what each format does with the same tags - is what this post is about. The guide for this app is where the limits are stated.
Top comments (0)