An old Windows PC can loop a playlist in OBS, but that does not mean it can decode the video, render the scene, encode 4K60 and upload continuously. Check the computer’s media support and your sustained upload headroom first; then test the complete setup rather than relying on a successful preview.
YouTube’s published 4K60 ingest recommendations differ by codec, and the surfaced English and India-localised bitrate tables may not show the same values. Confirm the current applicable recommendation in YouTube Live Control Room before setting OBS. No single bitrate or PC specification is right for every connection and machine.
Check PC capability and upload headroom
Treat the job as four separate workloads: decoding each source file, composing the scene, encoding the outgoing stream and sending it to YouTube. A PC can handle one of these and still fail at another. For example, a graphics card may have a hardware encoder but lack hardware decoding for the playlist’s codec; alternatively, it may decode the footage but struggle to encode a 4K60 scene at the chosen settings.
Start with the PC’s Windows version, processor, graphics hardware and available memory. Identify the exact GPU rather than relying on a general label such as “Intel graphics” or “gaming PC”. Check whether it supports hardware decoding of the file’s codec and hardware encoding of the intended output codec. OBS explains that hardware encoding moves work from the CPU to a specialised GPU component, but the options available depend on the installed hardware and software. That reduces one burden; it does not establish that the whole system can sustain the workload.
Next, inspect the video files you plan to loop. Note resolution, frame rate, codec and audio format. A 4K60 output does not make a lower-resolution source into native 4K, and a 4K source does not necessarily need to be re-encoded if it already matches the intended stream. If OBS must scale or convert source files, that adds work. The video format guide for a 24/7 stream is useful when you are deciding what to prepare before building the scene.
Measure upload, not download. Run a speed test that reports upload and repeat it at the times the channel is expected to run, including busy evening periods if that is when your connection is most contested. YouTube specifically recommends testing upload bitrate and monitoring stream health. A single good result is not proof of a stable connection through the night.
Compare the measured upload with the encoder bitrate you intend to use, allowing room for normal variation and other household or business traffic. Do not treat YouTube’s encoder recommendation as an ISP requirement or as a guarantee that an Indian broadband connection will hold it. If upload varies, other devices share the line, or the route to YouTube is unstable, the appropriate response may be a lower resolution or frame rate rather than forcing 4K60.
| Decision point | What to check | What it tells you |
|---|---|---|
| Source decode | File codec, resolution and frame rate; GPU decode support | Whether OBS can read the playlist without overloading the machine |
| Output encode | Available OBS hardware and software encoders | Whether the PC can produce the selected codec and frame rate |
| Upload | Repeated sustained upload measurements and competing use | Whether the connection has headroom for the chosen bitrate |
| Long run | Dropped frames, encoder overload and connection stability | Whether the whole setup remains usable beyond a short test |
If the system is already near its limit during an ordinary playback test, adding OBS, scaling and continuous encoding is unlikely to improve matters. A different machine, a lower output target or hosted looping may be more practical than replacing parts without first identifying the bottleneck.
Prepare the prerecorded video
Make a copy of the playlist files in a dedicated folder, and avoid changing or moving them after you have configured OBS. Consistent naming makes it easier to see what is playing and to restore the list if a drive letter or path changes. Keep the original files elsewhere as a backup.
Check that every item has the intended audio and picture. A silent clip, unexpected black lead-in or very different frame rate can be more noticeable when the same sequence repeats for hours. Play each file locally and listen through transitions. If the programme is intended to be continuous, decide whether gaps or a long fade at the loop boundary are acceptable before going live.
For an old PC, avoid unnecessary conversion. Transcoding a large source library can consume time and may reduce quality; leaving every file in a different format can also make playback behaviour harder to predict. If you need to standardise files, choose a format the computer can decode efficiently and test the resulting files in OBS. OBS’s media sources documentation describes the VLC video source and its available controls. Its VLC playlist support is a playback feature, not a certification that the computer can handle every source.
Put the files on a local drive with enough free space and stable access. A removable drive can work, but a loose cable, sleep setting or drive disconnect can stop playback. Set Windows not to sleep during the planned broadcast, while retaining a sensible screen-off setting if you do not need the display. Ensure power settings do not suspend the PC or its network adapter.
Configure OBS for continuous playback
Install OBS Studio and VLC, then open OBS and create a scene for the channel. Add a VLC video source and use its playlist controls to add the files in the order you want. Enable the loop playlist option so playback starts again when the final item finishes. As described in OBS’s documentation, VLC must be installed for this source type to work.
Use the source’s hardware-decoding option only if the GPU supports decoding the media format. Test both ways if playback stutters: hardware decoding can reduce CPU demand on a supported GPU, but it is not a universal fix for old hardware or unsupported codecs. Watch OBS’s performance indicators while a demanding section plays. If CPU use, rendering lag or dropped frames rise, simplify the scene and remove filters, browser sources and animated overlays you do not need.
Set the canvas and output resolution deliberately. If the source is 4K and you want a 4K stream, keep the scene simple and test scaling behaviour rather than assuming OBS will pass every file through untouched. A collection with mixed resolutions or frame rates may need conversion or scaling. That work can burden older processors and graphics hardware.
In Output settings, select an encoder the installed hardware actually offers. A GPU hardware encoder can move encoding work off the CPU, as OBS’s hardware encoding guide explains. If the encoder is unavailable, update or check the relevant graphics driver and OBS version, but do not assume a software encoder will be viable at 4K60 on an older processor. Test the exact output profile you plan to use.
Configure the stream for constant bitrate (CBR), up to 60 frames per second, and a two-second keyframe interval. YouTube’s encoder guidance says the keyframe interval should not exceed four seconds and recommends RTMPS where supported. These are ingest settings, not a promise that a particular computer or connection can maintain them.
Save the OBS profile and scene collection when the test configuration works. For unattended use, arrange for Windows and OBS to recover predictably after a restart, but remember that automatic launch is not the same as a successful stream. The guide to restarting an OBS Indian music stream automatically covers a related recovery problem; still test your own PC after a restart and after a network interruption.
Choose a 4K60 codec and bitrate
YouTube’s current encoder-settings guidance lists different recommended 4K60 ingest rates for different codecs. In the English page surfaced in research, the recommendations are 35 Mbps for AV1 or H.265 and 50 Mbps for H.264. These figures are not interchangeable: do not apply the AV1/H.265 value to an H.264 stream.
The English and India-localised bitrate tables surfaced for this topic differ. Before entering a figure, open the current applicable guidance in Live Control Room for your channel and confirm the codec row and resolution/frame-rate row shown there. Use the current value for the actual output codec, not a number copied from another locale, an older tutorial or a different frame rate. YouTube’s encoder settings and bitrate guidance is the primary reference; check the current control-room display as well.
| Output codec | YouTube’s surfaced English-table 4K / 2160p at 60fps recommendation | Practical implication |
|---|---|---|
| AV1 or H.265 | 35 Mbps | Use only if the chosen encoder supports the codec and YouTube’s current applicable table confirms it |
| H.264 | 50 Mbps | A higher ingest target than the surfaced AV1/H.265 recommendation; verify the line connection can sustain it |
These are YouTube recommendations for ingest, not an India-specific ISP threshold and not a measured promise of viewer playback quality. The bitrate is only one part of the path. A connection that briefly reaches the target but fluctuates, or is shared with other traffic, may still produce stream-health warnings. If your measured upload lacks steady headroom, consider 4K30 or a lower resolution/frame rate. The table and guidance should be checked again before a real broadcast because settings and localised pages can change.
Choose the codec based on what both the PC and YouTube ingest path support. H.264 is common, but its higher surfaced 4K60 recommendation can make upload headroom a concern. AV1 or H.265 may suit a supported encoder and ingest configuration, but availability varies by hardware and software. Do not choose a codec solely because its listed bitrate is lower: the old PC must encode it continuously and YouTube must accept that format for the selected workflow.
Create the YouTube Live event
In YouTube Studio, create a live stream or schedule an event, then select the intended stream settings. Confirm that the channel and event are the right ones before you connect OBS. A recurring prerecorded playlist still needs a live event configured for the expected resolution, frame rate and latency choices.
At 4K/2160p, YouTube says the option to improve for low latency is not available. Do not build the plan around a latency choice the resolution does not offer. For a playlist channel, a modest delay is often less important than stable ingest and a clean, uninterrupted picture.
Keep the stream private or unlisted while testing if that suits your workflow, and check the event details before changing its visibility. Do not assume a successful OBS connection means that the public event is already using the intended title, thumbnail or audience setting. A brief review in Studio prevents avoidable mistakes before viewers arrive.
Enter the stream destination and key
Copy the server URL and stream key from YouTube Studio into OBS’s stream settings. Use RTMPS when the encoder offers it, following YouTube’s recommendation for secure ingest. Treat the stream key as a password: do not publish it in a screenshot, paste it into a public support post or reuse a key carelessly across unrelated setups.
YouTube may offer a primary and backup ingest destination, but follow the current instructions shown for your event rather than guessing which address to use. The key identifies where OBS sends the feed; the event’s status and stream health are still checked in YouTube Studio. If the Live Control Room reports no data, check the selected server, key, event association and whether OBS is actually streaming before changing multiple encoder settings at once. The RTMP checks for a “No data” message can help distinguish a destination problem from an encoding problem.
If a key may have been exposed, replace it in Studio and update OBS. When diagnosing connection trouble, change one item at a time and note what changed. That makes it easier to undo a mistaken bitrate, server or key edit.
Preview and test before relying on it
Start OBS and wait for YouTube Studio to receive the feed. Check the preview for the correct playlist, framing, audio and event. Review stream health rather than stopping at the first image. YouTube recommends pretesting and monitoring stream health; an image in the preview proves only that a feed arrived, not that it will remain stable overnight.
Test a section with the most motion and the loudest or most complex audio in the playlist. Watch OBS for dropped frames, rendering lag and encoder overload, and watch the PC’s temperatures and behaviour over a longer trial. A short test cannot prove continuous reliability, but it can expose obvious bottlenecks before you announce a channel.
Also test the network under realistic conditions. Run the stream while the other expected devices or business traffic are active. A connection that looks adequate when the household is quiet may behave differently when it is busy. Do not use download speed as a substitute for upload measurement, and do not treat a single speed-test result as a guarantee.
Check what happens when the playlist reaches its end, when OBS is restarted, and after a controlled network interruption. Confirm that the loop resumes, OBS reconnects as expected and the Live Control Room recovers. A restart method that works on one Windows configuration may not work after a driver update or a power interruption. Record the steps you used so someone else can check the channel if you are away.
If the old PC cannot sustain the decode, encode and upload workload, do not keep forcing the same 4K60 profile. Reduce the target, upgrade only after locating the bottleneck, or consider a hosted loop if the main requirement is that your computer can be switched off. A hosted service still needs a compatible source, current terms and verified support for your intended resolution and frame rate. StreamNeo can remove the specific burden of keeping an old Windows PC running to feed a continuous playlist, but check its current capabilities and terms for your 4K60 use rather than assuming every file or channel requirement is covered.
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 an old PC run a 4K60 YouTube Live playlist?
Possibly, but age alone does not tell you whether it can decode the playlist, render the scene and encode the selected format at 4K60. Check the exact GPU and media codec support, then test OBS with representative footage for a sustained period. If it overloads, a lower output target or another operating path is more sensible than assuming a settings change will solve it.
Is 35 Mbps the right bitrate for every 4K60 stream?
No. The surfaced English YouTube table recommends 35 Mbps for AV1/H.265 and 50 Mbps for H.264 at 4K60, and the India-localised table may differ. Confirm the current applicable codec recommendation in Live Control Room and measure sustained upload with headroom before relying on the stream.
Does OBS looping mean the stream will keep running overnight?
No. Loop Playlist restarts playback after the listed files finish, but Windows, OBS, the decoder, encoder, power and internet connection can still fail. Test the whole path, including a restart and network interruption, and monitor stream health during a longer trial.
What if my upload or PC cannot sustain 4K60?
Try a lower frame rate or resolution and retest the actual output and connection. You can also identify whether decoding, encoding or upload is the limiting factor before considering an upgrade or hosted continuous loop. No single alternative is best for every channel, so compare the ongoing effort and cost as well as the technical fit.