Before you start: reuse one checked caption file
Captioning twice wastes time. Make one accurate caption file for each video and use it everywhere the video goes. If the video already lives on your YouTube channel with checked captions, you can download that file from YouTube Studio as an SRT and upload it to Facebook. If it doesn't, fix the captions on YouTube first. Our guide on how to add captions to YouTube videos walks through that part.
An SRT file is plain text: a number, a start and end time, and the caption lines. If you have never opened one, read SRT File Format: A Line-by-Line Guide before you edit one by hand.
Why not just rely on automatic captions? In 2022, a Consumer Reports study reported by UC Today tested auto-captions on seven platforms, including Facebook and YouTube. Some were getting around one in 10 words wrong, and results were worse for non-native English speakers. That study gave no Facebook-only error rate, but the lesson holds: a human has to check the text.
Uploading an SRT file to a Facebook Page video
Meta changes its menus often, so the labels on your screen may differ a little. The order of the work stays the same.
- 1
Name the file first
Rename your SRT so it carries a language and region code before .srt. For example, board-meeting.en_US.srt for English. See the filename section below.
- 2
Start the post from a desktop browser
Open Meta Business Suite for your Page and create a new post or reel with your video. Caption options have been more complete on desktop than in the mobile app.
- 3
Find the captions or subtitles setting
Look in the video's settings for captions or subtitles. Choose the option to upload a file rather than auto-generate.
- 4
Upload the SRT and pick the language
Select your file and confirm the language matches the file. If the upload fails, check the filename and that the file is saved as plain text.
- 5
Preview before you publish
Play the start, a middle section and the end. Make sure the captions line up with speech and nothing is cut off.
- 6
Add a second language if you have one
Upload a Spanish SRT the same way, with its own language code in the filename.
The filename rule: language and region codes
Facebook reads the language from the filename, so a file called captions.srt can be rejected or tagged wrong. Use the pattern name.language_REGION.srt, such as video.en_US.srt for US English. For Spanish, check Meta's current help page for the Spanish code it lists and use that exact code, then confirm the language shown after upload says Spanish. Keep the same base name for both files so your team can tell which video they belong to. If you post a lot of Spanish video, see Spanish captions for school and health center video.
No caption file? Edit Facebook's auto-captions
Sometimes you only have the raw video and no time to make an SRT. Facebook can generate captions for you, but treat them as a first draft.
Illinois State University's accessibility guide, last updated in 2022, describes the flow for Page videos uploaded from a desktop browser: you auto-generate the captions, open the Captions Editor with the pencil icon, make your edits, and save a draft. It tells staff to check captions before publishing, especially the spelling of names and places, and notes the feature was not available for mobile uploads at the time. Menu names may have changed since, so follow the same idea on your current screen.
What to check before you publish
- Speaker names. When a new person speaks and it isn't obvious on screen, add their name or role, such as "Board President:".
- Names and terms. Staff names, school names, street names, drug names and doses. Auto-captions often miss these.
- Sound cues. Add short tags like [applause], [music] or [bell rings] when the sound matters.
- Timing. Captions should appear with the speech, not seconds before or after.
- Numbers and dates. Check every time, date, phone number and dose against the script or slides.
- Nothing missing. Scan for gaps where a speaker talked but no caption shows.
For more on what counts as accurate, see caption quality standards.
Reels and Facebook Live
Reels
As of RNID's June 2026 update, Facebook's automated captions did not work on Facebook Reels. So add captions another way: use the caption tools in the Reels editor, or export the clip with captions burned into the picture. Check this against your own app version, since it may change.
Burned-in (open) captions work everywhere, but they have limits. Viewers can't turn them off or resize them, you can't fix a typo without re-exporting, and they can collide with text Facebook lays over the bottom of the screen. Keep them high enough, large enough and high contrast. Closed captions vs open captions covers the trade-offs.
Facebook Live
WCAG 2.1 success criterion 1.2.4 (Level AA) asks for captions on live audio. Automatic live captions on their own usually fall short of that, so for board meetings and other key events, plan for a human captioner feeding captions into your streaming setup. Once the stream ends, the replay is recorded video and needs accurate captions like any other upload. Upload a checked SRT to the replay. Our guide to livestream captions covers both halves.
Audio description on Facebook: link a described version
Captions cover what people say. Audio description covers what the picture shows that the soundtrack doesn't, such as a slide with a phone number that no one reads aloud. WCAG 1.2.5 asks for it in recorded video when that gap exists. Our guide on when audio description is required explains how to tell, and the check below can help.
Facebook's caption tools handle text, not a second narration track. The practical fix is to publish a described version of the video, for example on your YouTube channel, and link to it in the Facebook post. Better still, write the key visual information into the script so the main video needs less description.
Need audio description? Watch the version with audio description here: [link]. To request an accessible version of any of our videos, contact [name] at [email or phone].
Do Facebook posts fall under the rules?
The DOJ's ADA Title II rule and the HHS Section 504 rule both adopt WCAG 2.1 AA, with these compliance dates as extended in 2026. Check yours with the deadline checker.
| Rule | Who | Compliance date |
|---|---|---|
| ADA Title II | Public entities of 50,000 people or more | April 26, 2027 |
| ADA Title II | Smaller public entities and special districts | April 26, 2028 |
| Section 504 (HHS) | Recipients with 15 or more employees | May 11, 2027 |
| Section 504 (HHS) | Recipients with fewer than 15 employees | May 10, 2028 |
The DOJ's ada.gov fact sheet says social media posts a state or local government made before its compliance date do not need to meet WCAG 2.1 AA. Its example also shows that content posted after that date would probably have to meet the standard, and that includes captions for video. So treat every Facebook video you post after your date as needing real captions.
Two cautions. First, if a Facebook video is embedded on a current page of your website, the website rules apply to it. Second, if someone asks for an accessible version of any video, old or new, you need to provide one. Old video isn't treated as archived just for being old; see the archived content exception. This is general information, not legal advice.
A short Facebook caption checklist for your team
- Caption the YouTube copy first, then download and reuse that file.
- Name SRT files with a language and region code, such as video.en_US.srt.
- Upload from a desktop browser and preview the start, middle and end.
- If you use auto-captions, edit names, terms, numbers and speaker labels before publishing.
- Caption Reels in the editor or burn captions in, and check placement.
- For Live, plan live captions and upload a checked SRT to the replay.
- If the picture shows something the audio doesn't, link a described version.
- Add a line on how to request an accessible version.
Sources
- RNID
- Illinois State University
- U.S. Department of Justice, ADA.gov
- UC Today (reporting Consumer Reports study, 2022)
This is a reading of the rules, not legal advice. Something out of date? Tell us and we'll fix it.