To show the current lesson title in a 24/7 YouTube education stream, add it as a visible text overlay in the video composition and update that text when the lesson changes. YouTube’s stream title is separate: it labels the live event on the platform, while an OBS overlay appears inside the video image.
Decide whether you need one or both. If viewers should be able to identify the lesson while watching, update the overlay; if the live event listing should also identify it, update YouTube metadata separately. Neither field automatically changes the other.
Choose between an overlay and stream metadata
An overlay is part of the video being sent to YouTube. It can name the current lesson, show a course or chapter label, or give context when a viewer joins in the middle. In OBS Studio, a text source placed in a scene is one way to put that information over the video. The label appears wherever that scene is used, until you edit it, hide it, or switch to a scene without it.
YouTube metadata is the information attached to the live event on YouTube. YouTube Help explains that you can edit encoder stream details in YouTube Studio, including from the stream’s settings. That platform-facing title does not put words over the video. Equally, changing a text source in OBS does not rename the live event in Studio. See YouTube’s instructions for managing live stream settings before changing the title in your account.
| Approach | Where viewers see the title | Who or what updates it | Useful when |
|---|---|---|---|
| OBS text source | In the video image | An operator, changed text file, or a configured integration | The lesson name should remain visible while people watch |
| OBS browser source | In the video image, rendered from a web page | The web page or its existing publishing workflow | A title graphic or page is already maintained online |
| YouTube Studio metadata | On YouTube’s live event or stream details | Someone with access to the channel, or a separately configured integration | The platform listing should reflect the current lesson |
| Separate OBS scenes | In the image through the layout of each scene | An operator switches to the scene for the next lesson | Lessons use different layouts as well as different names |
For a straightforward lecture loop, a persistent text source is usually the least complicated visible label: one source, edited when the lesson changes. If each class has a different layout, such as a different instructor panel or slide arrangement, separate scenes may be more suitable. Metadata is a distinct task in either case.
YouTube’s API documentation distinguishes a broadcast from the stream carrying the feed, and the broadcast can have its own title and other details. That is useful context for developers building a custom integration, but it does not provide a ready-made connection between an education timetable and an OBS text source. Any link between a schedule, visible overlay and platform metadata needs to be supplied by your own workflow. For a continuously changing video library, the separate question of keeping a YouTube playlist live while adding new videos is worth considering alongside how you identify the lesson currently playing.
Add a text source to the OBS scene
First identify the scene that is actually carrying the lesson video. OBS scenes are compositions made from sources; the text needs to be added to the scene viewers receive, not merely to a scene you use for a starting screen or an unrelated transition. If several scenes carry the lesson, decide whether the same label should appear on each one and add or reuse the source accordingly.
In OBS, select the relevant scene and use the Sources panel to add a text source. The exact menu wording can vary with the operating system and version, so use the source-add controls in the installed application. Give the source a useful name such as “Current lesson label”, especially if the scene already contains video, slides, a camera and other graphics. A descriptive source name helps you select the right item later without guessing.
Enter a short sample title and confirm that it appears in the preview. Text sources may let you set font, size, colour and other appearance choices in their properties. Choose settings that can be read over the actual lesson image, not just against the OBS preview’s empty or dark areas. If you need a background behind the words, you can use an appropriate graphic source or a title design; check that it does not cover important slide content.
OBS’s Sources Guide describes sources as the building blocks in a scene and documents the available ways to add them. Use that guide if you need the exact steps for your OBS version. The important operational point is to verify the result in the scene preview and then in the outgoing programme, rather than assuming that entering text makes it visible in the right place.
A text source can be used in more than one scene, but be deliberate about whether those scenes should share the same text. If two scenes have independent copies, an operator may update one and leave the other showing an old lesson. If the scenes share a source, a text change may affect each place that source is used. Test this behaviour in your own scene collection before relying on it during a long broadcast.
Position and style the lesson label
Place the label where it can be read without covering the lesson’s essential material. For a slide-based class, a lower corner may be clear on one slide and obscure a diagram on another. Preview the overlay across representative slides, including ones with text near the edges, rather than judging it against a single title card. If the video layout changes, check the label position in each layout.
Keep the wording concise. “Algebra: linear equations” may identify the subject and lesson more clearly than a long course description that wraps over several lines. If you also need to show the instructor or course name, decide which information is most useful to a viewer joining mid-session and give it a clear hierarchy. Avoid styling that makes a lesson label compete with the actual teaching material.
Contrast matters more than decorative detail. Light text can disappear over a bright slide; dark text can disappear over a dark video. A solid or partly transparent backing can help, but it should remain restrained enough that it does not hide the content. Check the result at the size viewers are likely to watch, including on a phone, and with the video moving behind the label.
If the stream includes a camera view alongside slides, test the label against both. A placement that works over a slide may sit over a face or captions in the camera layout. You may choose a different scene arrangement, a consistent safe area, or a background panel behind the title. The right choice depends on the material, so review the real compositions rather than applying a universal screen position.
When a lesson title changes but the teaching layout stays the same, keeping the text source in place avoids unnecessary scene changes. When the next lesson requires a different layout, prepare another scene instead. OBS Studio Mode allows an operator to preview a scene before transitioning it to the live output; OBS explains the relevant controls in its Studio Mode overview. It can reduce mistakes during a planned transition, but the operator still needs to choose the correct scene and title.
Update the text when the lesson changes
A visible title is only useful if it matches the lesson actually playing. Write down who is responsible for changing it and at what point: before the next lesson begins, during a short transition, or as part of a scheduled handover. For a small channel, one operator may update the source and verify it. If another person controls the lesson sequence, agree how they will communicate the next title to the operator.
For a manually managed stream, select the text source, edit its contents, and check the preview before or at the lesson change. Avoid changing the title well ahead of the video if viewers can still see the previous lesson; equally, do not leave the previous title on screen after the new lesson has begun. A brief transition card can help if the programme includes a natural pause, but it is not a substitute for checking the final title.
A text file can be a practical handoff when the title is maintained outside OBS. OBS can use a text source that reads from a file, depending on the source and settings available in your version. In that arrangement, someone or something still has to put the correct lesson name into the file, and you need to confirm that OBS refreshes it as expected. Do not assume that a timetable or playlist changes the file unless you have explicitly configured and tested that connection.
Automation is possible as a custom workflow, but its parts must be specified. For example, a schedule might provide the current lesson name to a process that updates a text file, while a separate process updates YouTube broadcast metadata. Those are separate connections with separate failure points: a timetable may be wrong, a file may not refresh, or a platform update may fail. The reviewed OBS and YouTube documentation describes sources, scenes and metadata controls; it does not document a built-in timetable-to-overlay feature.
If a class sequence changes at short notice, make sure the update process can handle it. A manual workflow needs a person available to edit the title. A scheduled workflow needs a way to correct or override the schedule. Keep a fallback title or a way to hide the label if the current name is uncertain; a confidently displayed wrong title is less useful than a neutral label. If you also need to plan how material enters the stream, see how to make a live playlist of property tours in Marathi for a separate example of arranging prerecorded material into a continuous YouTube presentation.
The point at which the title changes should match the content transition. If the video is a sequence of recordings, a title change can coincide with the cut to the next recording. If the stream uses a live instructor or a lesson that does not follow a fixed schedule, update the label when the operator confirms the lesson has actually started, rather than relying on the planned timetable alone.
Use a browser source for an existing web-based graphic
OBS Browser Source places a web page into a scene. OBS’s Browser Source documentation describes it in simple terms: “Add a web page to your scene.” This is useful when your title design or a workflow that already maintains the current lesson is served as a page. It is not a title generator: adding a browser source does not make OBS discover which lesson is playing.
Before using this route, establish what the page displays and how it gets its data. If a staff member updates the page, that person remains responsible for the lesson name. If the page reads from a schedule or another system, verify that the system publishes the right lesson at the right time and that the page refreshes or updates in the way your scene requires. The browser source only renders what the configured page makes available.
In OBS, add a Browser Source to the intended scene and enter the address of the page you already maintain. Set its dimensions to fit the graphic you designed, then position it like any other source. Check whether the page background is transparent or opaque and whether the browser view includes unwanted page margins, navigation or other elements. A web page intended for a normal browser window may not be laid out well as a compact video overlay.
Test the page when the stream is running, not only when it is first loaded. Confirm that the title changes after the page changes, that the text remains legible in the video composition, and that a temporary connection or page error does not leave a misleading title on screen. If you cannot maintain a web page reliably, a plain text source may be easier to operate. Do not introduce a browser source merely because it sounds more automatic; the underlying title workflow must already exist.
Test the change during a private or unlisted run
Test the complete path before relying on a title update in the public 24/7 channel. Use a private or unlisted test stream where appropriate, following YouTube’s current visibility and live-stream settings. Confirm that the OBS scene with the title is the scene actually being sent, that the text is readable in the resulting stream, and that the update appears when you change it. The local OBS preview is useful, but it does not confirm every part of the YouTube viewing path.
Run through the same transition you expect in normal operation. Start with one lesson title, change to a second, and check what viewers see before, during and after the change. If you use a browser source, change the underlying page by the method your team normally uses. If you use separate scenes, preview the next scene and transition through Studio Mode. Check that no duplicate or stale label remains on screen.
A private or unlisted run also gives you a chance to test recovery. Close and reopen the relevant scene or source if that is part of your normal procedure, and check whether the intended title returns. For a page-based overlay, make sure it renders after a reload. Do not treat a successful short test as proof that every future transition will work; it confirms the tested workflow and gives you a chance to document any manual steps.
Write a small handover note for whoever may be on duty: which scene contains the label, which source to edit, where the next lesson name comes from, and how to verify the change. If the person updating the lesson title is not the person operating OBS, state who confirms the final wording. This reduces the chance that the teaching sequence and the on-screen label drift apart during an overnight or weekend schedule.
For a longer-running channel, also decide what the label should show if the programme pauses, repeats a lesson, or moves to a fallback video. A static title left over from the previous lesson can confuse someone who joins at that point. You may choose a neutral status label during a transition, hide the source, or show the title of the fallback content. Decide and test the behaviour rather than leaving it to guesswork.
Verify the visible label and metadata separately
Before a lesson begins, check the video output and YouTube event details as two separate items. In the video, confirm the exact spelling, position, contrast and timing of the overlay. In YouTube Studio, confirm that the live event’s title and description are appropriate for the event. If the platform title is intended to name the current lesson, update it through the available Studio controls; do not expect a text edit in OBS to do this for you.
If the public event title is meant to describe the whole channel or a long-running programme rather than each lesson, it may be more useful to leave that title stable and put the changing lesson identity in the overlay. The best choice depends on how viewers find the stream and how often lessons change. In either case, make the distinction explicit in the operating notes so the person handling a lesson transition knows whether one field or both fields need attention.
The YouTube Live Streaming API can be used by developers to manage broadcast details, including titles, but it requires a separately implemented workflow and appropriate authorisation. Google’s documentation on live broadcasts and streams explains the distinction, and the LiveBroadcast resource reference documents broadcast fields. Neither document establishes a ready-made link to your course schedule or OBS overlay. If your channel needs that level of automation, treat it as a development project and test each update path independently.
Keep a simple transition checklist close to the operating controls: confirm the lesson playing, update the visible label, verify the outgoing image, and update platform metadata only if your channel’s naming practice calls for it. For multiple channels, separate lesson libraries, schedules and scene collections can otherwise be easy to mix up; a practical planning point is covered in keeping separate video libraries for multiple channels. The checklist should reflect your own workflow rather than assume the same update method for every channel.
When a label is wrong, correct the source or page and verify the output again. Also check the platform title independently if that is meant to reflect the same lesson. A reliable process is not one that never needs correction; it is one where the responsible person can spot a mismatch and knows which separate field to change.
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 changing the OBS title overlay change the YouTube stream title?
No. The overlay is part of the video image, while the YouTube title is platform metadata. Change each separately if both should identify the current lesson.
Can OBS automatically show the lesson that is playing?
A text source displays the text you provide, and a browser source displays a page you provide. To update either automatically, you need a configured workflow that supplies the current lesson name; OBS does not infer it from a timetable or playlist by itself.
Should I use a text source or a browser source?
Use a text source when an operator can edit a simple visible label. Use a browser source when you already have a web-based graphic or page workflow that maintains the title, and verify that the page updates and renders correctly in the scene.
Do I need to change YouTube metadata for every lesson?
Not necessarily. If the YouTube event is intended to represent the whole continuous programme, you may keep its title stable and identify individual lessons in the video. If the event title should name the current lesson, update the metadata separately and confirm it in YouTube Studio.