Skip to main content

Why Your SDH Subtitles Are Probably Getting Rejected

SDH files carry sound descriptions and speaker tags that plenty of delivery destinations don't want. Here's how to strip them cleanly, in bulk, without breaking timing.

If you’ve ever had a delivery bounced back over subtitles, there’s a good chance the issue wasn’t the dialogue — it was everything around the dialogue.

SDH (Subtitles for the Deaf and Hard of Hearing) files are built to include sound descriptions — [door slams], [tense music playing], speaker tags like JOHN:, and bracketed cues for things a hearing viewer wouldn’t need spelled out. That’s exactly what SDH is supposed to do. The problem is that not every delivery destination wants SDH. Plenty of platforms and broadcasters want a clean, standard subtitle track — dialogue only, no sound description, no speaker labels — and if you send them an SDH file when they wanted a plain one, it’s a rejection, not a warning.

The manual fix is miserable. You’re opening an SRT or VTT file, hunting for every [bracketed cue], every SPEAKER: prefix, every italicized lyric line, and deleting them one at a time without breaking the timing underneath. On a single episode that’s tedious. On a season, or a back-catalogue delivery of forty titles, it’s a genuine bottleneck — and it’s exactly the kind of repetitive, error-prone task that shouldn’t need a person doing it by hand.

What the SDH Remover actually does

Drop in an SRT or VTT file and it strips sound descriptions, speaker tags, and music notes automatically, with a few things configurable rather than hard-coded:

  • Choose which cue wrapper format to strip (brackets, parentheses, or both)
  • Set your own speaker tag pattern, since not every source formats them the same way
  • Optionally keep lyric lines in italics rather than deleting them outright
  • Bulk process a folder’s worth of files at once, exported as a ZIP with a per-file report so you can see exactly what was removed from each one

That last part matters more than it sounds like it should. When you’re delivering to spec, “trust me, it’s clean” isn’t good enough — having a report per file means you can actually show your QC team, or the platform, what changed.

Where this fits in a real delivery workflow

This tool solves the “I have SDH, I need plain subtitles” problem. It doesn’t replace full caption QC — timing drift, reading speed, line length, and positioning still need proper review, especially if you’re delivering against a specific platform’s caption spec. That’s the kind of thing we handle as part of full Captions & Subtitling services, where SDH conversion is one step in a broader compliance pass rather than the whole job.

But if you just need a clean pass on a handful of files before a delivery deadline, it’s free, it runs entirely in your browser, and nothing gets uploaded anywhere.

Try the SDH Remover →


All FooEngine tools run locally in your browser. No files are uploaded to any server.