A spare PC can act as a dedicated encoder for an always-on YouTube gaming stream. Install OBS Studio, add the game and audio sources, connect YouTube with a stream key, choose settings the machine and connection can sustain, then test and monitor the broadcast.
The PC does not create gameplay by itself. It must either run a game and capture it live, or play approved prerecorded footage in a loop. Those are different workflows, with different rights, reliability and monitoring requirements.
Decide whether you need live gameplay or a rerun
Start by defining what viewers should see. In a live gameplay setup, the spare PC runs the game, captures its output and sends the changing picture to YouTube. Someone, or an automation arrangement you have tested, must keep the game producing useful video. A paused game, a disconnected controller or a login prompt can leave the stream technically live but practically empty.
A rerun uses prerecorded gameplay, highlights or another video file as the source. OBS can play media files, but a continuous archive raises separate questions: do you own the footage and music, is the licence suitable for public streaming, and will viewers understand that the video is not live? YouTube’s encoder guidance also describes cloud-based 24/7 streaming of prerecorded video as a use case, so a cloud workflow may be more suitable when playback, rather than local gameplay, is the real requirement.
| Your intended result | Suitable local-PC workflow | Main concern |
|---|---|---|
| Live play with changing inputs | Run the game on the spare PC and capture its window or display | Game performance, heat, input and operator presence |
| A repeatable highlights channel | Add owned or licensed video files to OBS | Rights, repetition and archive management |
| A long prerecorded broadcast | Use a tested media playlist or compare a cloud service | Local power, internet, relaunch and monitoring |
| Console gameplay | Use the PC as an encoder with suitable capture hardware | Capture-card compatibility and signal handling |
Do not buy a capture card just because you are using a spare PC. It is relevant when the gameplay comes from a separate console or computer. If the game runs on the same PC, OBS can usually capture the game, a window or the display directly, subject to the operating system and game’s behaviour.
If your plan is mostly a playlist, consider the practical differences before you build the channel around OBS. A local machine gives you direct control over files and scenes, but it remains dependent on local electricity, the internet connection and the computer staying healthy. For a broader comparison of continuous playback choices, see how to stream a playlist to YouTube Live using OBS.
Check channel eligibility before installing everything
YouTube requires the channel to be verified and free of live-streaming restrictions from the previous 90 days. Check this before spending time on scenes, overlays or a long test. The current YouTube Help instructions for getting started with live streaming explain the activation and eligibility process.
When live streaming is enabled for the first time, activation may take up to 24 hours. That is a possible waiting period, not a promise that every channel will be approved or ready immediately. Start the process early, and check the channel in YouTube Studio rather than assuming that a successful OBS installation means the channel can broadcast.
The 90-day restrictions check matters even if the spare PC is ready. A channel can have a working camera, encoder and internet connection and still be unable to start a live broadcast because of an account restriction. Review the current official YouTube page before publishing your schedule, as account requirements and interface wording can change.
You should also decide who owns the stream key and who can access the channel. Treat the key as a credential. Do not paste it into a public document, send it in a group chat or include it in screenshots. If you think it has been exposed, replace or reset it in YouTube Studio and update OBS.
Install and prepare OBS on the spare PC
Download OBS Studio from the OBS Project quick-start guide, then run its Auto-Configuration Wizard on the spare PC. The wizard considers the intended use, hardware and network conditions. It is a starting point, not a guarantee that the machine can play and encode a demanding game at the same time.
Install OBS on the PC that will actually run the game and broadcast. A laptop used for occasional testing may behave differently from a desktop left near a router. Before creating a polished layout, let OBS identify the available encoders and inspect the preview while the game is running.
Create a simple first scene rather than beginning with several animated overlays. A useful starting scene might contain:
- the game capture or display capture
- desktop or application audio, if needed
- microphone input, if someone is speaking
- a small text or image overlay only if it serves the viewer
Name sources clearly. “Game Capture - Main”, “Microphone - USB” and “Music - Licensed” are easier to troubleshoot than several entries called “Audio Input Capture”. Keep a plain fallback scene available so you can remove a troublesome browser source or overlay without rebuilding the broadcast.
Check the OBS system requirements, but do not read compatible requirements as a performance guarantee. OBS notes that the load depends on the encoder, output resolution, frame rate and scene complexity. A machine can run a game acceptably while failing to render or encode the stream smoothly because the game and OBS are competing for the same resources.
Before leaving the setup unattended, review practical PC behaviour as well. Disable sleep only after checking the settings for the operating system you use, prevent unexpected updates during your planned broadcast window where your normal maintenance policy allows it, and make sure the computer can reconnect to the network after a restart. These are operational precautions, not YouTube requirements, and they need to be tested on your own machine.
Add the game, video and audio sources
For live gameplay, add a Game Capture source first when it works reliably with the title you are running. Select the intended game rather than capturing the entire desktop where possible. Window Capture or Display Capture can be useful fallbacks, but they may expose notifications, unrelated applications or private information.
Open the game and confirm that the preview changes when you move through the game. Look for a black preview, a frozen frame, missing menus or a cursor that viewers should not see. Test a demanding scene rather than only the title screen. The encoder must handle the actual movement and effects that your audience will watch.
For prerecorded gameplay, add a Media Source and point it at a file you own or are licensed to show. Test whether the file ends, loops, changes aspect ratio or produces a gap between items. If you use a playlist, play through the transition between two files. A short black screen may be harmless in a test but confusing when repeated throughout a long broadcast.
Audio needs its own check. Watch the mixer meters while the game produces sound and while a microphone is speaking. Make sure the intended source is present once, not twice through both desktop audio and an additional application capture. Duplicate audio can create an echo that is difficult to notice on a small speaker but obvious to viewers wearing headphones.
Keep game audio below the level at which speech disappears. If there is no presenter, the game audio still needs to be steady rather than jumping sharply when a menu opens. Listen to the stream preview or a separate test recording instead of relying only on the mixer moving.
Music, sound effects, gameplay footage and overlays can each have separate rights. A game being installed on your computer does not automatically grant permission to rebroadcast every soundtrack or clip in every context. Keep records of the licences or permissions for prerecorded material, and check the current YouTube rules for your channel and content.
If YouTube receives video but no sound, work through the source and mixer methodically. The guide on YouTube Live having no sound over RTMP is useful when the local meters appear active but the public broadcast is silent.
Connect YouTube to OBS safely
In YouTube Studio, create or select the live stream and locate the stream URL and stream key. In OBS, open the stream settings, select YouTube or the appropriate custom service option, and enter the values in the matching fields. YouTube describes the stream key as the address and password that allow the encoder to send the broadcast, so protect it accordingly.
Check the destination before starting. A test sent to the wrong channel can still be a successful technical test, but it is a serious publishing mistake. Confirm the channel name, title, visibility, audience settings and category in YouTube Studio before you begin.
Use RTMPS when the available YouTube and OBS settings support it. YouTube’s encoder streaming documentation covers the current connection process, supported settings and stream-key workflow. Interfaces change, so follow the labels shown in your account rather than relying on an old screenshot.
Start with the stream set to private or unlisted when you need to inspect the complete path. This lets you check the YouTube watch page, video and audio without announcing an unfinished broadcast to your audience. A private test is not a substitute for checking the account’s real live-stream eligibility, but it can expose source and connection problems before a public start.
Choose an output profile the PC can sustain
The best profile is not the highest setting the software offers. It is the setting that leaves enough headroom for the game, OBS, scene composition and normal network variation. Test with the game running at the same resolution and visual intensity you expect during the real broadcast.
OBS may offer hardware encoding through the graphics card or other compatible hardware. Hardware encoding can reduce CPU pressure, but older hardware encoders may produce lower image quality than a modern alternative. Compare the available encoder choices during a real test rather than assuming that either “hardware” or “software” is always better.
Change one major variable at a time. If the stream struggles, reduce output resolution or frame rate, simplify the scene, reduce the game’s load, or choose a more suitable encoder. Changing resolution, frame rate and bitrate simultaneously makes it harder to identify the cause.
| Setting choice | What it changes | What to check |
|---|---|---|
| Higher output resolution | More visible detail and more work for the encoder and connection | GPU or CPU load, upload stability and readable motion |
| Higher frame rate | Smoother movement and more frames to encode | Whether the game and encoder maintain it consistently |
| More complex scenes | Additional browser, image, animation or capture work | Rendering warnings and preview smoothness |
| More conservative profile | More headroom for a marginal PC or connection | Whether text and fast gameplay remain clear enough |
YouTube provides current bitrate and encoder guidance in its live-stream settings documentation. Use that as the reference for your chosen resolution, frame rate and codec, then test your actual upload connection. The configured bitrate must be sustainable for the whole path from the spare PC to the ingest service, not merely achievable for a brief speed test.
If OBS reports rendering or encoding overload, the problem may be the game rather than the internet. Lower the game’s frame rate or graphics load, simplify the OBS scene, reduce the output or use a suitable hardware encoder. If OBS reports dropped frames or intermittent disconnections, investigate the network path and bitrate. Those symptoms generally point to a connection problem between the PC and the ingest server, although local hardware and drivers can complicate diagnosis.
A wired connection is often easier to troubleshoot than a marginal wireless connection, but it does not guarantee a stable broadcast. Watch the connection during the hours when the stream is meant to run. A spare PC that works beside the router may behave differently when moved to another room.
Test the complete broadcast before leaving it alone
Do not treat the first public launch as the test. Run a short private or unlisted broadcast with the game, scenes, audio and output settings you intend to use. Check the OBS preview, YouTube’s stream health, the public or test watch page and the recording produced by the test.
Ask another device to watch the stream. A phone on a different connection can reveal a delay, missing audio or an inaccessible watch page that is not obvious from the encoder PC. Confirm that the picture remains in motion, the sound stays synchronised and the title and thumbnail are correct.
Exercise the failure points you can safely test. Stop and restart the game source, disconnect and restore the network if your setup permits it, and observe what OBS and YouTube report. Do not assume that a reconnect setting will solve every crash, power interruption, driver failure or router problem. Read what should happen when the ingest drops and decide what your own escalation or restart plan will be.
YouTube recommends testing, monitoring stream health, confirming that the event is accessible and checking that local archive files grow. Keep a local recording only if the PC has enough storage and performance headroom. Recording can add load, and a local file is not a replacement for checking the actual YouTube broadcast.
Streams under 12 hours are automatically archived according to YouTube Help. Do not assume that one stream longer than that will be preserved in full. If the footage matters, use a separate recording plan and check the current YouTube archive guidance before relying on the live replay as your master copy.
An always-on stream still needs an owner or alerting plan. Check it at intervals, watch for a frozen game, muted audio, dropped frames and an ended broadcast, and decide who will respond when something fails. A desktop UPS may help with a short power interruption, but it cannot repair an internet outage or a software failure.
If the real goal is a continuous prerecorded channel and you do not want to maintain a powered PC, compare that requirement with a cloud streaming workflow. StreamNeo is intended for the specific nuisance of leaving your own computer running: upload the video, add the YouTube stream key and let the broadcast run while the computer is switched off, with monitoring and automatic restart for drops. It is YouTube-only, so it is not a substitute for a encoder or a live game that must run locally.
Keep a simple operating note beside the PC. Record the channel, scene collection, intended source, encoder profile, stream-key reset procedure and the checks to perform after a restart. This is more useful than relying on memory when the stream fails at an inconvenient hour.
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
How do I use an old PC to stream on YouTube 24/7?
Install OBS, add the game or approved prerecorded source, connect YouTube with the stream URL and key, and choose an output profile the PC and upload connection can maintain. Test the complete broadcast before leaving it unattended, because running a game and encoding it can overload a machine that appears capable during ordinary use.
Can I leave OBS running all the time?
You can leave OBS running, but that does not mean every failure will recover automatically. The PC can lose power, the game can crash, the network can disconnect or audio can stop, so use testing, monitoring and a response plan rather than assuming the process is self-managing.
Can I loop prerecorded gameplay on YouTube Live?
You can build a prerecorded workflow with OBS, but check that you own or are licensed to use every video and audio element. Test file transitions, avoid presenting a rerun as live gameplay, and consider whether a cloud playback service is more suitable than keeping a spare PC powered continuously.
Will YouTube save a 24/7 livestream?
YouTube says streams under 12 hours are automatically archived. Do not rely on a single stream longer than that being preserved in full; use a separate local recording plan when the material must be kept and check the current official archive guidance.