A spare PC can run a 24/7 YouTube stream by encoding your video and sending it continuously to YouTube through an encoder application. The workable settings depend on that computer, the source video, and the upload connection, so test the exact configuration before relying on it overnight.
For a stream lasting a full day or longer, keep your own recording as well. YouTube says a stream exceeding 12 hours may not be captured at all, so the platform archive should not be your only copy of the broadcast.
What the spare PC needs to do
The spare computer has four jobs: play or produce the video, encode it, send the encoded feed to YouTube, and keep doing those things without being interrupted by ordinary power or sleep settings. It does not need to be a new machine, and there is no universal minimum specification that proves a particular old PC will run every resolution and frame rate reliably.
That distinction matters. A computer may play a video smoothly while struggling to encode it, particularly when the encoder is re-scaling the picture, adding overlays, mixing audio, or using software encoding. A different computer may encode well but lose the stream because its wireless connection is inconsistent. The only useful test is the complete arrangement you intend to leave running.
Start by checking the source material. If your devotional loop is already 720p at 30 frames per second, there may be little value in asking the encoder to create a 1080p or 60fps output. Re-scaling does not create extra detail, but it can add work for the computer. For a simple lofi or bhajan loop, a stable, modest output is often more useful than a higher setting that leaves the encoder close to its limit.
The PC also needs dependable power and ventilation. Disable sleep, hibernation and automatic shutdown for the account running the encoder, while keeping security updates and other maintenance under control. Check what happens after a power cut: some computers can be configured to start when power returns, but that is a setting to verify on your own hardware, not an assumption to make.
If the stream is important, consider connecting the computer to the router with Ethernet when that is practical. Wireless can work, but the useful question is whether the connection remains reliable in the room and at the time you plan to broadcast. YouTube’s live streaming tips recommend planning for a reliable network and testing the arrangement rather than treating a single speed result as proof of continuous stability.
The encoder application is the software that sends the computer-produced feed. YouTube’s encoder guidance identifies OBS among verified encoder options, but the choice of application does not remove the need to configure and monitor it. If you are building a playlist-based channel, the guide on making OBS automatically play the next video covers the playback part; this article focuses on keeping the feed connected to YouTube.
Enable YouTube Live before the planned start
Do this before preparing the final broadcast. YouTube says the channel must be verified and must not have had live-streaming restrictions in the previous 90 days. First-time live-streaming activation can take up to 24 hours, so enabling it shortly before your intended launch can leave no time to troubleshoot.
In YouTube Studio, open the live-streaming area and follow the activation steps. The exact labels can change, so use YouTube’s current instructions for creating a live stream with an encoder. Do not assume that an old channel is automatically ready simply because it can upload ordinary videos.
Once live streaming is available, create a broadcast or select the stream arrangement you want to use. Give the broadcast a clear title and description, choose the visibility setting, and check the audience and other channel settings that apply to your content. For the first full test, Unlisted or Private is usually more useful than making an uncertain configuration public.
A 24/7 channel also needs a plan for what viewers see if the source stops. A frozen frame, silent audio or blank scene can remain unnoticed if nobody is watching the control room. Prepare a simple fallback scene where appropriate, and decide whether the stream should end, show a holding screen, or continue with another item when the main file finishes.
If you are looping rain, music or other recorded material, make sure you have the necessary rights and permissions for the material you use. This setup guide cannot decide whether a particular recording may be broadcast. YouTube’s current rules and the rights holder’s terms remain the relevant sources for that question.
Connect the encoder with the URL and stream key
YouTube gives the encoder an ingest URL and a stream key. The URL tells the application where to send the feed; the key connects that feed to the selected channel and stream. Enter both in the encoder’s streaming settings, then save the configuration.
Treat the stream key like a password. Do not paste it into a public tutorial, send it in a group chat, or leave it visible in a screenshot. YouTube describes the key as a credential for connecting the encoder, and its stream settings guidance includes controls for managing and resetting keys.
If a key is exposed, reset it rather than hoping that nobody will use it. A reset means that any encoder still using the old key will stop connecting until you update it. Keep a private note of which computer and configuration use each key, especially if you operate more than one channel.
Some stream arrangements let you reuse a custom key. Reuse can be convenient when the same spare PC will handle the same channel repeatedly, but it also means that the key deserves the same protection each time it is copied. Before starting, check that the selected broadcast in YouTube Studio is the one you intended to connect.
For the transport and output format, follow YouTube’s current encoder settings rather than copying a preset from an unrelated channel. YouTube recommends RTMPS for standard encoder streaming and lists H.264, HEVC and AV1 video, with AAC or MP3 audio. Not every old computer or encoder supports every codec, so choose one that both the application and the machine can actually produce.
Choose a sustainable resolution, frame rate and bitrate
There are three linked decisions: the size of the picture, how many frames it contains each second, and how much data the encoder sends. Higher settings can require more encoding capacity and more upload bandwidth. A spare PC is not made more capable by selecting a larger number in the output menu.
YouTube’s guidance lists these H.264 bitrate recommendations for the following examples:
| Output | YouTube H.264 bitrate recommendation | What changes for the spare PC |
|---|---|---|
| 720p at 30fps | 8 Mbps | Lower picture size and frame rate generally reduce the work and upload demand compared with higher outputs |
| 1080p at 30fps | 14 Mbps | More picture data and encoding work than 720p at 30fps |
| 1080p at 60fps | 17 Mbps | More frames per second, with additional encoding and upload demand |
These are YouTube’s platform recommendations, not a promise that your computer, router or broadband connection will remain stable at those settings. Use the official encoder settings and bitrate table for the resolution and frame rate you choose, and check the table again before publishing because platform guidance can change.
Upload capacity needs headroom. YouTube advises leaving 20 per cent room above the chosen stream bitrate. In practical terms, do not treat an upload test that barely reaches the target as a safe operating margin. Results can vary during the day, and other devices may use the connection while the stream is running. YouTube states the same principle in its streaming tips: “Leave a bit of room (20% recommended).”
Suppose the source is a slow-moving 720p loop and the computer is modest. Starting at 720p and 30fps may be a sensible test configuration, using the platform’s recommended bitrate as a reference while confirming that the connection has additional capacity. If the encoder reports overload or the network repeatedly falls behind, lower the output or investigate the cause rather than assuming the stream will settle by itself.
Frame rate deserves particular attention for loops. A still background with gentle movement may not benefit from 60fps, while a local news loop with scrolling text can need careful testing to keep text readable. The article on when 30fps beats 60fps for 24/7 loops explains the trade-off in more detail.
Use constant bitrate, or CBR, where the YouTube settings call for it. YouTube’s standard guidance also recommends a two-second keyframe interval and says it should not exceed four seconds. Set the option in the encoder, then confirm that the application has not replaced it with a profile intended for ordinary recorded video.
Audio needs a separate check. A stream can have a healthy picture and still be unusable because the audio is silent, distorted or much too loud. Play the source through the encoder, watch its audio meters, and listen to the actual stream preview with headphones before leaving it unattended.
Test privately and inspect the preview
Do not make the first overnight attempt your first real test. Use a Private or Unlisted broadcast, load the same type of video and audio you plan to run, and let the encoder operate long enough to expose the likely problems. A short test cannot prove that a system will run indefinitely, but it can reveal wrong keys, missing audio, an overloaded encoder, or a connection that cannot hold the selected bitrate.
Test the actual content, not just a blank colour scene. A devotional video with animated text, a rain video with a moving background, and a local news loop with captions place different demands on the encoder. If the final channel uses a playlist, allow the playlist to move between items during testing so that a transition does not reveal a missing file or incompatible scene.
In YouTube Studio, inspect the Live Control Room preview before making the broadcast public. Check that the picture has the expected shape and resolution, the audio is present, and the stream is attached to the intended title and visibility setting. YouTube’s encoder guidance also recommends checking the stream page and access from suitable devices as part of preparation.
Watch for warnings in both places. YouTube may report an insufficient bitrate or an unstable connection, while the encoder may report dropped frames, skipped frames or encoding overload. These messages point to different problems. Network-related drops suggest the upload path is struggling; encoding overload suggests the computer cannot produce the selected output in time.
Repeat the test after changing one major setting. If you lower resolution, alter the frame rate and change the bitrate simultaneously, you will not know which change solved the problem. Keep a small note of the settings and the result. That makes it easier to return to a known configuration after an update or accidental change.
Monitor stream health during operation
A 24/7 stream is not simply a video file left open. It is a chain involving the power supply, operating system, playback application, encoder, local network, internet connection and YouTube ingest. Any part can fail without the other parts being at fault.
Keep YouTube Studio’s stream health view available on another device or check it at planned intervals. Look for changes in bitrate, connection warnings, dropped frames and picture or sound errors. If nobody is available to watch continuously, arrange checks around the first hours of operation and after any change to the PC, router or source files.
The spare PC should not be used for unrelated heavy tasks while it encodes. Large downloads, cloud synchronisation, video editing, games or scheduled backups can compete for processing, storage or upload capacity. A dedicated local account and a simple startup routine can reduce accidental changes, although they cannot eliminate hardware or network failures.
Make the environment easy to inspect. Label the power lead and network cable, keep the encoder scene and stream settings documented privately, and record the steps for restarting the application. If you need remote access, secure it separately and avoid exposing the stream key in screenshots or logs.
A restart plan is more useful than a claim of automatic recovery. Decide what you will check first: power, internet access, encoder status, YouTube stream health, then the source file or playlist. If the connection drops, allow the encoder to reconnect only if its behaviour is understood. Some failures require manual intervention, and a spare PC does not guarantee uninterrupted uptime.
If you regularly compare local encoding with another operating model, the guide to OBS on a spare PC versus a VPS sets out the practical differences. A spare PC gives you direct control over the machine and local files, while it also leaves you responsible for its power, maintenance, network and physical location.
Record locally and understand the archive limit
YouTube’s automatic archive is useful, but it is not a dependable sole preservation plan for a continuous broadcast. YouTube says streams shorter than 12 hours can be automatically archived, while a stream exceeding 12 hours may not be captured at all. Its archive live streams guidance uses this wording: “If your stream exceeds 12 hours, it may not be captured at all.”
That means a 24-hour or longer channel should record locally if retaining the complete programme matters. Configure the encoder to save a recording to the spare PC or to a separate drive, and check that the recording is actually being written during the private test. A recording indicator alone is not enough if the destination is full, disconnected or not writable.
Storage demand depends on the recording codec, resolution, frame rate, bitrate, audio settings and how long you retain the files. Do not choose a drive capacity from the stream duration alone. Estimate from the actual recording settings, leave working room for the operating system, and check the available space before starting a long session.
A portable external drive can be useful for moving or backing up the local files, but it is not automatically a solution. Confirm that the spare PC can write to it reliably, that it does not enter a power-saving state, and that the recording application has the correct destination. If one file becomes unwieldy, use the encoder’s supported file-splitting or scheduled-recording options where available.
A local recording also creates a second load on the PC. Encoding the stream and saving a recording may require additional processing or disk activity, so test with local recording enabled. If the computer cannot handle both reliably, a lower output setting or a different recording arrangement may be necessary.
For a continuous channel, you can preserve the most important material in smaller segments rather than treating one enormous file as the only archive. Keep the original local files until you have checked them, and consider copying important sections to a separate device. This does not protect against every failure, but it is safer than assuming YouTube will provide a complete replay after a broadcast longer than 12 hours.
The local recording is also useful for investigating a problem. When a viewer reports missing audio or a frozen scene, you can compare the file saved by the encoder with what appeared on YouTube. That helps distinguish a source or playback fault from an upload or platform issue.
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 leave OBS running all day on an old PC?
You can test an old PC as a local encoder, but no generic specification proves that it will sustain a chosen output indefinitely. Check encoding load, dropped frames, temperature, power behaviour, network stability and local recording with the exact content and settings you plan to use.
What bitrate should I use for a YouTube live stream?
Use YouTube’s current bitrate table for your resolution, frame rate and codec, then leave upload headroom. YouTube recommends 20 per cent room, and its listed H.264 examples include 8 Mbps for 720p at 30fps, 14 Mbps for 1080p at 30fps and 17 Mbps for 1080p at 60fps.
Will YouTube save a 24-hour live stream?
Do not rely on it. YouTube says a stream exceeding 12 hours may not be captured at all, so record locally if the complete broadcast matters.
Should I use a spare PC or another operating option?
A spare PC is useful when you already have the machine, local files and a connection you can monitor. It also leaves you responsible for power, updates, hardware, the encoder and the network; compare those responsibilities with other operating options before choosing one.