For embedded captions, open your stream in YouTube Studio’s Live Control Room, go to Settings > Setup > Closed captions, select Embedded 608/708, and save. Your encoder must also send compatible EIA-608/CEA-708 caption data; selecting the Live Control Room option alone does not create captions.
You can also use supported software to send captions to YouTube through HTTP POSTs. YouTube’s instructions describe live-event workflows, not a special 24/7 caption mode, so test the route you choose at the start, during operation and around planned boundaries or restarts.
Choose a caption path for the stream
There are two documented routes to consider: embed caption data in the video sent by your encoder, or send captions separately through supported software using HTTP POSTs. The first depends on the encoder and caption source carrying compatible data. The second depends on software that supports YouTube’s workflow and on handling its ingestion URL and delay requirements. Neither route is activated simply by choosing a setting in the Control Room.
| Path | How captions reach YouTube | Check before choosing |
|---|---|---|
| Embedded 608/708 | The encoder carries caption data inside the video stream | Whether your encoder can send EIA-608/CEA-708, where the text comes from, and whether viewers can see it |
| HTTP POST | Supported software sends captions to a Captions Ingestion URL | Whether the software supports YouTube’s workflow, how the URL is handled, and the required broadcast delay |
Choose embedded captions if your existing production chain can generate and carry the required data reliably. This may suit a setup in which captions are already produced as part of an encoder workflow. Do not assume that a file containing subtitles will be sent as live captions just because it is available to the encoder: confirm how the encoder reads or encodes the caption data and that it includes it in the outgoing stream.
The HTTP route may suit you when supported captioning software sends text separately rather than embedding it in the video. YouTube’s event instructions include a 30- or 60-second broadcast delay for this method. That changes the timing viewers experience, so consider whether delayed captions fit your content, particularly for news, announcements or a live devotional programme with spoken introductions. Check the current instructions and software support before you build around this path.
YouTube says the 608/708 standard can support up to four language tracks, while YouTube currently supports one caption track for this embedded workflow. If you need multiple languages, do not infer that the standard’s capacity means the platform will display multiple tracks here. Check YouTube’s current guidance and choose a workflow that matches what viewers will actually be able to select. The YouTube Live access checklist covers a separate prerequisite: confirming that your channel can use live streaming. Access and captions are different questions, but both are worth checking before a long-running launch.
Open Closed captions in Live Control Room
In YouTube Studio, create or open the encoder stream you intend to use, then enter its Live Control Room. Open the stream’s Settings, select the Setup tab and find Closed captions. The precise interface can change, so use YouTube’s current labels if they differ from the path described here.
This is a setting for the stream configuration, not a caption generator. Think of the Control Room selection as telling YouTube which incoming caption path to expect. If no captions are being sent, choosing an embedded option cannot turn dialogue or lyrics into text. YouTube’s guidance is direct: captions must be sent to YouTube for a live stream to have them.
Before changing the setting on a channel’s main broadcast, make sure you know which stream configuration and encoder output you are working with. If you operate multiple programmes or rotate between a test stream and a public stream, confirm that the setting belongs to the intended stream. A useful habit is to write down the chosen route alongside the encoder profile and the person responsible for checking it. That is especially helpful when a volunteer or colleague takes over a channel after you have prepared it.
YouTube’s live caption requirements explain the documented embedded and HTTP approaches. Refer to that page while configuring rather than relying on an old screenshot or a third-party tutorial whose interface may have changed.
Select Embedded 608/708 and save
For the embedded route, select Embedded 608/708 in the Closed captions section and save the change. Then configure the encoder to output compatible EIA-608/CEA-708 captions. Both ends of the connection matter: YouTube needs the matching selection, and the encoder needs to send the caption data in the format expected by that selection.
After saving, check that the choice remains selected when you reopen the stream’s settings. This is a simple configuration check, not proof that captions are reaching the stream. Confirm the encoder profile separately, then verify the actual caption display in the preview or with a viewer test. A status indicator or saved setting can show that a choice was made without showing that the incoming text is present and readable.
If the encoder offers a choice labelled “embedded”, inspect its documentation to establish that it means EIA-608/CEA-708 output for the YouTube workflow. Similar labels can refer to different functions in different products. YouTube does not endorse a particular encoder in the cited instructions, so confirm standards support with the encoder maker rather than treating a model name or a generic caption option as evidence.
The selection is a routing choice, not a promise of continuity. A stream that works in a brief test may still need checking after a profile change, a reconnect or a new live session. YouTube’s live-event instructions do not establish that captions will persist through every restart in a 24/7 operation. Treat the setting as one part of a setup to verify at the moments when your broadcast changes state.
Configure the encoder to send EIA-608/CEA-708
In the encoder, find the caption setting that enables EIA-608/CEA-708 output, sometimes described as embedded captions. The option must be configured in the profile actually used to send the live stream. If you prepare a profile on one computer and run a different encoder or profile overnight, check that the running setup has the same caption source and output behaviour.
Caption text needs a source. Depending on your workflow, an encoder may read caption data from a file format or encode it in real time. Confirm what your specific encoder supports, where the text comes from, and whether the output includes that data while the video is sent. A subtitle file sitting next to a looping video does not by itself prove that the live encoder is transmitting captions in the required format.
Make a short test with representative content. For a bhajan channel, this might include a spoken introduction and a section with lyrics; for a local news loop, include a presenter’s voice and a change between clips. Check that captions appear at sensible times, are legible and correspond to the audio. This will help distinguish a missing caption source from a mismatch between encoder output and the Control Room selection.
If the test fails, check the chain one step at a time: confirm captions are being generated or read, confirm the active encoder profile is sending EIA-608/CEA-708, confirm the correct stream is open in the Control Room, and confirm Embedded 608/708 is saved. Do not change several things at once and then assume the final result reveals which part was wrong. Record the working profile and its caption source so you can restore them after routine changes.
The guide to looping a recorded video on YouTube Live in OBS may help if your stream uses a repeated video, but looping video and embedding live captions are distinct jobs. A loop can repeat the pictures and audio while the caption data is absent, mistimed or not carried at all. Test the complete output rather than assuming that a successful video loop proves the caption path works.
Consider the supported HTTP POST path
If you are not using embedded captions, YouTube documents a route in which supported software sends captions through HTTP POSTs. The workflow uses a Captions Ingestion URL. YouTube’s event instructions say to add a 30- or 60-second broadcast delay in Advanced settings, turn on Closed captions and copy the captions ingestion URL. Follow the current instructions in the Control Room; verify the labels and requirements before going live, as interfaces and supported software can change.
Treat the ingestion URL as a configuration value that needs careful handling. Copy it into the supported captioning software as instructed and keep it available to the people who maintain the broadcast. Avoid pasting it into public notes or sending it in a channel announcement. If you replace the caption software, change the stream setup or hand operations to another person, check that the destination and the Control Room configuration still match.
The broadcast delay is a real trade-off, not a detail to skip. It gives the caption workflow time to send text, but viewers will see the stream later than its source. For a looping music or ambience station, that may be acceptable; for time-sensitive news or a live announcement, consider what the delay means to your audience. Do not remove it simply because a test appears to work without it: use the current YouTube instructions for the selected method.
YouTube’s live stream setup guidance is useful for the surrounding broadcast configuration, while the caption requirements page describes the caption path. Confirm that the software you intend to use is supported for this workflow. Research does not establish a particular service or product as compatible, so check with its provider and test before relying on it.
Test captions during operation and restarts
A 24/7 channel needs a test plan that reflects more than the first few minutes. The caption documentation is written for live events and does not define a separate uninterrupted-stream procedure. Check captions at the stream’s start, during ordinary operation and around any planned boundary or restart. If your operation creates successive live sessions rather than keeping one session open, verify the new session as its own state.
At the start, inspect the Live Control Room preview and, where practical, view the stream as an audience member who can turn captions on. Confirm that the text appears, can be enabled and matches the programme. During operation, check again after the content changes or at a routine point in your monitoring schedule. A caption stream that worked for the opening clip may fail later if the source changes or the encoder profile is replaced.
Around a restart, reconnect or stream boundary, check both the Control Room setting and the outgoing caption data. Do not assume a caption track will recover automatically just because the video returns. YouTube does not promise in the cited instructions that captions persist across every encoder restart, so your procedure should include a human or automated check appropriate to your setup. If the broadcast is managed by a small team, write down who checks and how they report a failure.
For a failure, note what viewers could see and when it began, then inspect the caption source, encoder output and selected YouTube path. For HTTP captions, include the software connection and ingestion destination in your checks. Restore the known working configuration, verify captions in the live output, and then document the cause if you identify it. A visible picture and audible sound do not demonstrate that caption data is being transmitted.
Keep archive expectations separate from live caption checks. YouTube’s encoder guidance says streams under 12 hours are automatically archived; that statement does not establish that an uninterrupted 24-hour broadcast will produce one complete archive. If you need a record of captions or a complete programme archive, check current platform guidance and plan for the particular way your stream is divided or recorded. See the guide to keeping a looping live stream running without a gap for a related operational concern: continuity of the programme is not the same as continuity of captions.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does selecting Embedded 608/708 create captions?
No. It selects the path YouTube expects, but the encoder must send compatible EIA-608/CEA-708 caption data. Check that captions are being generated or read and carried in the outgoing stream, then verify them in the live output.
Can I use HTTP POST captions instead?
YouTube documents a supported-software workflow that sends captions to a Captions Ingestion URL. Its live-event instructions include a 30- or 60-second broadcast delay, so check the current YouTube procedure and software support before using it.
Will captions continue through every restart?
The cited instructions do not promise caption continuity across every encoder restart or establish a special 24/7 caption mode. Test at the start, during operation and around restarts or new session boundaries, and include caption checks in your recovery routine.
How many embedded caption tracks can viewers use?
YouTube says the 608/708 standard can support up to four language tracks, but YouTube currently supports one caption track for this embedded workflow. Check the current official guidance if language-track support is important to your channel.