CaptionPass
ProductConvertLearnPricingComplianceEnterpriseDocs
Sign inCreate accountDashboardConvert & fix free
CaptionPass

Professional caption delivery QA for editors and producers.

Product

  • Free caption converter
  • Fix captions
  • Pricing
  • What is CaptionPass?
  • API
  • Sign in
  • Dashboard
  • Compliance
  • Accessibility
  • Enterprise
  • Verify a receipt
  • About
  • Changelog

Learn

  • SRT vs VTT
  • YouTube caption upload issues
  • Why your captions are not showing
  • Fix overlapping subtitles
  • Educators
  • All guides →

Legal

  • info@captionpass.com
  • Privacy
  • Terms

© 2026 CaptionPass. Caption reliability layer for delivery.CaptionPass is in early access — features and limits may change. Spotted something off? Use Send feedback above.

Home/Learn/FCC caption quality standards

Last updated August 28, 2026 (UTC)

The FCC's four caption quality standards

The FCC has held captions to four quality standards since 2014. They are the clearest published articulation of what “good captions” means, which is why they get cited far outside the broadcast context they bind — and why it matters to be exact about which of them any given tool can actually decide.

Below, each standard is marked with how much of it a caption file alone can settle. Those marks are read from the engine rather than written by hand, so the page cannot claim more than the product does.

See a real conformance receipt — generated through the production engine on every page load, no account needed.

Verify a receipt you were sent — including one we hold no copy of.

What CaptionPass does about compliance — for a reader who arrived here having never heard of it.

The four standards

FCC caption quality standards and what a caption file can settle
CriterionWhat it requiresWhat a caption file can settle
79.1(j)(2)(i)AccuracyCaptioning shall match the spoken words in their original language, and convey background noises and other sounds, to the greatest extent possible.Not evaluatedNothing in a caption file can settle this. It is reported as not evaluated and is never marked passed.Deciding whether the words are right means comparing them to the audio. This engine never sees the audio and will not assert accuracy from the text alone.
79.1(j)(2)(ii)SynchronicityCaptioning shall coincide with the corresponding spoken words and sounds, and be displayed at a speed that can be read by viewers.Partly checkedThe file can show this failing, but cannot show it passing. No findings means nothing detectable is wrong — not that the criterion is met.Readable speed is fully decidable from the file. Coinciding with the spoken word is not — that half needs the audio.
79.1(j)(2)(iii)CompletenessCaptioning shall run from the beginning to the end of the programme, to the fullest extent possible.Partly checkedThe file can show this failing, but cannot show it passing. No findings means nothing detectable is wrong — not that the criterion is met.Gaps and a late start are arithmetic. Whether a stretch with no captions was silence or dropped dialogue needs the audio, and coverage against programme length needs a known duration.
79.1(j)(2)(iv)PlacementCaptioning shall not block other important on-screen information, and shall not run off the edge of the video screen.Partly checkedThe file can show this failing, but cannot show it passing. No findings means nothing detectable is wrong — not that the criterion is met.Line count and dropped positioning are visible in the file. Whether a caption covers a lower third or a scoreboard needs the video.

Cited from 47 CFR 79.1(j)(2) — caption quality standards, adopted by FCC 14-12 (2014) — read the regulation. Applies to video programming distributed on US television, and — through 47 CFR 79.4 — clips of that programming redistributed online.

Why one of them can never be marked passed

Accuracy cannot be reached from a sidecar file at all. Deciding whether the words are right means comparing them to the audio, and this engine never sees the audio.

So it is reported as not evaluated on every receipt issued, permanently, by design. That is a scope boundary rather than a gap waiting to be filled — and any tool that certifies caption accuracy without listening to the audio is overstating what it did.

Does this apply to your video?

79.1 binds video programming distributed on US television, and through 47 CFR 79.4 the clips of that programming redistributed online. A university, agency or business publishing original video to its own site is generally looking at the ADA and WCAG instead — see evidencing ADA Title II captions and checking captions against WCAG 2.1 AA.

The four standards remain a useful vocabulary either way. “Synchronicity” is a more precise thing to ask a vendor for than “good timing”, and reading speed is the half of it you can settle from the file you were sent.

What this is not. A conformance receipt is evidence of what was checked, by which engine, against which version of which standard, and what it found. It is not a legal opinion, an audit, or a safe harbour. CaptionPass reads the caption file and never the audio, so anything that needs the audio — above all whether the captions match what was said — is reported as not evaluated rather than assumed.

Common questions

What are the FCC's four caption quality standards?
accuracy, synchronicity, completeness, placement — set out at 47 CFR 79.1(j)(2) — caption quality standards, adopted by FCC 14-12 (2014). They apply to video programming distributed on US television, and — through 47 CFR 79.4 — clips of that programming redistributed online.
Which of them can be checked from a caption file?
Accuracy: not evaluated. Deciding whether the words are right means comparing them to the audio. This engine never sees the audio and will not assert accuracy from the text alone. Synchronicity: partly checked. Readable speed is fully decidable from the file. Coinciding with the spoken word is not — that half needs the audio. Completeness: partly checked. Gaps and a late start are arithmetic. Whether a stretch with no captions was silence or dropped dialogue needs the audio, and coverage against programme length needs a known duration. Placement: partly checked. Line count and dropped positioning are visible in the file. Whether a caption covers a lower third or a scoreboard needs the video.
Do the FCC standards apply to online video?
They apply to video programming distributed on US television, and — through 47 CFR 79.4 — clips of that programming redistributed online. A university or business publishing original video to its own site is generally looking at the ADA and WCAG rather than at 79.1, though the four standards remain a useful vocabulary for what "good captions" means.
Why is accuracy never marked as passing?
Accuracy cannot be settled from a caption file, because that comparison needs the audio. Reporting it as not evaluated is a deliberate scope boundary rather than a gap waiting to be filled.

