To keep today's class timetable visible on a continuous YouTube livestream, add it to the video scene in your encoder. Viewers then receive the timetable as part of the picture, alongside the lesson or other programme content.
Your YouTube title, description and scheduled start time remain separate metadata. They can explain the broadcast and help viewers find it, but they do not place a timetable over the video. The schedule must be designed as a graphic or display source and included in the outgoing stream.
Timetable graphic versus stream metadata
There are two different jobs here. The encoder composes the picture that YouTube receives. YouTube then publishes that picture with information such as the broadcast title, description, visibility setting and, where relevant, a scheduled start time.
A timetable graphic belongs to the first job. It might be a prepared image, a browser page, a presentation slide, or another display source. Once it is included in the encoder scene, it becomes part of the video output. If the scene is visible, viewers can see it whether they watch on a phone, television or computer.
Metadata belongs to the second job. A title such as “Monday Mathematics and Science Classes” can identify the stream, while the description can contain the full timetable as text. That text is useful for people who open the description, but it is not an on-screen timetable. A scheduled start time tells YouTube when a particular broadcast is intended to begin; it does not overlay class times on an already-running lesson feed.
For a school or coaching centre, this distinction affects the entire workflow. If the schedule must remain visible while a lesson plays, design it into the video before sending the composed output to YouTube. If viewers need reminders, a separate watch page or event-specific metadata may also be useful, but that is an additional arrangement rather than a replacement for the graphic.
You have three broad operating models:
| Model | Viewer destination | Useful when | Main trade-off |
|---|---|---|---|
| One continuous broadcast | One always-on channel URL | Classes run from a shared daily timetable | The schedule and programme need careful updating while the broadcast continues |
| Separate scheduled class streams | A different watch page for each class or event | Reminders, event-specific descriptions or separate archives matter | More broadcasts and more operator work |
| Continuous feed plus separate events | The general feed remains available while selected classes have their own broadcasts | A school wants continuity as well as distinct event destinations | The workflow is more complex and should be tested before use |
Google's YouTube Live Streaming API documentation gives the example of a channel with a 24/7 live feed that also creates a separate video for an interview. That describes how broadcasts and streams can relate; it does not mean every encoder provides a simple button for this arrangement.
Choose the model based on what viewers need to open, what must be archived, and who will maintain the schedule. Do not choose separate broadcasts merely because the timetable is being shown as a graphic. The graphic can work in a single continuous stream.
Prepare a timetable viewers can read
Start with the timetable itself, not the encoder. Write down the days, local time zone, class names and any information a viewer needs to understand the next programme. If the audience includes families or learners outside your area, label the time zone rather than assuming that everyone interprets the times locally.
A simple panel might contain:
- Monday to Friday
- IST
- 08:00 — Mathematics
- 09:00 — English
- 10:00 — Break
- 10:30 — Physics
- Next class: English at 09:00
You do not need to copy this layout. The point is to remove ambiguity. “Physics” is more useful than a code known only to staff, and “10:30 IST” is more useful than “10:30” when viewers may be joining from another region. If the schedule changes regularly, include a date or a label such as “Today's timetable” so an old image cannot be mistaken for the current one.
Keep the graphic stable. A timetable that changes position, flashes, or moves across the lesson may be technically visible but difficult to use. A fixed side panel or lower panel is usually easier to follow than several separate labels appearing at different times. Leave enough room for the teaching content, especially if the lesson includes slides, a teacher's face, handwritten work or captions.
Design for the size at which people actually watch. A timetable that looks comfortable on the operator's large monitor may become unreadable on a mobile screen. Use short class names, clear row spacing and strong contrast. Avoid placing pale text over a detailed classroom image. If the background changes during the stream, a solid or lightly opaque panel gives the schedule a more consistent reading surface.
Do not fill the panel with every administrative detail. A phone number, long explanation, multiple logos and a full paragraph can push the useful information into a small corner. Put extended notes in the YouTube description or on the school's website, and reserve the video area for the current day, class times and next-class information.
Prepare more than one version if the timetable genuinely differs by day. Give each file a clear name, such as monday-timetable-IST.png and friday-timetable-IST.png. Store the editable source separately from the image used in the scene. That makes a correction easier when a teacher changes a class time, and reduces the chance that someone edits the only copy while the broadcast is running.
Before adding the graphic to the stream, view it at the intended output resolution and at a smaller window size. Look for clipped text, crowded rows and times that could be mistaken for dates. Ask someone who did not make the timetable to read it. A second person can often spot an unclear abbreviation or a missing day faster than the person who has been looking at the design.
Add the graphic to the encoder scene
The exact buttons depend on the encoder you have selected, so there is no universal timetable-overlay instruction. The general composition is the same: create or open the scene that contains the programme, add the timetable as a source, place it above the content, and confirm that the composed scene is the one being sent to YouTube.
A graphic file can be added as an image source in an encoder that supports image sources. A timetable hosted on an internal webpage may instead be shown through a browser or display source. If the schedule is part of a presentation, the presentation window can be captured. These are different source types, but the important result is the same: the timetable becomes visible in the encoder's preview and is included in its output.
If your encoder also carries a camera, microphone or lesson video, add those sources first and then add the timetable source. Check the source order if the encoder uses layers. The schedule needs to sit above the lesson content if it is meant to remain visible. If it is hidden behind an opaque video source, it may appear in the editor but not in the final picture.
The education guide from INFLIBNET demonstrates adding and positioning sources such as display capture and a video capture device in OBS. It is useful as an example of scene composition, but it does not establish a current universal timetable template or guarantee that every OBS installation uses identical labels. Follow the current documentation for the encoder version you actually operate.
Keep an uncomposed scene available if the timetable must sometimes disappear. For example, you might have a “timetable on” scene for the general channel and a “lesson only” scene for a full-screen demonstration. Name scenes and sources plainly. “Tuesday schedule, IST” is safer for handover than “Source 4”, particularly when a school has more than one operator.
If the timetable is a browser or display source, consider what else could appear in that window. Close unrelated tabs, notifications and private information before capturing it. A prepared image is often easier to control for a simple fixed schedule. A live webpage may be suitable when the timetable must be updated centrally, but it introduces another page and display state that should be checked before the stream begins.
Do not assume that adding a file to the encoder automatically changes the live output. Select the scene or layout that contains the source, then confirm that the preview shows the timetable over the intended programme. Some encoders distinguish between a preview and a live programme output, so make the change deliberately rather than relying on an unverified click.
Position and check it on screen
Position the timetable where it does not conceal the lesson's important information. A side panel may cover a teacher or a slide; a lower panel may cover subtitles or the bottom line of a presentation. There is no single correct corner because the underlying programme, aspect ratio and audience devices differ.
Play representative content while checking the graphic. Use a lesson slide with small text, a camera shot, a transition between videos and any captions that normally appear. The timetable should remain readable in each case. If it disappears against a bright background, adjust the panel rather than expecting viewers to interpret it from context.
Check the complete output, not just the local preview. If the encoder provides a monitoring view, use it. You can also inspect the YouTube preview before going live. Watch for scaling that makes the panel smaller than expected, cropped edges, a changed aspect ratio or a timetable that is visible locally but missing from the outgoing programme.
Ask three practical questions:
- Can a viewer tell which day and time zone the timetable refers to?
- Can they identify the next class without pausing the video?
- Can they still follow the lesson when the timetable is present?
If the answer to any question is no, change the composition before considering the stream ready. Readability is a production requirement, not a decorative extra. The official sources do not provide a universal font size or mobile-reading threshold, so judge the result on the actual output rather than applying an invented rule.
Keep the panel in a predictable location. Viewers who return to the channel should not have to search the entire picture for the schedule. If the position must change for a particular lesson, explain that change in the description or use a consistent alternative scene rather than moving it without warning.
A timetable can also become stale while remaining perfectly readable. Include a visible day or date where appropriate, and decide what should appear if the current class has ended. “Next class at 14:00” is more useful than leaving the last class highlighted indefinitely. If there is no lesson for several hours, show the next programme or a clear break label rather than implying that a completed class is still live.
Send the composed output to YouTube
Once the scene is correct, configure the YouTube broadcast and connect the encoder. YouTube's encoder setup guidance explains the current platform workflow for creating or configuring a live stream, using the stream URL and stream key, checking the preview and going live. Interface labels can change, so use the current Live Control Room instructions for the account and broadcast type you are operating.
Treat the stream key as a credential. Paste it into the encoder's stream settings without publishing it in a timetable document, screenshot or public instruction page. If several people operate the channel, keep access to the key controlled and document which broadcast it belongs to.
Before starting the continuous feed, check the preview for the final composition. Confirm that the timetable is present, the lesson content is present, audio is behaving as expected and there are no private windows in a display capture. The preview is also a useful place to check whether the output has been scaled or cropped by the time it reaches YouTube.
Your connection still matters even if the timetable is only a small graphic. The whole composed video, including the programme underneath it, is sent to YouTube. If you are deciding whether a particular connection is suitable, use a measured approach rather than guessing from a provider's headline figure. The guide on upload speed for a 24/7 YouTube stream in India covers the connection question in more detail.
The same applies to picture settings. A timetable with thin text can become hard to read if the output is compressed too heavily or scaled repeatedly. Use the encoder's supported settings and check the actual YouTube preview. The bitrate checklist for a YouTube stream is relevant when you are reviewing the wider delivery settings, although it does not replace YouTube's current guidance for your selected encoder.
YouTube says first-time live-stream activation may take up to 24 hours. Treat that as a setup requirement, not as something to discover when the first class is due to begin. Activate live streaming in advance, test the account and allow time to correct the timetable, scene and connection.
If you schedule a broadcast, use the current controls in Live Control Room and distinguish the event's scheduled information from the timetable in the video. A scheduled start can help a viewer find or remember a particular broadcast, but it will not create the visible timetable panel for you.
Keep the schedule current during a 24/7 run
A continuous stream needs a timetable maintenance plan. Decide who owns the source file, who approves changes and when the updated graphic is loaded. A teacher changing a class at 09:00 should not have to find an operator who is away from the control computer without a handover process.
For a fixed weekly schedule, prepare the next day's graphic before the current day ends. Load it into the encoder while checking the preview, then switch to it at an agreed time. If the schedule can change at short notice, keep the timetable editable and maintain a plain-text backup of the current classes so that an operator can rebuild the panel if the image is unavailable.
Changing a source during a live broadcast can briefly expose an empty scene, an old timetable or a transition that covers the lesson. Make changes during a low-risk moment and watch the outgoing result afterwards. If your encoder supports previewing a scene before taking it live, use that facility. If it does not, have a second operator verify the change from the public watch page.
Plan for gaps. A continuous education channel may have a lesson, a recorded explanation, a break and then another class. Decide whether the timetable remains visible over every part of the day or whether it changes with the programme. If the panel stays on screen during a break, label the break accurately. If the content switches automatically, test the boundaries; the advice on preventing black frames between videos applies to the wider loop even though it is not specifically about timetable graphics.
Automation can reduce repeated operator work, but it does not remove the need for a current source. A workflow that switches playlists or videos automatically may still show yesterday's timetable unless the graphic is updated as part of the same process. Read how a YouTube livestream can switch playlists automatically alongside your encoder documentation, and verify what is actually changed in the outgoing scene.
For an unattended stream, the practical pain is not creating the first timetable; it is keeping the composed output running when the office computer is off or the operator is not watching it. StreamNeo removes that specific computer-running burden by taking an uploaded video, using your YouTube stream key and continuing the broadcast from the cloud with monitoring and automatic restart. It is still your responsibility to prepare an accurate timetable graphic and decide how schedule changes are approved.
A 24/7 stream is also not automatically the same as a useful archive. YouTube says streams under 12 hours are automatically archived. Do not assume that one very long continuous feed will give you a complete automatic recording for every class. If learners need separate replays, plan recording and archive handling independently, or use separate class broadcasts where that better matches the teaching workflow.
The official API documentation describes a continuous 24/7 feed alongside a separate event broadcast as a platform model. That can be useful when a school wants one permanent destination plus a dedicated page for an examination briefing or guest class. It also creates more things to monitor, so test the handoff and decide which stream receives the timetable during the event.
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 YouTube add the timetable from the description?
No. The title and description are stream metadata, while the timetable viewers see must be part of the encoder's outgoing video. You can repeat the schedule in the description for people who open it, but that text does not appear over the lesson automatically.
Can I use one timetable for a continuous channel?
Yes. Add the timetable as an image, browser or display source in the scene and keep that composed scene live. Update the source when the day or schedule changes, and check the public output after each change.
Should every class have its own YouTube broadcast?
Not necessarily. One continuous broadcast suits a channel that wants one always-available destination, while separate broadcasts can be better when each class needs its own watch page, reminder or archive. A continuous feed alongside separate event broadcasts is also possible, but it adds operational complexity.
What should I do before the first live class?
Enable live streaming early because YouTube says first-time activation may take up to 24 hours. Test the encoder scene, timetable readability, stream key, preview, audio and archive plan before the teaching schedule depends on the channel.