A practical way to run a radio-style YouTube live stream from a Windows PC is to use OBS Studio: prepare a visual and a looping audio source, connect OBS to a stream in YouTube Studio, then monitor the broadcast. Treat 24/7 as an operating goal rather than a guarantee; it depends on power, Windows staying awake, a stable upload connection, playback and a workable recovery plan.
Before you build the scene, confirm that your channel can go live and that you have permission to broadcast the audio. Then run a test long enough to check the whole path, including what viewers see and hear. A setup that works for a short preview can still fail overnight if the PC sleeps, the router loses power or the playlist reaches an unexpected end.
Confirm that your channel can stream
Open YouTube Studio and check the live-streaming controls before spending time on OBS. YouTube requires a verified channel and says it must not have had live-streaming restrictions in the previous 90 days. If live streaming is being enabled for the first time, activation may take up to 24 hours, so do not leave this until the planned launch.
The current eligibility and setup steps are on YouTube’s live-streaming tips page and its encoder setup guide. Check the channel itself in Studio as well: account eligibility is not the same as confirming that a particular scheduled event is ready. If you see a restriction or a prompt to finish activation, resolve it and retest rather than trying to work around it with a different encoder.
A radio stream also needs rights for the material it carries. Use audio you created or have explicit permission to livestream, and consider whether that permission covers a recording or archive too. A consumer music subscription should not be treated as permission to rebroadcast its catalogue. YouTube scans live streams for third-party matches; a rights holder may cause matched material to be replaced, interrupted or stopped. Even when you have a licence, YouTube says the channel may need to be allowlisted by the rights holder in Content ID for the stream to proceed without a claim interrupting it. Its copyright guidance for live streams explains this distinction. For India-specific questions about a particular work or use, check the applicable rights with the rights holder or a qualified adviser; the Copyright Act text is background, not an individual legal determination.
Build a simple OBS radio scene
Install OBS Studio from the official OBS Project site, then create a scene for the radio channel. A scene can combine a still image or title card with an audio source. For example, a devotional channel might show the programme name and a schedule while playing a locally stored bhajan file. Keep text legible on a phone screen and avoid showing information you would not want to remain visible in a public live page.
In OBS, add a Media Source and choose the audio file. The OBS Media Sources guide documents supported local media and the Loop option for repeating a single file. If you want a rotation, use a VLC Video source with a playlist and enable Loop Playlist. VLC must be installed for that source to work; match the VLC and OBS architecture, such as 64-bit VLC with 64-bit OBS. Test the transition at the end of each track rather than assuming that a playlist will loop cleanly.
Keep media files on the PC rather than on a removable drive or a network share that might disappear during a session. Give the files clear names and keep the playlist in a known location. If the audio source is missing or changes path, OBS may no longer play it after a restart. For a repeating visual, a still image is less demanding to manage than a complex animated scene, though you may prefer motion for the channel’s style.
If you are assembling a playlist from a long prerecorded programme, the same repeat logic applies outside radio; this guide to repeating a YouTube live playlist automatically covers the general idea. For this Windows setup, make sure OBS itself is the source of the playback and that the loop has been tested in the scene.
Connect OBS to a YouTube event
In YouTube Studio, use Create → Go Live and create or schedule the stream in Live Control Room. Copy the stream URL and stream key shown for the event into OBS’s stream settings. Treat the key like a password: do not put it in a public note, screenshot or stream overlay. If it is exposed, replace it in Studio before broadcasting again.
Start streaming from OBS and look for the incoming preview and stream-health information in Live Control Room. Depending on the workflow you choose, you may then need to start the event in YouTube Studio for it to become live to viewers. Follow the on-screen state in Studio rather than assuming that pressing Start Streaming in OBS alone has made the public broadcast live. The YouTube encoder setup instructions describe how the encoder URL and key connect to a stream.
Use a conservative video format and bitrate that your upload connection can sustain. YouTube’s encoder settings guide recommends CBR and a two-second keyframe interval, and lists RTMPS as the encrypted transport option. Its H.264 recommendations are ingestion guidance, not a measurement of your home connection. For example, the listed recommended bitrate for 720p30 is 8 Mbps, while 1080p30 is 14 Mbps. These figures describe the encoder-to-YouTube stream and do not say that a broadband plan with the same advertised speed will sustain that upload continuously.
| H.264 output option | YouTube recommended bitrate | YouTube listed minimum |
|---|---|---|
| 480p30 | 4 Mbps | 0.4 Mbps |
| 720p30 | 8 Mbps | 3 Mbps |
| 720p60 | 8 Mbps | 3 Mbps |
| 1080p30 | 14 Mbps | 5 Mbps |
| 1080p60 | 17 Mbps | 6 Mbps |
Choose a target with room below the upload rate you can sustain in practice, not just a brief peak from a speed test. A fixed image with audio may not need the same visual detail as a fast-moving programme, but YouTube’s encoder recommendations still provide the relevant starting point. Run a test at the intended settings and watch the health indicator. The National Informatics Centre’s webcast service page gives 2–4 Mbps of dedicated bandwidth per stream in its own hired-agency context; that is not a YouTube setting or a universal home broadband requirement in India.
Keep Windows and playback awake
Windows power settings can undo an otherwise sound setup. On the PC, set sleep and screen behaviour so the computer does not enter sleep during the planned broadcast. A display can turn off while the PC remains awake; check that you have not configured the whole system to sleep when the screen goes dark or the laptop lid closes. For a laptop, review the lid action and keep it on a stable, ventilated surface.
Do not rely on an interactive browser tab to keep audio playing. OBS should own the scene and media source, and the files should remain available locally. Disable updates or restart prompts only in ways consistent with your normal security practice; do not assume that Windows will never request a restart. Before a long session, check for pending restarts, confirm the right audio output is selected, and avoid changing devices or logging out while the stream is running.
Power and connectivity are separate failure points. A wired Ethernet connection is a sensible choice when available because it avoids dependence on a Wi-Fi link, but it does not prevent ISP outages. If brief power cuts are a concern, consider a UPS sized for the PC and router; work out the likely load and runtime for your own equipment rather than relying on a generic capacity claim. A router on backup power cannot restore a neighbourhood connection failure, and a PC cannot keep streaming if it loses power.
For a broader prerecorded stream workflow in the same market, see setting up a 24/7 YouTube stream from prerecorded videos in India. The key difference here is that your Windows PC remains responsible for playback and encoding, so its power and sleep settings are part of the broadcast plan.
Check the upload and watch the stream
Test the actual upload path at the bitrate you intend to use. A speed test is a useful first check but only samples a moment; monitor OBS and Live Control Room while a test runs. OBS reports dropped frames when the connection cannot sustain the selected bitrate or is otherwise unstable. Its connection troubleshooting guide recommends reducing bitrate and investigating the network path when dropped frames occur.
If dropped frames continue, reduce the output target and repeat the test. Check whether other devices are uploading large files or making video calls, whether Wi-Fi signal varies in the PC’s location, and whether the issue appears at particular times. Do not raise the bitrate simply because YouTube’s table recommends a higher setting: the recommendation is not evidence that your ISP can carry it reliably. YouTube’s own guidance also recommends testing upload capacity and checking stream health before relying on a live encoder.
During the test, listen from a separate device rather than only through OBS’s meters. Confirm that music is audible, the visual is correct, and there is no clipping, silence between playlist items or unexpected desktop audio. Monitor the public or unlisted viewer experience from a phone on mobile data if practical; that helps distinguish an issue on the viewing device from one in the encoder feed. Check that the title, visibility and scheduled start are what you intended.
A local recording can help you inspect the encoded result, but it consumes disk space and needs its own management. YouTube’s live-streaming tips advise monitoring audio and video quality and checking local archive file growth. If you record in OBS, choose a destination with enough free space, verify that the file is growing during a test and decide how old recordings will be removed. That recording is a separate safeguard, not a replacement for watching stream health.
Plan recovery before the first long session
OBS can attempt to reconnect after a dropped connection, and its overview describes automatic reconnect settings. That is useful if the link briefly recovers, but it cannot restart a PC that has lost power, repair a router failure or guarantee that viewers experience no interruption. Make the recovery steps specific enough that another person can follow them if you are away.
Write down where the stream key is stored, how to check the event in Live Control Room, how to confirm OBS is playing the right scene, and who can restart the PC or contact the ISP. Keep a spare copy of the image and audio files somewhere accessible, and know how to rebuild the playlist if its path breaks. If a restart is needed, verify both the OBS preview and the YouTube event state before leaving the stream unattended again.
For a channel that cannot be watched continuously, decide what constitutes a meaningful alert: OBS stopped, the YouTube preview disappeared, audio fell silent, or the connection shows repeated dropped frames. A person who can check those signals is part of the operating plan. If you run a devotional or local information channel, agree in advance what message or slate should appear when the intended programme cannot be restored quickly; a frozen image with silence can confuse viewers more than a clearly labelled pause.
An alternative is to avoid making the local PC the sole point of failure. A cloud-based service can remove the need to keep your own computer on and can restart a broadcast after some interruptions; for example, StreamNeo turns an uploaded video into a YouTube live stream, so the PC does not need to remain powered for playback. That does not remove the need to prepare rights-cleared media, check the channel and monitor the resulting live event. If you want to compare operating models, start with cloud streaming options for prerecorded YouTube live streams and verify any vendor’s current terms directly.
Test the full route before launch
Run an upfront test before announcing a continuous schedule. Check the channel’s live eligibility, OBS scene, playlist loop, stream key, encoder settings, audio level, viewer playback and recovery steps in one session. If possible, have someone else watch from a different network and report what they actually hear and see. A preview that looks right on the production PC does not confirm that the viewer feed is sound.
Test the less obvious transitions: let one track end, allow a playlist to loop, check that the visual remains in place, and confirm that OBS reconnects after a deliberately safe short network interruption. Do not simulate a power failure during an important public stream. Instead, document what a real restart would involve and practise the restart procedure before launch. After the test, inspect the YouTube event and any local recording, then correct the specific faults you found.
If your channel depends on music, the test is also a useful point to review rights and Content ID status. A clean preview is not proof that all future tracks are cleared or that a rights holder will not claim a later item. Keep records of permissions and check how to check if music is licensed for a 24/7 YouTube radio stream before you rely on a catalogue for a long-running broadcast.
A Windows-and-OBS setup suits you if you want direct control over the playlist and visual, already have a PC and can keep power, internet and monitoring available. It asks you to manage the computer and its recovery. A cloud approach reduces that local operating burden but adds a vendor relationship and terms to check. Neither choice removes YouTube eligibility, rights or archive considerations.
Archive limits for long sessions
YouTube says streams under 12 hours are automatically archived. It does not promise a complete archive for one session that runs longer than that, so do not plan a single 24-hour broadcast on the assumption that the whole thing will be available afterwards. Check YouTube’s current encoder setup guidance before settling on an archive workflow.
If you need a dependable record of each programme, consider separate live sessions shorter than 12 hours and/or a local recording. Separate sessions mean planned transitions and more event management; local recording means disk space, file checks and a retention plan. In either case, verify the resulting archive in your own channel before relying on it for listeners, records or republishing. Archive behaviour is not the same as uninterrupted live availability.
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 I run the stream with the Windows PC switched off?
Not with OBS playing media from that PC: the computer must stay on and awake for the encoder and playlist to run. A cloud-based workflow can remove that specific dependency, but you still need to check the channel, source material and live event.
Why does OBS show dropped frames?
Dropped frames indicate that the network is unstable or cannot sustain the chosen bitrate. Reduce the bitrate, check the local network and repeat a test at the intended settings; an advertised broadband speed does not establish stable upload capacity.
Will YouTube archive a full 24-hour stream?
YouTube’s stated guidance is that streams under 12 hours are automatically archived. It does not promise a full archive for a single longer stream, so use shorter sessions or a separate local recording if keeping the full programme matters.
Does a short test prove that the stream is ready for 24/7 operation?
No. It confirms that the pieces work at that moment, but it cannot establish future power, internet or software availability. Test the playlist and recovery steps, then plan who will monitor the stream and respond when something changes.