FCC caption display settings, August 2026: burned-in captions
The FCC's caption display settings rule had an August 17, 2026 compliance date. Burned-in captions are pixels in the video; how to add them with Sume's API.

Does the FCC caption display settings rule apply to burned-in captions? The rule, as the FCC's page and secondary summaries in the search results (read 2026-10-04) describe it, requires manufacturers of covered apparatus and multichannel video programming distributors to make closed captioning display settings readily accessible. Compliance with that requirement was due by August 17, 2026. It is about the settings a viewer can change for closed captions on devices such as TVs, set-top boxes, computers, phones and tablets.
Burned-in captions, also called open captions, are part of the picture. A viewer's caption settings do not restyle them, because they are pixels in the video. That makes them predictable, and it is why teams use them for social video. I am not giving legal advice, and whether a particular product is covered is a question for counsel.
What the FCC page says
Start with the FCC's announcement of the effective date. The summaries I read named four factors the FCC will use to judge readily accessible: proximity, discoverability, previewability, and consistency and persistence. I did not verify the full rule text, so read it before you rely on any detail.
Burned-in vs closed, in one table
| Question | Closed captions | Burned-in with Sume |
|---|---|---|
| Where the text lives | A separate caption track | In the video pixels |
| Viewer can restyle | Yes, through device settings | No |
| Styles | Set by the viewer's device | slam, punch, tiktok-green, korean-ad, Hangul identities |
| Cost per job | Not applicable | $0.20 for videos up to 60 seconds, confirm in GET /v1/catalog |
Burn captions with one call
POST /v1/video-captions takes a public HTTPS video_url and returns a job-backed captioned video. Without script_text, speech-to-text supplies the words. A silent clip fails as caption_no_speech, and the docs point to cues for authored overlay copy.
curl -X POST https://api.sume.com/v1/video-captions \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: fcc-burned-in-001" \
-d '{"video_url":"https://media.sume.com/artifacts/example/clean.mp4","style":"black-outline"}'What to decide first
If your video goes to broadcast or a regulated distributor, ask them which caption format they require, since they may need a separate caption track, which this endpoint does not produce. If it is social video, burned-in captions are the usual choice.
Sources
Related posts
More in Developers
- Fit narration to a fixed slot: measure first, then set TTS speed
A 45-second cap or a 30-second slot decides your script. Render once with word timings, compute the speed ratio, and rewrite only if outside 0.6 to 1.5.
- format_not_forkable 409 in the Sume API: what it means and the fix
Sume returns 409 format_not_forkable when the id you called names a built-in capability, not a Format card. How to tell, and which ids to call instead.
- Gemini 3.8 Live audio: wrap 24 kHz PCM in WAV, resample to 16 kHz
Gemini 3.8 Live takes 16-bit 16 kHz PCM in and returns 24 kHz out. A Python WAV wrapper, an ffmpeg resample command, and the Sume detach settings that match.
- Gemini video understanding 88% fewer tokens vs Sume Video inspect
Gemini reports up to 88% fewer tokens on long video. Sume Video inspect and Reference ingest take another route: stills, transcript and a manifest.
Written by Sume