If you already have a Nintendo Switch gameplay recording as a video file on your computer, you can loop it in OBS and send it to YouTube as an encoder livestream. You do not need a capture card to play that existing file, and Nintendo says direct gameplay streaming from a Switch to YouTube is not currently supported.
The practical path is to prepare the file, add it to OBS as a Media Source, enable Loop, then connect OBS to YouTube Live and check the preview before starting. A long-running broadcast still depends on your computer, OBS, network and rights to the footage; a loop does not make those concerns disappear.
Can a recorded Switch VOD stream continuously?
Yes, if “continuously” means that a video file plays repeatedly inside an active YouTube livestream. In OBS, the Media Source can replay a local file when its Loop option is enabled. OBS sends the resulting picture and audio through YouTube’s encoder workflow; the Switch itself is not sending the live signal.
That distinction matters. Nintendo’s current support guidance says Switch gameplay cannot be streamed directly to YouTube. If you already have a VOD on your computer, you can use it without acquiring the console’s signal again. If you still need to record new or longer footage from the console, a capture card can carry the console’s video to a computer for recording or encoding. It is an acquisition tool, not a requirement for looping a file.
There are also two different meanings of “continuous”. The file may repeat without interruption in OBS, while the YouTube event itself should be managed in sessions if the replay matters. YouTube says livestreams longer than 12 hours may not be captured at all, and DVR rewind may be limited or unavailable beyond that duration. Plan a deliberate end and restart before the 12-hour point rather than assuming one event will create a usable replay.
A continuous broadcast is not the same as guaranteed unattended uptime. A computer can sleep, OBS can close, an upload connection can falter, or the event can stop. Test the path and decide how you will notice and respond if it fails overnight.
Prepare the VOD as a computer video file
Start with the actual recording you want viewers to see, saved locally on the computer running OBS. Check that the file opens and plays through from beginning to end in a normal media player. Listen at the start and near the end, check that the picture is oriented correctly, and note whether the ending is abrupt or contains a pause that will be obvious when the loop returns to the beginning.
A Switch’s built-in Capture Button is not a way to produce a full-session VOD. Nintendo describes it as saving up to 30 seconds of gameplay before the button press, and some games do not support the feature. Nintendo documents transferring captures to a Windows computer using a data-capable USB cable connected directly to the Switch; the dock’s USB ports do not support that transfer feature. A microSD card is an alternative transfer route. These details may help when moving a short clip, but they do not turn the feature into a long-form recording workflow.
Keep an original copy of the VOD somewhere other than the only working location if the footage matters. Avoid renaming, moving or replacing the file after you have configured it in OBS, because the source path can then stop pointing to the right file. If you edit or convert a copy, play that copy before using it live. A full playback check is more useful than discovering a damaged ending after the stream has started.
If the VOD contains separate commentary, game audio or other material, listen to the complete mix. Check that commentary is audible over gameplay and that there is no long unintended silence. If audio and picture already drift in the source, OBS looping will repeat the problem rather than repair it; the practical checks in this guide to fixing audio and video sync in a cloud YouTube playlist stream can help you think through sync symptoms.
Be especially careful about what a repeated file contains. Nintendo’s Game Content Guidelines apply to uploads and livestreams. They encourage creative input or commentary and say creators may not simply upload or livestream existing Nintendo video or gameplay footage without their own creative or editorial input. The guidelines separately discuss gameplay captured using Nintendo system features, and third-party intellectual property may require permission. Read the current Nintendo Game Content Guidelines before putting a long or repeated clip on air. Do not assume that owning the game or making a recording settles every rights question.
Add the file to OBS as a Media Source
Open OBS and select the scene that should carry the gameplay. In the Sources panel, add a Media Source and give it a recognisable name, such as “Switch VOD”. Choose the local file. OBS’s Media Sources documentation describes the source options; labels and layout can vary a little by OBS version.
A Media Source is suited to a file that OBS should play. It is different from a capture-device source, which receives a signal from attached hardware. For an existing VOD on disk, choose the file source and do not add hardware merely because the footage originally came from a Switch.
Check the scene canvas after adding the source. Make sure the image fits the canvas without important gameplay or on-screen text being cropped. If the source is smaller than the canvas, decide whether to preserve its original proportions or adjust the layout; stretching can make the picture look distorted. Keep the preview free of desktop windows, chat overlays or other material that is not meant to be broadcast.
If you use an overlay, treat it as part of the same scene and confirm that it does not cover game information. An OBS browser overlay can be useful for a persistent on-screen element; see these browser source settings for a persistent YouTube loop stream overlay. Keep the setup simple at first. Each extra source is another element to verify when checking that the scene behaves as intended.
Enable Loop and check playback
Open the Media Source properties and enable Loop. If the source is not already playing, use the playback controls or restart the source to begin from the start. Watch the preview rather than relying only on a checked box: confirm that the file begins, the audio meter responds when sound should be present, and the final moment rolls back to the beginning.
The end-to-start transition deserves attention. If the recording ends on a menu, a silent gap or a sudden cut, that same transition will happen every time it repeats. You can edit the file to make the join less distracting, but review the complete edited version before replacing the source. If you want viewers to see a sequence rather than one repeated VOD, prepare a deliberate playlist workflow instead; a single Media Source loop simply repeats the same file.
Before connecting to YouTube, test the scene locally in OBS. Let the source run long enough to see that it continues and check several points in the recording, not just the opening frame. A short test cannot prove that an overnight session will remain stable, but it can catch an incorrect file path, muted audio, a frozen picture or an unintended crop.
Keep a local recording if you need a dependable copy of the output. The stream itself should not be treated as the only archive, especially where YouTube warns that an event beyond 12 hours may not be captured. Confirm that the computer has enough available storage for any local recording you plan to keep, and know where OBS is saving it.
Connect OBS to YouTube Live
YouTube’s encoder workflow uses a stream URL and stream key. In YouTube Studio, create or configure the live event, then enter the connection details in OBS’s streaming settings. Follow YouTube’s current encoder setup instructions, because the Studio interface and event choices can change.
Treat the stream key like a password. Do not show it in a screen recording, paste it into a public chat, or share a screenshot that exposes it. If it is exposed, use YouTube Studio’s current controls to replace or reset it. Confirm that the intended event is selected before sending the signal; a valid connection to the wrong event is still a problem.
There are channel prerequisites. YouTube says the channel must be verified and must not have a livestream restriction in the preceding 90 days. Enabling livestreaming for the first time can take up to 24 hours, so do not leave activation until the moment you plan to go live. Check YouTube’s live-streaming eligibility guidance in advance.
The computer and uplink have to carry the encoded stream throughout the session. YouTube recommends upload bandwidth with headroom; its streaming tips suggest about 20% beyond the stream bitrate. That is guidance, not a guarantee: household traffic, Wi-Fi conditions and other network changes can affect the available upload. A wired connection, where practical, and a test at the intended settings can help reveal problems before the public event.
For a low-bandwidth location, choose settings the connection can sustain rather than aiming at a higher resolution without testing. This guide to setting a church YouTube stream to 720p on low bandwidth covers the kind of trade-off to consider. Do not copy a setting blindly: the right choice depends on your file, encoder and actual upload capacity.
Preview and start the event
Once OBS is connected, wait for the stream to appear in YouTube’s Live Control Room. Check the preview carefully before starting the event. Confirm that the game picture is visible, the audio is present and balanced, and nothing private or unintended is on screen. If YouTube reports a connection or stream issue, address it before inviting viewers or promoting the event.
Use a private or unlisted test where that fits your channel and purpose. Verify that the start, playback, audio and loop transition all behave correctly. Then start the event through the Live Control Room workflow. OBS sending a signal and the YouTube event being live are related steps, but check the Studio status rather than assuming the event began merely because the encoder is connected.
For a replay that matters, set an operational limit below 12 hours and end the event deliberately before that point; start a new event for the next session. YouTube says a stream under 12 hours can be automatically archived, but longer streams may not be captured at all. It also cautions that DVR rewind may be limited or unavailable for streams longer than 12 hours. The guidance is a caveat, not an archive guarantee, so keep a local recording and verify the replay after ending.
A session break means separate live events, not one uninterrupted YouTube event. Decide how to communicate that to viewers, and whether the file should resume at its beginning or at a particular point when the next event starts. If you need a specific continuation point, test how you will seek or restart the source in OBS before relying on that method during a live handover.
While live, monitor OBS and YouTube Studio. Look for a frozen image, missing audio, connection warnings or an unexpected source stopping. A stream built from a local file removes the need to play the console live, but it does not remove the need to watch the broadcast path. For an overnight channel where leaving a personal computer running is the pain point, StreamNeo removes that computer-from-home burden by turning an uploaded video into a YouTube livestream; it does not change your responsibility to check footage rights, event behaviour or YouTube’s current rules.
Use a capture card only to acquire new footage
A capture card is relevant when you still need to get video from the Switch into a computer for recording or encoding. In that case, the console’s output is connected to capture hardware, and the computer receives it as a video source. A vendor’s AVerMedia Switch and OBS guide illustrates this kind of arrangement, but it is an example, not proof that every card will work with every computer, Switch model or software setup.
For a VOD that already exists as a computer file, the capture card contributes nothing to the loop. Use OBS’s Media Source for the file. This avoids buying or configuring a device for a job it does not do, while keeping the two workflows clear: capture new console output when necessary; play and loop an existing recording from storage.
| Your situation | Practical route | What to check |
|---|---|---|
| The full VOD is already on your computer | Add it as an OBS Media Source and enable Loop | File playback, end-to-start transition, audio and source path |
| You only have a Switch clip | Transfer the clip to the computer, then test it as a file | The built-in capture is short; confirm the clip is complete and supported by the game |
| You need to record longer or new console footage | Investigate a capture card and a suitable computer workflow | Compatibility, recording method, sound and rights for the resulting footage |
| The YouTube replay is important | Run shorter sessions, end and restart deliberately, and retain a local copy | YouTube’s 12-hour archive and DVR caveats |
| You cannot keep a personal computer running unattended | Consider an appropriate hosted prerecorded-stream workflow | Confirm platform fit, monitoring needs, current terms and your rights to the file |
The right route depends on which part of the work you already have in hand. A card helps acquire footage; OBS looping helps broadcast a file; session planning helps protect the replay. None of those steps resolves whether repeated gameplay and included music or other material are appropriate for your channel. Review Nintendo’s current rules and any relevant third-party rights before going live.
If you want a more involved computer-based automation approach, this guide to launching an FFmpeg YouTube stream after reboot discusses another encoder workflow. It is not needed just to loop a VOD in OBS, and a restart mechanism should not be mistaken for monitoring or a guarantee that a broadcast will recover correctly.
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 stream prerecorded gameplay on YouTube?
Use an encoder workflow: load the existing file into OBS as a Media Source, enable Loop if you want it to repeat, and connect OBS to a YouTube Live event with the stream URL and key. Check the Live Control Room preview and start the event there. Keep the key private and test audio and picture first.
Can I stream Switch gameplay directly to YouTube?
Nintendo’s current support guidance says direct Switch gameplay streaming to YouTube is not supported. For footage you already recorded, move the file to a computer and stream it through OBS or another suitable encoder workflow. A capture card is for acquiring new console footage, not a prerequisite for playing an existing VOD.
How long can a YouTube livestream run before it stops saving?
YouTube says a stream longer than 12 hours may not be captured at all, and DVR rewind may also be limited or unavailable beyond that duration. If the replay matters, end and restart the event before 12 hours and keep a local recording. Check the current YouTube guidance rather than treating automatic archiving as guaranteed.
Does the Switch Capture Button record a full gameplay session?
No. Nintendo describes it as saving up to 30 seconds of gameplay before the button press, and some games do not support the feature. For longer footage, you need an appropriate recording workflow; a capture card may be useful when acquiring new console footage, but it is not needed for an existing video file.