Developer RunbooksObsidian & Markdown100% Free & Open Source
Video Caption & Subtitle QA Release Checklist
Pre-flight quality assurance checklist for video subtitles: character encoding validation, reading speed limits, two-point synchronization, and player compatibility.
Designed For
Post-Production Supervisors, Video Producers, Localization Teams, and Creators
Companion OpenTools Utility
Writing & Text WorkbenchOpen Tool
What's Included in this Template
Character encoding verification (UTF-8 encoding with BOM handling)
Timing sync check across first and last dialogue marks (two-point verification)
Line length validation ensuring cues do not exceed ~42 characters
Reading speed ceiling check (verifying pace stays under ~21 characters/sec)
Minimum screen duration verification (at least 700 ms)
Access & Download Template
Live Preview & Code InspectorZero Server Uploads
# Video Caption & Subtitle QA Release Checklist
Use this pre-flight verification checklist before publishing video captions or uploading subtitle sidecars (.srt, .vtt) to hosting platforms.
---
## 📋 Phase 1: File Format & Encoding Integrity
- [ ] **Encoding Standard**: File is encoded in **UTF-8** (without unexpected Windows-1252 or Latin-1 byte corruption).
- [ ] **BOM Handling**: Byte Order Mark (BOM) is stripped or properly handled if targeting strict web players.
- [ ] **Sequential Indexing**: Cue numbers in .srt files increment strictly sequentially with no gaps or duplicates.
- [ ] **Timestamp Format**: Timestamps follow exact format specifications (e.g. `00:00:00,000` for SRT, `00:00:00.000` for WebVTT).
---
## ⏱️ Phase 2: Synchronization & Timing Accuracy
- [ ] **First Line Anchor**: First spoken dialogue event syncs within 100 ms of the spoken audio onset.
- [ ] **End-of-Video Anchor**: Final spoken cue lines up accurately with the end of dialogue (confirms zero frame-rate drift).
- [ ] **Minimum Cue Duration**: Every subtitle event displays for **at least 700 ms**.
- [ ] **Scene Cut Alignment**: Subtitles do not bleed across scene cuts for brief fractional frames.
---
## 👁️ Phase 3: Legibility & Reading Speed Compliance
- [ ] **Line Count Limit**: No subtitle cue exceeds **2 lines**.
- [ ] **Line Length Limit**: Lines do not exceed **about 42 characters** in width.
- [ ] **Reading Speed Ceiling**: Reading speed remains **under about 21 characters a second** across all cues.
- [ ] **Natural Break Structure**: Line breaks preserve prepositional phrases, verb phrases, and proper nouns.
---
## 🚀 Phase 4: Player Validation
- [ ] Rendered preview verified in target player (e.g. Web player, VLC, YouTube studio).
- [ ] Subtitles render legibly against both bright and dark background scenes.
Frequently Asked Questions (FAQ)
How do I check if my subtitle file has drifted before publishing?
Play the first 30 seconds of the video to check initial sync, then jump directly to the final 2 minutes. If the offset grew over the duration, the file requires two-point synchronization to fix a frame-rate mismatch.
Why should I check character encoding before releasing captions?
Subtitles authored on Windows often use Windows-1252 (CP1252). When played in modern web browsers expecting UTF-8, accented characters and typographic quotes render as broken symbols (mojibake).
More in Developer Runbooks
Obsidian & Markdown
Production Incident Response & Blameless Post-Mortem Runbook
DevOpsView
Obsidian & Markdown
Engineering Standard Operating Procedures (SOPs) Starter Kit
OperationsView
Obsidian & Markdown
Broadcast Captioning & Subtitle Style Guide
Creator PackView