Convert your captions free

Upload on CaptionPass, pick a delivery preset, and download upload-ready output with optional enhanced formatting — free tier, no account required.

Convert & fix free →

More guides

  • Free online caption converter — SRT, VTT, and delivery QAHow CaptionPass works as a free caption converter with upload-ready and enhanced exports, platform presets, and explainable fixes. Try the same presets on the homepage tool or Quick fix before you open a Pro project.
  • SRT to VTT converter guide — headers, timestamps, and pitfallsWhen to convert SRT to WebVTT, what breaks if you rename extensions, and how to validate before HTML5 or YouTube delivery. CaptionPass converts and validates both formats in the dashboard workbench and v1 API.
  • SRT vs VTT — when each format silently failsComma vs dot timestamps, WEBVTT headers, and where YouTube, TikTok, and HTML5 bite. Run either format through the homepage tool or POST /api/v1/process to see explainable fixes before delivery.
  • Caption file encoding — UTF-8, BOM, and garbled textWhy uploads show mojibake or blank cues: UTF-8 vs legacy encodings and quick fixes. CaptionPass ingest reports flag encoding issues in the workbench Checks tab and v1 processing errors.
  • Burned-in vs soft subtitles — what to deliver whenOpen captions burned into the picture vs separate SRT/VTT tracks — tradeoffs for editors and clients. Pro users can mux or burn-in via v1 render jobs after sidecar QA in the workbench.
  • Reading speed for captions — CPS, line length, and platformsCharacters per second, lines per cue, and where YouTube, TikTok, and HTML5 push back. Platform presets in the dashboard and v1 API apply the same CPS and line-length rules automatically.
  • YouTube caption upload issues — silent rejection and timingWhen Studio accepts a file but captions vanish: format, line length, drift, and how to validate before publish. Export with the YouTube preset from Deliver or v1 before you upload to Studio.
  • YouTube rejected my SRT — invalid file and Studio errorsWhen YouTube Studio blocks an SRT upload: encoding, index gaps, bad timestamps, and how to validate before you retry. Quick fix and the homepage tool surface the same diagnostics as a failed v1 run.
  • Caption timing drift after export from Premiere or DaVinciWhy captions slip after NLE export: frame rates, timecode starts, and how to normalize before YouTube or client delivery. Pro drift diff in the workbench compares revisions after you re-import from an NLE.
  • CaptionPass vs generic subtitle convertersFormat swap tools vs delivery QA: explainable fixes, platform presets, and when each approach fits your workflow. CaptionPass adds Checks, receipts, and handoff packs on top of one-shot homepage conversions.
  • CaptionPass vs Subtitle EditDesktop authoring vs delivery QA: when to use Subtitle Edit for editing and CaptionPass for platform-safe validation and API automation. Ship Subtitle Edit exports through the dashboard workbench or v1 API for final QA.
  • Caption QA API for CI/CD pipelinesAutomate SRT and VTT validation in GitHub Actions or your build pipeline with POST /api/v1/process and Bearer API keys. Keys and usage meters live under dashboard Automate alongside export webhooks.
  • TikTok subtitle format — short lines, CPS, and clean SRTVertical video reading speed, styling stripped on upload, and export settings that survive TikTok delivery. Use the social-shorts handoff profile or TikTok preset from Deliver before upload.
  • Why your captions are not showing — a triage guideHTML5, YouTube, and TikTok checks when subtitles vanish after upload. Cross-check workbench preflight and History receipts to confirm what CaptionPass actually exported.
  • Fix overlapping subtitlesWhat overlap means and why some players drop overlapping cues. CaptionPass flags overlapping_cues in Checks and can auto-fix via Fix again or v1 process.
  • TTML and DFXP — broadcast-style timed text on the webNamespaces, timing, styling stripped in practice, and when TTML is the right interchange vs SRT or WebVTT. Convert inbound TTML through v1 or the homepage tool when clients deliver broadcast sidecars.
  • CaptionPass JSON IR and the developer-json presetLossless-ish cue interchange for tooling: when to use JSON IR, version tag, and how it pairs with the HTTP API. Request the developer-json preset from POST /api/v1/process or export it from the workbench.
  • Timecode, frame rate, and caption syncWhy captions drift or jump: drop-frame vs non-drop, fractional frame rates, and export settings that survive upload. Pro drift panel and v1 diff help confirm sync after re-export from an NLE.
  • WCAG-minded captions — reading speed, sound tags, and burned-in contrastHow WCAG 1.2.x thinking maps to real files: CPS, line length, SDH-style cues, and contrast for open captions. Platform presets in the dashboard enforce readable CPS before you hand off to clients.
  • Educators & classrooms — CaptionPass for instructionPartner program for instructors: API keys, workspace pilots, Learn guides, and classroom-appropriate access. Students can start with the free homepage tool before moving to dashboard projects.
  • How to evidence ADA Title II captionsWhat the DOJ web rule requires for captions, what counts as evidence rather than an assurance, and what a per-asset conformance record contains. Deadlines are dated and cited, and the tense is computed so the page cannot describe a passed deadline as upcoming.
  • What goes in the caption rows of a VPATWhich WCAG criteria are the caption rows of an Accessibility Conformance Report, which conformance level each evidence outcome actually supports, and why Not Evaluated beats an unjustified Not Applicable.
  • How to check captions against WCAG 2.1 AAWhich WCAG success criteria a caption file bears on, how to run a per-criterion check that names its own limits, and what a clean result does and does not establish.

Fix in CaptionPass

Free caption converter · Homepage tool · HTTP API (v1) · Pro workspace