Why does "I sent the SRT" still fail when stakeholders only double-click an MP4?
Sidecars require co-located files, correct MIME handling, and user toggles—any missing link means silent failure. Hard-burning is the pragmatic answer for training decks, compliance clips, and after-sales walkthroughs that must read like printed instructions. Teams google hardcode subtitles to mp4, burn srt online no install, enterprise email video captions, and vlc subtitles not showing because responsibility shifts to a single artifact. ASS shadows differ slightly across libass builds, so golden-device checks still matter. VTT cue settings left dirty can confuse parsers; sanitize before mux. Bilingual stacks get unreadable on phones—consider separate language SKUs instead of stacking everything once. Licensing for burn-in may differ from sidecar distribution—verify the contract table. This variant stresses UTF-8 hygiene, pilot burns, muted previews on weak devices, then batch derivatives with checksum manifests.
SRT burn variant: shortest path from fragile sidecar to single forwarded file
- Switch to subtitle-file mode, validate UTF-8 without BOM, and pick the language track you actually intend to bake to avoid overlapping cues.
- Upload the final video plus the subtitle file, skim first and last cues against total duration, and watch for leader black where early cues would be invisible.
- Export and confirm captions remain visible with the player subtitle toggle off; store MP4 plus original SRT in version control with a burn revision tag.