To add a still image and an audio playlist in OBS, put the image and a VLC Video source in the same scene, then enable Loop Playlist on the VLC source. If you only have one long audio file, use a Media Source and enable Loop instead.
Those settings repeat media; they do not keep a computer, internet connection, encoder or YouTube broadcast running around the clock. If the goal is a 24/7 mantra channel, you also need to decide where playback will run and who will notice and respond when it stops.
What a free always-on setup must cover
A still image and playlist are the content portion of the setup. The image remains visible while the audio source plays, and looping tells OBS what to do when the playlist ends. A continuously available channel needs more: a machine capable of running the scene, power, a stable network connection, a configured encoder and a way to recover from failures.
“Free” can mean different things here. OBS and VLC are free software, but a computer left running still uses power and depends on your home or office connection. A cloud account may offer resources without a charge under specified conditions, but you must configure those resources, stay within the provider’s terms and handle monitoring yourself. Managed playout may reduce hands-on work, but its price and limits depend on the provider’s published plan.
It helps to separate the requirements before choosing. First, make the scene play the right content. Second, test that the stream reaches YouTube. Third, decide how the broadcast will be restarted or checked if something fails. One successful test answers only the first two questions for that test; it does not establish that a setup will continue indefinitely.
For a single track, OBS’s Media Sources guide describes local audio playback and the Loop setting. For multiple tracks, the same guide explains VLC Video playlists. The source name can be misleading: VLC Video supports audio files as well as video files.
Build the scene in OBS
Start with a scene for the mantra broadcast. Add an Image source and select the still visual you intend to show. Add the audio source to that same scene so the image and sound are present together. Check that the image fits the canvas and that the audio meter moves when playback begins; these are simple checks for a blank canvas or silent source.
For a collection of tracks, add a VLC Video source and use its playlist controls to add the local files. Enable Loop Playlist so playback starts again after the last item. Shuffle Playlist is optional: use it if a changing order suits the channel, and leave it off if you want a predictable sequence. OBS documents shuffle as off by default in the cited guide, but software interfaces can change, so check the controls in your installed version.
VLC must be installed for VLC Video to appear in OBS. OBS’s documentation specifies that 64-bit OBS requires 64-bit VLC. If the source is missing, check the installation and matching bitness before rebuilding the scene. The OBS media source documentation is the primary reference for the source options and compatibility note.
If there is only one long recording, a Media Source is simpler than constructing a playlist. OBS lists MP3, AAC, OGG and WAV among supported local audio formats and provides a Loop control for repeating one file. A collection in a single continuous file avoids track transitions inside OBS, but it is less convenient when you need to replace or reorder individual mantras.
Before streaming, listen through the playlist and inspect the transitions. Confirm that files begin and end as expected, the order is intentional, and no track is unexpectedly silent. If the visual includes text, verify it remains legible at the stream’s viewing size. These checks do not address licensing: use audio and images whose rights permit the livestream you plan to make.
Assess OCI Always Free as a DIY candidate
Oracle Cloud Infrastructure’s Always Free resources can be considered for a technically capable DIY setup, but the relevant question is not simply whether an account has resources labelled free. You need to determine whether the available compute, storage, network transfer and applicable account terms suit your particular media and stream. This article does not establish that any particular OCI configuration fits, nor that free resources provide managed always-on playout.
A DIY cloud setup means you take responsibility for making the playback and broadcast software run, configuring it to reach YouTube, and checking what happens after a disconnect or process failure. You also need to understand how the resource’s eligibility and usage are governed by OCI’s current terms. A resource being available at no charge is not the same as an ongoing service commitment for your channel.
This can make sense if you are comfortable with cloud administration, can test the full path from media to YouTube, and are willing to monitor and maintain the setup. It is a poor fit if “free” is being used to mean “someone else will keep the channel going without my attention”. For a VPS-based approach, compare the practical responsibilities in starting a nonstop sermon stream with a VPS in India. The workloads differ, but the distinction between configuring your own environment and buying managed playout is relevant.
Do not infer a service guarantee from an account tier’s name. A stream can fail because of the application, a configuration error, a provider change, YouTube ingestion, or a media problem even when a compute instance is available. Your decision should rest on the current resource description and terms, plus your own end-to-end test and recovery plan.
Check capacity and outbound transfer
The media files and the outgoing live stream place different demands on a setup. The playlist requires enough storage for the files you intend to play, while the outgoing broadcast consumes network transfer for as long as it is sent. Compute also has to encode the visual and audio reliably at your chosen settings. Without the file sizes, encoding settings, schedule, and current resource limits, it would be misleading to say that a particular free configuration fits.
Estimate from your actual content and intended broadcast settings rather than a generic claim. Add up the local media size to see whether it fits the storage you are considering. For network transfer, use the outgoing bitrate you configure in OBS and the time you expect to stream to estimate the amount sent; include a margin for testing and other traffic. Then compare those needs with the provider’s current published limits and terms. If the numbers are close to a limit, do not treat the configuration as suitable merely because a short test worked.
For YouTube, OBS’s ability to send a stream and YouTube’s ingest requirements are separate from the local playlist settings. YouTube’s HLS ingest guidance gives format and segment requirements for HLS specifically. Those instructions do not describe VLC playlists, nor do they promise a broadcast will run continuously. If you are not deliberately using HLS, do not apply its segment settings to a normal local audio playlist.
A local OBS machine avoids cloud compute configuration but still relies on local power and connectivity. A cloud DIY setup moves the workload away from your desk but adds cloud configuration and account limits to the work. A managed playout service may take on some playback operations, though you still need to prepare suitable media, configure the destination and review what the plan actually includes.
Compare managed playout plans
Managed playout is a different operating model from installing OBS and VLC on a computer you leave on. You provide the content and configure a channel or destination according to the provider’s process; the provider runs the repeated broadcast as a service. StreamNeo, for example, removes the need to leave your own computer running for this uploaded-video-to-YouTube workflow, which addresses the specific problem of keeping a desktop powered and connected. It is YouTube-only, so it is not a fit if you need to broadcast to another platform.
Do not compare plans by a headline word such as “unlimited” or “always on” alone. Check whether the plan supports a still visual with audio, how it accepts the media, whether playlists or a single prepared file are required, what channel or stream limits apply, and what happens if content needs to be changed. Confirm whether monitoring and automatic restart are described, and read any exclusions. A service’s description is evidence of its stated features, not a guarantee that a YouTube channel will never encounter an interruption.
| Approach | What you configure | Main ongoing responsibility | Best reason to consider it |
|---|---|---|---|
| OBS on your own computer | Image source, audio source, YouTube output and local playback | Keep the computer, power and connection available; notice failures | You want direct control and already have a suitable machine |
| DIY cloud resources, including OCI candidates | Cloud account, compute, storage, broadcast software and YouTube output | Check limits, maintain the configuration and monitor the stream | You can administer cloud workloads and accept the operational work |
| Managed playout | Media and channel settings according to the provider | Review plan terms, content and destination; escalate issues as needed | You want to avoid leaving your own computer running |
A managed option is not automatically better for every channel. If you want to experiment with OBS scene design, change sources frequently, or learn the encoding path, a local setup may be more flexible. If the channel should continue while your home computer is off and you do not want to administer a cloud environment, managed playout may be worth evaluating. For a broader view of the distinction, see YouTube 24/7 live stream services compared with a VPS.
Read free-tier limits carefully
Before relying on any free cloud tier, read the provider’s own current page for eligibility, resource availability, usage limits and account conditions. Do not assume that every advertised resource is available in every region or that a resource remains available on the same basis over time. Keep a copy of the relevant terms for your own records and revisit them before building a channel around them.
The same discipline applies to managed providers’ free trials or entry plans. Verify the channel count, media requirements, trial duration if stated, supported destination, and any restrictions on use. A trial is a chance to test the workflow, not proof of future availability or a promise that the stream will never stop. If payment, renewal or cancellation terms matter to your decision, read those terms directly rather than relying on an old comparison.
YouTube’s rules are another separate layer. A technically valid OBS scene does not settle whether your channel can use every feature or whether the content is suitable for livestreaming. Check YouTube’s current official guidance for the account and stream format you intend to use. Avoid treating an older forum post, a search snippet or a successful test as current policy for your channel.
The media itself deserves the same attention. A file playing correctly says nothing about the rights attached to it. Check the source and permission for each mantra recording and image, particularly if a playlist combines works from different owners. No technical guide can confirm that a particular recording is cleared for your use.
Estimate the work you will own
On a local computer, the daily work can be modest when everything is stable, but the setup depends on that machine remaining available. Operating system restarts, updates, audio-device changes, a home router outage or a power cut can interrupt it. You need a way to tell whether the broadcast has stopped and enough access to restore it. A scene that loops correctly while OBS is open does not restart a failed computer.
With DIY cloud resources, the computer-at-home dependency changes, but the work does not disappear. You may need to configure the operating environment, make the broadcast start after a restart, verify access to the media, and understand logs or alerts when a process fails. The exact tasks depend on your implementation. If you cannot yet explain how you would check the stream and recover it after a reboot, treat that as part of the cost of the free-resource route.
With managed playout, some operational tasks are handled by the provider, but you still own the content and the channel relationship. Check the live result, keep your source files organised, and know how to update media or respond to a YouTube-side issue. A provider’s monitoring or restart feature can reduce a particular burden; it does not transfer responsibility for every possible cause of interruption.
A simple test plan makes the trade-offs visible. Run the intended scene with the actual image and playlist, inspect the outgoing stream, and let it continue long enough to confirm that the playlist returns to the start as expected. Test how you would notice a failure and what steps you would take to recover. If the stream is important overnight, ask someone who will be available to check it, or choose a service model whose stated operation better matches your availability.
If the main problem is playlist behaviour rather than hosting, the guide to looping audio files in OBS covers the related single-file setup. For a multi-track mantra stream, keep the playlist itself understandable: use clear file names, remove obsolete versions, and document the intended order so another person can identify what should be playing.
Choose for your skills, needs and terms
Choose local OBS when control and hands-on operation suit you. The image-plus-playlist scene is straightforward to test, and you can change the files or arrangement yourself. The trade-off is that your own machine and connection remain part of the broadcast path, so it is not an unattended cloud service simply because Loop Playlist is enabled.
Choose a DIY cloud candidate only after checking the current resource and account terms and mapping the work you will do. OCI Always Free may be worth assessing if you are technically capable and willing to configure and monitor your own setup. It is a candidate for evaluation, not a proven fit for every stream and not a managed always-on guarantee. Keep a fallback plan if the account, resource or configuration no longer suits your use.
Choose managed playout when reducing the need to run your own computer or administer cloud resources matters more than direct control over the playback environment. Compare the provider’s actual plan details and constraints, and confirm that the destination is YouTube if that is where you need to broadcast. Be candid about what you still need to handle: media rights, YouTube account requirements, channel presentation and checking the resulting stream.
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
Can OBS show one still image while a playlist plays?
Yes. Add an Image source and a VLC Video playlist source to the same scene. The image stays as the visual while the VLC source plays the audio playlist; the source name does not mean it only accepts video.
Why can’t I find VLC Video in OBS?
VLC needs to be installed for the source to be available. OBS’s documentation also specifies that 64-bit OBS needs 64-bit VLC, so check that both are installed with matching bitness.
Does Loop Playlist make the stream run 24/7?
No. It repeats the playlist when it reaches the end, but it does not keep OBS, the computer, the network or YouTube online. Those need their own monitoring and recovery plan.
Is OCI Always Free enough for a 24/7 mantra stream?
That cannot be established without checking your actual workload against OCI’s current resource availability and terms. Treat it as a DIY candidate to configure and monitor, not as a confirmed fit or a managed guarantee.