01
Audit the file
Open an SRT or WebVTT file and see exact blockers, review items, clean cues, and the next repair in one local audit.
Local subtitle delivery QA
SRT / WebVTT · iPhone and iPad
Caption QA Local
Find overlaps, reading-speed issues, timing errors, and line-layout blockers before a subtitle file reaches delivery.
Paid upfront · No subscription · No ads · No cloud processing
A delivery-focused workflow
One subtitle file. One clear repair queue. One checked handoff.
02
Repair the cue
Edit cue text and timecodes while checking duration and reading speed before the file leaves your device.
03
Deliver proof
Export a checked SRT or WebVTT file with PDF, CSV, and Markdown QA reports for a concrete handoff.
Real app screens
The result stays inspectable.
Every image below comes from the working app with a fictional example subtitle project. No private user files or generated UI mockups are used.
Blocker-first audit
Readiness, affected cues, and the next repair stay visible.
Cue repair workspace
Adjust text and timing with the relevant quality context nearby.
Checked-file handoff
Create subtitle files and practical QA reports from the reviewed project.
Inspect the real output
Open the files before you buy.
These four files were generated by the same exporter used in the app from the fictional Harbor Signal Trailer project. They contain no customer or developer data.
PDFVisual QA reportA readable delivery summary with score, blockers, and repair guidance.34 KBDownloadCSVFinding-by-finding auditStructured severity, cue, issue, detail, and fix columns for handoff.1.0 KBDownloadMDMarkdown QA reportA portable review record for tickets, repositories, and production notes.1.3 KBDownloadSRTChecked subtitle fileThe exported subtitle file used alongside the audit reports.619 BDownload
Fictional production sample. Findings are practical review aids, not a certification of platform or accessibility compliance.
Local by design
Subtitle content stays on your device.
There is no account, analytics SDK, advertising SDK, cloud sync, transcription service, or AI processing backend. You choose the input file and every export destination.
Read the privacy policyQuestions before delivery
Caption QA Local FAQ
What subtitle files does Caption QA Local check?
Caption QA Local imports SRT and WebVTT subtitle files. It can also export a checked SRT or WebVTT file after review and repair.
Does Caption QA Local upload subtitle files?
No. Subtitle text, timing, edits, findings, and saved projects remain on the device unless the user deliberately exports a file through Apple's share sheet.
Which subtitle issues can it find?
The local audit checks overlapping or invalid timing, empty text, reading speed, line length, line count, short or long duration, tight gaps, and duplicate text using adjustable rules.
What can I export after a subtitle QA pass?
The app can create a checked SRT or WebVTT file plus PDF, CSV, and Markdown QA reports for review records and delivery handoff.
Can I inspect a real Caption QA Local export before launch?
Yes. This page includes a downloadable SRT file and the matching PDF, CSV, and Markdown reports generated by the app's exporter from a fictional subtitle project.
Does the app require a subscription, account, ads, or AI service?
No. Caption QA Local is designed as a paid-upfront local utility with no subscription, account, advertising, transcription service, or cloud AI processing.
Does a clean result certify accessibility compliance?
No. Findings are practical review aids based on adjustable rules. They do not certify every broadcaster, platform, language, or accessibility standard.
Caption QA Local
Planned App Store price: US$3.99, paid upfront.