A dependable way to add a stinger or jingle to a YouTube live stream is to put a local audio file in an OBS Media Source, then set its playback behaviour in the scene where it should play. Before you use it, check that its licence covers both the live broadcast and any archived replay.
This guide uses OBS as the concrete example; other streaming software may use different names and controls. The same sequence applies whether the cue is a station ident, a scene-change sound, a devotional channel intro or a short transition between programme segments.
Choose and prepare a cue file
Start by deciding what the sound needs to do. A one-shot sting marks a transition and then gets out of the way. An intro may play once as the broadcast begins. A bed or ambience track is different: it is meant to continue under other material, so its duration and loop behaviour matter more than a sharp ending.
Choose a file you can locate on the computer running OBS. OBS Media Sources support MP3, AAC, OGG and WAV files, according to the OBS Media Sources guide. Save the chosen file in a stable folder rather than Downloads or a removable drive that might be unplugged. If you move or rename it later, OBS may no longer find it.
Keep a clean copy of the original file. If you edit a cue to trim silence or make a fade, export a separate version with a clear name such as intro-sting-final.mp3. Listen to the exported file from beginning to end. A cut that sounds fine in an editor can leave a click, an abrupt tail or a little silence that makes a scene change feel late.
A short cue does not need to be loud to be recognisable. Check that speech remains intelligible when the sound plays, and avoid choosing an effect with a peak that will startle someone listening on a phone. You can adjust the source level in OBS later; first, make sure the file itself is the intended version and that it plays on the computer.
For a quick, downloadable option, YouTube Studio's Audio Library lets you search music and sound effects by keyword. Download the item you want and keep its attribution details with the file. If the track is offered under a Creative Commons licence, YouTube says to include the required artist credit in the video description. A custom cue can give a channel a more distinctive identity, but it also means you must establish the terms for using that recording.
Confirm rights for live use and archived replay
Do not assume a sound is cleared because it is brief, labelled “free” or called “royalty-free”. Check the licence for the actual recording and for the way you intend to use it. The relevant permission should cover a YouTube live broadcast; if you keep the stream as a replay, confirm that it covers that use as well. A licence may set conditions on attribution, territory, duration or monetisation, so read the terms rather than relying on a label or a description written by the uploader.
YouTube’s guidance says that music found online with a “free” label may still be flagged by Content ID. Its guidance on finding safe music recommends checking third-party licences. YouTube identifies Audio Library music and sound effects as known to it to be copyright-safe; that statement does not make every sound on another site equivalent, nor does it remove any attribution requirement attached to an Audio Library item.
The live risk is separate from whether you believe you hold permission. YouTube says it scans live streams for matches to third-party content. If it detects such material, it may replace the stream with a placeholder and warning; continued use can interrupt or terminate the broadcast. YouTube also advises creators who have licensed third-party content to ask the rights holder to add the channel to its Content ID allowlist. A licence alone may not prevent a live interruption if the channel has not been allowlisted.
An archived live video can receive a Content ID claim after the broadcast has ended. That makes the archive worth checking before you go live, not after a claim appears. Keep a copy of the licence, any written permission and the relevant attribution. If the rights holder needs your channel ID or URL to allowlist it, arrange that in advance and confirm it has been done. Do not treat a credit in the description as a substitute for permission.
If the sound comes from another creator or a production library, ask specifically whether the grant includes YouTube live use and retained VOD or replay use, and whether the channel needs allowlisting. If terms are unclear, choose a different cue or seek clarification from the rights holder. For a broader look at how music choices shape an ongoing channel, see running a chillhop radio stream with song rotation; the same habit of checking each source’s terms applies to a short sting.
Add a Media Source in OBS
Open OBS and select the scene in which you want the cue to be available. In the Sources dock, use the add control and choose Media Source. Give it a descriptive name, for example Scene change sting or Opening ident, so you can recognise it later when you revisit the scene.
In the source properties, point OBS to the local audio file. The Media Source is intended for media files placed into scenes, and OBS documents the supported audio formats in its source guide. Confirm that the source is enabled and that you have selected the right file. If the file does not appear or play, check its path and format before rebuilding the scene.
For a single cue, one Media Source is usually the simplest arrangement. OBS also documents a VLC Video source that can handle a playlist, but it requires VLC to be installed. A playlist makes sense if you need a group of files managed together; it adds another dependency and is unnecessary for one scene-change sound. If you are already working with recorded material in OBS, the guide to playing a recorded video playlist on YouTube Live covers a different playlist use case.
Adding a source does not mean you should leave it active everywhere. OBS sources belong to scenes, and scene composition determines what is available when you switch. The next decisions are whether the cue should loop, whether it should restart when activated, and which scene transitions should trigger it.
Set looping and playback restart behaviour
In the Media Source properties, decide whether the cue should loop. For a one-shot sting or intro, leave looping off so it plays once and ends. Enable looping only when the file is meant to provide continuous audio, such as a background bed. A short sound effect looping unintentionally can become a distracting repeated noise, particularly if the source stays active in a scene.
The restart option controls what happens when the source becomes active. If Restart playback when source becomes active is enabled, the cue starts from the beginning when the source is activated. That is usually the useful behaviour for a sting that should play afresh whenever you enter a particular scene. If it is disabled, the source may resume from its prior playback position rather than making the intended clean entrance. OBS documents both looping and restart controls in its Media Sources reference.
Think through the transition that will activate the source. If a scene contains the cue from the moment OBS starts, its activation may happen at a different time from the moment you intend viewers to hear it. If you want the cue only on a scene change, test that actual change rather than relying on a preview of the scene. Playback behaviour depends on source activation, so the scene and source settings need to work together.
Do not use looping as a workaround for a cue that ought to be retriggered. Looping makes the file repeat while active; restart-on-activation makes it begin again when activated. Those are different jobs. For example, a two-second channel ident should normally play once and restart on activation, while a longer ambience layer may be designed to loop and remain active.
Place the cue in the correct scene
Put the source in the scene that matches the moment you want the audience to hear it. A single scene-change sting might belong in an interstitial or transition scene rather than in the main programme scene. An opening ident may belong in a dedicated opening scene. This keeps the sound tied to an intentional action instead of leaving it running in the background by accident.
If you reuse a cue across several scenes, consider whether a shared scene or duplicated source setup is easier to operate without mistakes. Either way, give the source a clear name and test each route. A small local news channel, for instance, might use a short ident when moving from headlines to a weather loop, but not each time the operator returns to the headlines. The scene plan should reflect that editorial choice.
Pay attention to source visibility and activation rules, especially if you use nested scenes or transitions. A source can exist in a scene without being heard at the moment you expect if another scene is active, the source is muted, or the transition does not activate it as planned. If the cue should play on every entry, test leaving the scene and returning. If it should play only once at startup, test a full start sequence rather than repeatedly clicking a source during setup.
For a 24/7 channel, a cue may be heard by people who join at any point, not only at the beginning of a scheduled programme. That is a reason to use transitions sparingly and to place them where they provide context. Channels built around repeated devotional segments can plan their scene sequence alongside the morning prayers and aarti stream guide, while keeping the cue’s timing and rights checks specific to the file being used.
Check levels and test the transition
Use the OBS audio mixer to check the cue alongside speech, music and other programme sound. Start with the cue low enough that a presenter’s words remain clear, then listen to the overlap at the point where the scene changes. There is no universal mixer value for a sting: the perceived level depends on the recording, the other sources and the listener’s playback device. Listen rather than setting a number because it looks familiar.
Watch the mixer while the cue plays. Make sure the source is not muted, that its meter responds and that other audio sources behave as expected. If the cue masks speech, lower its source level or revise the transition so it does not overlap. If the cue sounds thin or disappears on a phone speaker, it may need a different mix or a different sound rather than simply being turned up until it dominates.
Record a short local test or use a private or unlisted broadcast to hear the complete path as a viewer would. Check that the sting begins at the intended moment, starts from the beginning on the next activation, ends cleanly and does not repeat. Test with the microphone and background programme audio active, since a cue that sounds fine by itself can clash with narration or a music bed.
Do the test from the scene sequence you intend to use, not only by pressing play in the source properties. Include the transition into and out of the scene, and listen to the recording afterwards. A viewer’s experience includes the incoming and outgoing audio, not just the sound file. If you rely on a recorded loop or playlist as well, the guide to using Icecast metadata in a YouTube radio livestream is useful context for keeping programme elements coordinated.
Before the real broadcast, confirm that the channel, scene and source are the intended ones, the cue file remains available at its saved location, and the licence record is easy to retrieve. A successful local test proves the audio route works; it does not prove rights, allowlisting or YouTube review outcomes. Keep those checks separate.
Troubleshoot playback or mix issues
If there is no sound, first confirm that the source is in the active scene and not muted in the mixer. Then inspect the file path, test the file outside OBS and check that it is one of the supported formats. If you recently moved the file or renamed a folder, reselect it in the source properties. A broken path can look like a mysterious scene problem when the source simply has nothing available to play.
If it plays only the first time, inspect restart behaviour and the way the source becomes active. Leave the scene and return to it in a controlled test. If the cue continues from the middle or does not start again, enable restart-on-activation if that matches your intended behaviour. If it plays repeatedly, check whether looping is enabled or whether the scene sequence is activating the source more than once.
If the cue is too loud or buries speech, reduce the source level in the mixer and test the full scene again. Avoid changing several levels at once; otherwise, it is hard to tell which change improved the balance. If the cue is missing only in the recording or stream, compare the audio routing and the monitored output with the local test, then make a new test recording before going live.
If YouTube warns you about matched content, stop and review the cue’s rights and the platform’s guidance rather than assuming the alert is a mistake. A claimed licence may still require the owner to allowlist your channel. Check YouTube’s current live-stream copyright guidance, and remember that an archived stream may be checked after the live session. Do not keep a questionable cue in rotation while waiting to see whether the issue resolves itself.
A cloud-operated channel can remove the need to leave a personal computer running for the broadcast, but it does not replace careful cue preparation or rights checks. StreamNeo is useful when the specific pain is keeping a computer powered on simply to carry a prepared video stream through the night; the cue still needs to be part of a tested file and cleared for its intended uses.
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
How do I play a sound effect when I switch scenes in OBS?
Add the local audio file as a Media Source in the scene where it should play. Enable restart when the source becomes active if you want it to start from the beginning each time you enter that scene, then test the actual transition and mix.
Can I use a royalty-free jingle during a YouTube live stream?
Only if the licence covers your intended live use and any replay you keep. “Royalty-free” does not by itself establish that permission, and a third-party rights holder may need to allowlist your channel for Content ID.
Should a stinger loop in OBS?
Usually not if it is a one-shot transition or intro: leave looping off and use restart-on-activation when it should play again on a later entry. Looping is for audio intended to continue repeating while its source remains active.
Does a licence guarantee that YouTube will not interrupt my live stream?
No. YouTube says a licensed third-party stream may still be interrupted if the channel has not been allowlisted by the rights holder, and archived streams can receive claims after the broadcast. Check the current YouTube guidance and confirm the necessary arrangements before using the cue.