Subtitle Localization QC

How to use Subtitle Localization QC

A translated subtitle file needs mechanical checks as well as language review. Compare real SRT cue structures and explicit delivery limits before reviewing the localized video in playback.

1. Paste actual source and translated SRT excerpts with standard sequence and timestamp lines.
2. Set the client reading-speed and line-length policy; inspect missing cues, overlaps and timing drift.
3. Resolve mechanical findings and complete bilingual meaning, accessibility and actual video playback review.

Good to know

• At most 100 cues per input and 8,000 UTF-16 characters per field. This strict profile accepts HH:MM:SS,mmm --> HH:MM:SS,mmm with no extra cue settings; invalid times or duplicate sequence IDs are refused.
• Spaces and inert formatting tags count as literal Unicode code points; line endings do not. This is an explicit counting convention, not a universal captioning standard or grapheme measure.
• The tool does not translate, inspect audio or certify meaning/accessibility. Missing sequence matches are not invented, and repeating decimal speeds are marked with an ellipsis.
• Each field is limited to 8,000 UTF-16 characters; CSV inputs use the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Empty/duplicate identities, unsupported controls and unpaired surrogates are refused.
• Exports are editable review records. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; inspect your actual spreadsheet/import settings before sharing.
• Everything runs locally in your browser. No AI model, upload, provider account, calendar, call, video render, automatic outreach, publication or saved input. Enter only information you are authorized to process; declarations remain unverified.