To make an always-on YouTube stream of retro gaming footage, first decide whether you are broadcasting gameplay as it happens or looping a recording. Live console gameplay usually needs a compatible capture device and computer running OBS; a prerecorded loop can instead be sent by an encoder or continuous-streaming service.
The capture route depends on the console, computer and operating system, and a working signal does not grant permission to broadcast the game or its music. Plan the technical setup, YouTube activation, rights checks and archive approach before you leave a stream running unattended.
Choose a capture route for your console
There are two different jobs people often mean by “how to stream retro games 24/7”. One is showing gameplay live while someone plays. The other is looping footage that has already been recorded. The first needs a live source and capture chain; the second needs a video file and an encoder that can keep sending it. Decide which you mean before buying equipment or setting up a channel.
For live console gameplay, the usual route is console video output to a capture device, then from that device to a computer running OBS. The console remains the source of the game; OBS combines the captured picture and sound with any overlays, commentary or other sources you choose. Whether that arrangement works depends on the console’s output and the device’s compatibility with your computer.
A capture device with passthrough can be useful if you want to play on a separate display while the computer receives the captured signal. Check the device’s documented inputs, outputs and operating-system support against your actual setup. A product category is safer advice than a model name when the console and computer are not specified: the right capture card for OBS is the one that supports both ends of your signal path.
If you already have gameplay recordings, you do not need to keep a console running merely to repeat them. You can loop a file through a continuous encoder workflow. YouTube’s encoder-options help page lists software choices for continuous streams, including Gyre as a cloud-based option for prerecorded video. That is one possible automation route, not a requirement or a rights clearance. For a comparison of local and hosted approaches, see which cloud service is easiest for a nonstop YouTube stream in India.
A locally run loop leaves the computer, source file, network connection and recovery after a failure in your hands. A cloud-hosted loop removes the need to leave your own computer encoding that file, but you still need to prepare the video, connect the channel and check the result. If your project is a sequence of recordings rather than one file, software for scheduling playlists across multiple 24/7 YouTube channels may help you think through playlist control. Do not confuse an automated prerecorded loop with a live capture of a game being played.
Check console and computer compatibility
Before purchasing a capture device, trace the signal from the exact console you intend to use. Confirm that it produces a video output the device accepts, that the computer has a suitable connection, and that OBS can see the device on your operating system. A device may be suitable for one console-computer combination and not another.
Nintendo Switch systems illustrate why compatibility needs a condition attached. OBS’s game-capture FAQ says Switch systems can use a capture device while docked. A Switch Lite cannot be docked and is not compatible with that docked capture-device path. Do not buy a capture card on the assumption that every console, or every Switch model, can send video to it in the same way.
For macOS and Linux, OBS advises preferring capture devices that support UVC, a standard intended to improve operating-system compatibility. Check the device maker’s current documentation as well as OBS’s guidance; UVC support does not make every device or connection suitable for every computer. On Windows, too, check the current driver and OBS support rather than relying on a listing that only says “USB capture”.
You may need to consider passthrough if you want to play on a display with the same console signal you capture. Check how the device routes the signal and whether the arrangement fits your monitor or television. Keep the setup simple at first: connect the console, confirm that you can play and see a picture, then add overlays or extra audio sources after the capture is stable.
If the game runs on a PC, capture may not require an external device at all. OBS describes ways to capture supported games and supported console remote-play apps running in a computer window. That is conditional on the game or remote-play application being supported and behaving correctly on your computer; it is not a universal substitute for a console capture device. The OBS guidance on capturing games and console remote-play apps is a useful compatibility check before you plan around that route.
Add the capture device or supported remote-play window in OBS
For a capture-device setup, connect the console to the device and the device to the computer, then open OBS. Add a Video Capture Source to the scene and select the capture device. If the picture does not appear, check that the device is selected, the console is outputting to it and no other application has taken exclusive control of it. Exact menus and device names vary, so follow the instructions for your device and OBS version.
For supported remote play, open the console’s remote-play application on the computer and sign in or connect as that application requires. In OBS, add an appropriate window-capture source and select the application window. This route depends on the specific console, remote-play software, operating system and capture method. Test both video and audio; a visible window does not guarantee that OBS is also receiving the game sound.
Make a short private test before arranging a long broadcast. Watch for cropping, black bars, a delayed picture, muted sound or duplicate audio. If commentary is part of your programme, check its balance against game audio. Keep a scene with only the game source available as a troubleshooting baseline, and add overlays one at a time so that a new issue has an obvious likely cause.
OBS is an encoder, not a continuous-power plan. For live play, the computer must stay on and the source must remain available while you want to broadcast. A captured game that pauses at a menu or loses its connection will still be the picture viewers receive. If the aim is a continuous channel rather than a particular play session, consider whether recorded footage better suits the schedule.
Create or reuse a YouTube Live stream
Open YouTube Studio and go to Live Control Room. Create a stream or select an existing one, then note its server URL and stream key for the encoder. Treat the stream key as a credential: do not show it in a screen recording or share it in public. If someone else sees it, replace it in YouTube Studio before sending a broadcast.
A new channel may need to enable live streaming before the planned launch. YouTube says first-time enablement can take up to 24 hours, so complete this step early and confirm that the account is eligible. Its current help page also describes channel verification, an absence of live-streaming restrictions in the previous 90 days, and a minimum age requirement of 16. Platform requirements can change; check YouTube’s current live-streaming eligibility and enablement guidance for your channel rather than treating a checklist copied elsewhere as permanent.
Choose a title, visibility and schedule that match what you are actually sending. If a viewer arrives to find a static recording loop, do not describe it as live gameplay. If the broadcast is a play session, make clear whether it is commentary, a replay or another format. A clear schedule also gives you a point to check that the stream is still wanted and the rights for the planned material remain appropriate.
Connect the encoder and send the feed
In OBS, open the streaming settings and choose YouTube or the matching service option. Enter the server URL and stream key from Live Control Room if you are using the custom configuration. Keep the key private, then apply the settings and start with a short test. YouTube’s encoder setup instructions describe the server URL and key workflow and the steps for sending an encoder feed.
Once OBS starts sending, check the Live Control Room preview before treating the broadcast as ready. A preview lets you catch the wrong scene, missing game audio or an unexpected desktop before viewers see it. Depending on the scheduled-stream workflow, YouTube may also require you to press “Go live” in Live Control Room after the preview appears. Sending from OBS and making the scheduled event public are not necessarily the same action.
For a prerecorded loop, set up the file and repeat behaviour in the encoder or continuous-streaming tool you choose. YouTube lists Gyre among options for continuous prerecorded streams; check its current terms and features directly if you are considering it. An automated loop still needs monitoring and a sensible recovery plan. StreamNeo can remove the need to leave your own computer switched on to repeat an uploaded video as a YouTube live stream, which is useful when your source is a prepared recording rather than live console play.
For an OBS-based feed, the computer, power and network connection remain part of the broadcast chain. If one fails, viewers may see a stalled picture or lose the stream. A cloud-hosted prerecorded feed changes that dependency, but it does not ensure that the file is suitable, that a rights holder will permit it or that YouTube will keep the broadcast uninterrupted. For the computer-side trade-offs in a local workflow, see how to run a 24/7 stream on Windows without leaving the desktop open.
Check the scheduled stream and live output
Review the preview for picture, sound and the correct scene. Check on a second device or browser if practical, especially if the stream is scheduled: this helps distinguish an encoder preview from the public viewing experience. Confirm that the title and schedule describe the actual programme, then monitor the first part of the broadcast rather than assuming that a successful start means the rest of the night is covered.
Decide how you will stop the broadcast. In YouTube’s scheduled workflow, end it in Live Control Room and stop the encoder as applicable. For a locally run continuous stream, stopping OBS alone and ending the YouTube event may be separate actions. Know which control ends the public broadcast, and avoid leaving a blank or unintended scene live after the intended programme has finished.
Plan archives separately from continuity. YouTube’s encoder guidance states that streams under 12 hours are automatically archived. Do not assume that an indefinitely running broadcast will become one complete automatic replay. If preserving a particular session matters, consider a shorter planned stream or a separate recording and verify the archive after ending the broadcast.
A long stream also deserves a recovery plan that matches the source. For live gameplay, decide who can check the console, capture chain and OBS if the game or computer stops. For prerecorded footage, decide how you will notice and address a stopped encoder or a failed source file. YouTube and OBS documentation explain setup, not a reliability guarantee for your individual power, network or hardware. If you are running a local encoder, how OBS and FFmpeg differ for a 24/7 stream can help you assess the software side of that choice.
Check rights and platform rules before leaving it on
A working signal path gives you no rights to the game visuals, soundtrack or other material in the stream. Check the publisher’s current rules for the exact game, platform and use you have in mind. Nintendo’s guidance, for example, covers livestreams and calls for creative input or commentary in the circumstances it describes; it also says third-party intellectual property requires the necessary permissions. Its current guidelines are Nintendo-specific, not a general licence for games from other publishers.
SEGA’s general guidance is likewise specific to SEGA products and to the conditions it sets for gameplay videos, including third-party material such as music and the need for new elements such as commentary or narration. SEGA says product-specific rules take priority if they conflict with its general guidance. Read the rules for the actual publisher and game; do not generalise one company’s permission to another company’s catalogue. The same caution applies to music bundled with a game, overlays and footage supplied by someone else.
YouTube scans live streams for matches to third-party content. It says a stream may be replaced with a placeholder or interrupted or terminated when such content is identified. A licence does not necessarily prevent an interruption: YouTube says the rights holder may need to add the channel to its Content ID allowlist. An archived stream may also receive a Content ID claim after the broadcast. Review YouTube’s copyright guidance for live streams and check with the relevant rights holder where needed. Neither an automated loop nor a capture card handles these permissions for you.
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 capture footage from my game console?
For a compatible console and computer, connect the console’s video output to a capture device, connect that device to the computer and add it in OBS as a Video Capture Source. Compatibility depends on the console, device, computer and operating system; for example, the Switch capture-device route described by OBS applies while docked, not to Switch Lite.
What capture card do I need for OBS?
There is no single model that suits every console and computer. Match the device’s input to the console’s output, check computer and operating-system support, and prefer UVC-compatible devices on macOS or Linux in line with OBS’s advice. Check current manufacturer documentation before buying.
Can I loop a video as a YouTube live stream?
Yes, an encoder or continuous-streaming tool can send prerecorded footage as a continuous feed, and YouTube lists software options for that purpose. It is different from capturing live gameplay, and it does not grant permission to stream the video, game footage or music.
Will YouTube automatically save a 24/7 stream as one replay?
Do not rely on that. YouTube says streams under 12 hours are automatically archived, so plan a separate recording or shorter broadcast if you need a complete replay, and check the archive after the stream ends.