To keep a devotional image on screen while a local audio file plays continuously in OBS, create a scene with an Image Source and a Media Source, then enable Loop on the audio source. Before you stream, check that the audio reaches OBS’s mixer and YouTube’s preview, and confirm you have permission to broadcast both the image and the recording.
A still image does not need to be converted into a video just to appear in an OBS scene. The practical work is choosing the right sources, checking how they behave together, and testing the viewer-facing stream before your programme begins.
Prepare the image, audio and rights
Gather the image and audio files you intend to use before opening OBS. Keep them in a folder you can find again, and avoid moving or renaming them after you have selected them as sources. OBS needs to be able to access the local files when the scene is used; a source pointing to a file that has moved may not behave as expected later.
Check that you have the right to broadcast each item on YouTube. That may mean using material you created, material licensed for this specific use, or material for which you have otherwise confirmed permission. A devotional subject does not itself make a recording or image free to use. A familiar bhajan recording can still be someone else’s performance or sound recording, and an image found online may have reuse conditions.
Keep permission details and licence terms accessible. A subscription or download permission should not be assumed to cover a public live broadcast unless its terms say so. YouTube says it scans live streams for third-party content; identified material may trigger a warning or a placeholder, and persistent content may interrupt or terminate a stream. Some licensed tracks may still be interrupted unless the rights owner allowlists the channel. Read YouTube’s guidance on copyright issues with live streams and check any relevant permissions with the rights owner before relying on a track.
This is separate from the technical setup. OBS can display the selected image and play a selected audio file, but those functions do not grant you rights or confirm that a particular use is permitted. If you are unsure whether a licence covers a live YouTube broadcast, resolve that before scheduling the stream rather than treating a successful test as proof of permission.
Create a scene in OBS
Open OBS and create a scene for this broadcast, or select a scene you have set aside for it. A scene is the arrangement of sources that OBS will show and send to the stream. Giving this setup its own scene makes it easier to check the devotional image and audio together without disturbing other layouts you use.
In the Sources panel, choose the plus button and add an Image Source. OBS’s Sources Guide explains how sources are added and how their order affects what appears on top. Name the source clearly, such as “Main devotional image”, so you can recognise it later. Select the image file and confirm it appears in the preview.
Source order matters when sources overlap. For a simple still background, keep the image below any optional text or other visual source. If the image sits above a text overlay, it can cover the text. You can drag sources in the list to change their order; check the preview after doing so rather than assuming the list order is correct.
If this is your first OBS stream, the OBS Quick Start Guide is a useful companion for understanding the basic scene and source workflow. Keep the immediate goal modest: one scene, one image, and one audio file. Add overlays only if they serve a clear purpose and you have time to test them.
Add and position the devotional image
Select the Image Source and choose the still devotional image from your computer. A successfully selected source should appear in the OBS preview. If it does not, check the file selection and confirm that the file still exists at that location.
Set a sensible landscape canvas and output for the way you intend to present the stream, then fit the image to the canvas. The image should fill the intended frame without being accidentally cropped or stretched. OBS’s preview gives you a practical way to inspect the composition: look for cut-off text, faces, important symbols, or borders, and check that the picture is not obscured by another source.
If the image’s shape does not match the canvas, fitting it may leave empty space or crop some of the original. Decide which matters more for your design. For example, a square image may be easier to preserve in full with space around it than to enlarge until its edges are lost. Do not stretch a devotional illustration just to fill every part of the screen if that distorts the artwork.
A static image remains static while the audio plays. It does not need to be exported as a video file merely to sit on screen in OBS. If your intended presentation includes timed slides or motion, that is a different setup and should be tested separately; this guide covers a single still image.
Once the image looks right, leave the preview open while you add the audio. That lets you check that the picture remains visible when you select or adjust the next source. A still frame makes framing simple, but it is still worth checking what a viewer will see rather than relying on the source name alone.
Add the audio Media Source
In the Sources panel, use the plus button again and select Media Source. Choose a clear name, such as “Continuous devotional audio”, then select the local audio file. OBS documents its Media Source and lists MP3, AAC, OGG and WAV among supported audio formats.
For one file that should repeat, Media Source is the straightforward route: it has a loop setting for that file. Make sure the source is active and visible in the scene, then watch the OBS audio mixer as playback begins. A moving meter is useful evidence that OBS is receiving audio from the source, but it does not by itself prove that the YouTube stream will deliver audible sound to viewers.
There is another route if your plan is a playlist rather than one file. OBS’s VLC Video Source can work with a playlist and offers Loop Playlist, but it depends on VLC being installed. The OBS and VLC architectures should match: 64-bit OBS needs 64-bit VLC. For a single local track, that extra dependency is unnecessary. The choice is not about which is universally better; it is about whether you need a playlist and are prepared to maintain the VLC dependency.
| OBS route | Use it when | Loop behaviour and requirement |
|---|---|---|
| Media Source | You want one local audio file | Enable Loop for that file in the source properties |
| VLC Video Source | You need a playlist workflow | Enable Loop Playlist; VLC must be installed with a matching architecture |
Choose the route that matches the actual broadcast rather than adding complexity “just in case”. If you later change from one recording to a playlist, make the change in a test session and verify playback again before the scheduled stream.
Enable looping and test a full repeat
Open the Media Source properties and turn on Loop. This tells OBS to start the file again when playback reaches its end. It does not create new audio, repair a damaged file, or promise that playback will never stop for another reason. Check that the selected file is the one you meant to use and that playback actually starts.
Let the track reach its end during a test, then listen for the transition as it starts again. The end of a recording may contain silence, a cut-off note, or a long pause that becomes noticeable on repeat. Looping repeats the file as supplied; it does not smooth or edit the join. If the transition is distracting, prepare a suitable audio edit using material you are entitled to use, then select and test that file.
Keep the Media Source active in the scene. If you switch to a different scene during a live broadcast, the audio behaviour may depend on the sources and scene arrangement you have configured. Test the scene you expect to use, and avoid treating a moving meter in an unrelated scene as confirmation that this audio is live.
For creators who want to loop product demo videos on YouTube Live with OBS, the same broad principle applies: test the repeat behaviour of the actual media in the intended scene. For a devotional audio file, pay particular attention to the join and to whether the source remains active after the file restarts.
Check the audio path and levels
Start playback and look at the OBS mixer. The source’s meter should respond when audio plays. If it does not, check that the Media Source is active, that the correct file is selected, and that the source is not muted. Confirm that the file itself plays on your computer. Make one change at a time and observe the mixer again, so you can identify which adjustment fixed the issue.
The mixer is a check of the OBS input path, not the entire route to a viewer. You also need to establish that the stream sent to YouTube contains audible audio. During a private or otherwise appropriate test, monitor the YouTube preview from a separate device or playback route where possible. Avoid judging the viewer sound solely by listening to the same computer that is running OBS; local monitoring can work even when the streamed audio path is configured differently.
If you have added another audio capture source, check for duplicate capture. OBS warns that capturing the same device both in a scene and in global Settings > Audio can cause echo. A local Media Source is not the same as capturing a microphone or desktop device, but the wider scene can still include other audio sources. If you hear doubling, inspect the mixer and mute or remove the duplicate route rather than lowering everything indiscriminately. OBS’s Audio Sources guide describes the different source types.
Set the level so the audio is clear and does not sound distorted. Listen through the loudest part of the recording, not only a quiet opening. The meter can help show that audio is present, but use your ears as well: clipping or distortion in the file will not be repaired simply by routing it through OBS. For further troubleshooting, see this guide on stopping audio clipping in a 24/7 rain stream; the subject differs, but the practical habit of checking louder passages is relevant.
Connect OBS to YouTube Live
In YouTube Studio, open the Live Control Room and create or select an encoder stream. Follow YouTube’s current instructions for creating a live stream with an encoder. Copy the server URL and stream key into OBS’s stream settings. Treat the key like a password: do not show it in a screen capture, share it in a message, or leave it visible during a public demonstration.
Choose output settings with both YouTube’s guidance and your actual upload connection in mind. YouTube’s encoder settings page lists H.264, H.265 (HEVC) or AV1 video, AAC or MP3 audio, CBR bitrate encoding, and a recommended keyframe interval of two seconds, not exceeding four seconds. For stereo audio, its advanced settings list a 44.1 kHz sample rate and 128 kbps audio bitrate. Check the current YouTube encoder recommendations before you set a profile, as platform guidance can change.
For H.264, YouTube lists 5 Mbps as its recommended bitrate for 1080p at 30 fps and 3 Mbps for 720p at 30 fps. These are platform recommendations, not promises that your connection or computer will sustain them. YouTube also recommends keeping upload-bandwidth headroom in its streaming tips; use the current page rather than assuming the available upload speed is all available for a stable live stream.
| H.264 starting point | YouTube-listed recommended bitrate | What to consider |
|---|---|---|
| 720p at 30 fps | 3 Mbps | A lower output demand than the 1080p example, but test it on your actual connection |
| 1080p at 30 fps | 5 Mbps | Use only if upload capacity and computer performance can sustain the chosen output |
YouTube advises running a speed test to test upload bitrate. A speed test result is a point-in-time check, not a guarantee of stable performance through a long broadcast. If the available upload capacity is limited or variable, choose a more modest resolution and bitrate that fit the conditions you can observe, then test the actual stream. The still image does not require motion-heavy video encoding, but a stable ingest connection is still needed to deliver audio and video to YouTube.
Verify the preview before going live
Start with a test using the same image, audio file, scene and output settings planned for the real broadcast. OBS’s Quick Start Guide recommends testing for a few minutes rather than jumping straight into a first stream or recording. YouTube likewise advises testing before going live, with audio and movement in the video similar to what you plan to stream. For a static image, the key checks are that the image stays visible and the audio plays as intended.
Check both ends of the route. In OBS, confirm the scene preview looks right and the audio meter moves. In YouTube Studio, wait for the stream preview and inspect the stream health indicators. Listen to the preview from a viewer-facing device or route, at a sensible volume. Check that there is no unexpected silence, echo, distorted sound, black or misplaced image, or delay that would make the presentation confusing.
If the preview has no sound, work through the path in order: confirm the file plays locally, confirm the Media Source is active and not muted, check the OBS mixer, and then check YouTube’s preview. If the preview has sound but the level is wrong, adjust and repeat the test. If the image is cropped or covered, correct the source fit or order and look again at the YouTube preview rather than stopping at the OBS canvas.
A successful test shows that the setup worked under the test conditions; it cannot guarantee uninterrupted playback later. Network conditions, a computer sleep or restart, file access, and other changes can affect a stream. For a one-off event, stay nearby and monitor it. For a recurring or extended broadcast, plan who will check the channel and what they will do if the stream drops. If you need to review what happened after a broadcast, YouTube Analytics for live streams can help you examine available stream reporting, but it does not replace live monitoring.
This is also where the distinction between a working setup and a permitted broadcast matters. A clear preview confirms that the audio and image reached YouTube during the test; it does not establish that either item is authorised for the planned use. Keep the relevant permissions available and follow up on any platform notice. YouTube’s live Content ID matching programme has separate operating requirements, so do not treat those requirements as a general rule that every creator must own every element. The practical task here is to clear the actual image and recording you plan to use.
Keep the setup manageable for repeated streams
Once the test passes, avoid making untested changes immediately before the broadcast. Keep the image and audio in a known location, note which OBS scene is intended for the stream, and keep the stream key private. If you change the file, scene, source order, output profile or audio routing, check the affected part again in a test rather than assuming the previous result still applies.
For a recurring devotional channel, a short written checklist is more useful than relying on memory during a late-night start. Include: open the intended scene; confirm the image is framed; confirm the correct audio file and Loop setting; confirm the mixer responds; check the YouTube preview and stream health; and verify rights documentation is at hand. These are checks, not a promise that every issue will be prevented.
If keeping a computer running OBS and checking it through the night is the part that is difficult, StreamNeo can remove that specific computer-on burden by turning an uploaded video into a YouTube live stream that runs with your computer switched off. It is a different workflow from this OBS scene guide, so stay with OBS when you specifically need to configure an encoder scene on your own computer.
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 a still devotional image need to be made into a video first?
No. Add it as an OBS Image Source and fit it in the scene preview. A still image can remain on screen while a separate Media Source plays audio.
How do I loop one audio file in OBS?
Add the local file as a Media Source and enable Loop in its properties. Play it through a full repeat during a test so you can hear how the end joins the beginning.
The OBS meter moves, but why can’t I hear the YouTube preview?
The meter confirms audio is reaching the OBS mixer, not that viewers can hear it in the YouTube stream. Check the source is active and unmuted, then listen to the YouTube preview from a viewer-facing device or route and inspect the stream configuration.
Does a successful test mean I have permission to stream the image and music?
No. A technical test checks that the setup sends the material; it does not grant rights. Confirm that the image and recording are cleared for your intended YouTube broadcast, and consult YouTube’s current guidance if a rights issue appears.