Video Localization Version Auditor

How to use Video Localization Version Auditor

A source edit can invalidate a translated video even when every filename exists. Compare the current segment version with each declared language delivery before a localized release.

1. Assign stable segment IDs and update their version whenever source meaning, audio or timing changes.
2. List required languages and the source version each delivered asset actually used.
3. Resolve stale/missing/unapproved pairs and inspect final translated playback before release.

Good to know

• At most 500 required segment-language pairs. Duplicate and unexpected delivery records are retained as explicit findings rather than silently overwritten.
• This reconciles entered version declarations, not file contents, translation fidelity, lip sync, voice consent or publication rights.
• 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.