How do I make a gaming video play in a loop on YouTube Live? You do it by adding the local gaming file to OBS as a Media Source, setting it to restart when it ends, and sending the OBS scene to YouTube as a live feed.
YouTube’s ordinary Loop or Repeat control is different. It repeats playback for a viewer on a normal video or playlist; it is not documented as a control that repeats an uploaded video inside an incoming Live broadcast. For Live, the repeated footage must be part of the feed your encoder sends to YouTube.
First, choose the workflow that matches the result
There are two different jobs that are often described as “looping a video on YouTube”. If you want to watch a published video repeatedly, YouTube’s current Help instructions describe a Loop control on a computer, a playlist Loop control for playlists, and Repeat settings on supported television or console playback. On Android, the documented path is Settings, Additional settings, then Loop video. The menu labels can change with the app or device.
That is ordinary playback. The viewer is asking YouTube’s player to repeat content that has already been published. It does not turn that content into a Live broadcast.
For a Live event, YouTube describes a feed sent by an encoder or a supported console. The encoder can share gameplay or another composed source, and YouTube receives that feed through the stream URL and stream key. The official encoder workflow explains this distinction and the connection steps.
This guide uses OBS with a gaming file already saved on your computer. Because the source is a local file, you do not need a capture card to play it in the scene. A capture card may be relevant when bringing a separate console or another physical device into a computer, but it is not a universal requirement and does not solve the loop itself.
Before preparing the event, check that live streaming is enabled on the channel. YouTube says the channel must be verified, must not have live-streaming restrictions in the previous 90 days, and the minimum age for live streaming is 16. YouTube also says first-time activation can take up to 24 hours, so do not leave activation until the planned broadcast.
Create an OBS scene for the gaming video
Install and open OBS, then create a scene for this broadcast. A scene is the composition OBS will send: the gaming footage, any text or image overlays, and the audio sources that belong with them.
Give the scene a useful name such as “Gaming loop”. This matters when you later add other scenes for a starting screen, an intermission card, a webcam, or live gameplay. A clear name reduces the chance of sending an empty or unfinished scene when you connect the event.
In the Sources area, add the source that will carry the local video. You can keep the scene simple at first. Start with the gameplay file alone, confirm that it loops correctly, and add overlays only after the basic feed works. Each extra source creates another item to inspect during testing.
If the file contains commentary, game sound, or music, decide whether that audio belongs in the broadcast. A silent video can still be a valid test of movement and picture, but it will not tell you whether your final audio mix is usable. Use a short representative section if you are testing before a longer event.
A scene also gives you a clean place to set the canvas. Match the scene and output dimensions to the format you intend to send, while following YouTube’s current encoder guidance rather than assuming one resolution or bitrate suits every connection. YouTube explains that live feeds are transcoded into multiple output formats, so viewers may receive different versions of the stream.
Add the local clip as a Media Source
In the Sources area, choose the option to add a Media Source. Name it after the file or programme, then browse to the gaming video stored on your computer. OBS will place that file in the scene as a playable source.
A local file is different from a game window or a capture device. OBS reads the saved video directly, so the computer does not need to display the original game while the file is playing. This is why a capture card is not required for this workflow.
After adding the file, look at the preview. If the picture is too small, right-click the source and use the transform options to fit it to the canvas. Check the crop carefully. A stretched image, missing HUD, or cropped subtitle may not be obvious when you are focused on the source settings.
Use a copy of the source if you want a second visual treatment, such as a background version behind a smaller gameplay window. Otherwise, one Media Source is easier to troubleshoot. Keep the source name specific enough that you can identify it while the broadcast is running.
If OBS cannot read the file, check the file path and whether the file opens normally in a local player. Moving or renaming the file after adding it can leave OBS pointing at the old location. Put the final file in a stable folder before your test rather than changing the source shortly before going live.
For a channel built around several clips, you can make separate scenes or use a suitable playlist-based workflow. Do not assume that a YouTube watch-page playlist loop will create the Live feed. The repetition must happen in the production workflow that is sending content to YouTube.
Set the source to restart when it ends
Open the Media Source properties and look for the playback controls. Enable the option that restarts the playback when the source reaches the end. In different OBS versions, the wording may refer to looping or restarting playback when the source becomes inactive. Read the option carefully and confirm that it applies to the Media Source you added.
Also check whether the source is set to play automatically when the scene becomes active. If it is not, you may need to start playback manually after switching to the scene. A manual start can be useful for a controlled event, but it adds another action that can be missed. For a simple repeated file, automatic playback is usually easier to verify.
Do not stop at the tick box. Move the playhead through the file by allowing it to reach its end, then watch whether the first frame appears again. The transition is the important test. A source can show a picture in the preview while still failing to restart at the end.
Notice what happens to the audio at the join. Some files end with a hard cut, while others have a quiet tail or a different loudness at the beginning. If the loop sounds abrupt, edit the source file or use a longer sequence with a deliberate transition. OBS can repeat the file, but it does not automatically make two unrelated ends sound like one continuous programme.
This is also a good point to check the file itself. A video that contains a frozen frame, a black gap, or a silent section near its end will reproduce that problem on every cycle. The more often a file repeats, the more visible a small defect becomes.
If you are preparing a sequence rather than one clip, test the complete sequence before connecting YouTube. For a troubleshooting reference about a stream that stops after a single file, see why a 24/7 YouTube gaming stream may stop after one video. The exact cause can be different, but the useful principle is the same: test the end-of-file behaviour instead of assuming it.
Arrange the scene and audio
Use the OBS preview to compose the final picture. The gameplay should be large enough to remain readable on the intended viewing devices. If you add a logo, channel name, schedule, or chat reminder, keep it away from important game information and avoid covering subtitles or score details.
Add text or image sources only when they have a job. A static title card can identify the game and the nature of the replay. A small label can tell viewers that the footage is prerecorded. Clear labelling helps distinguish a repeated recording from live gameplay and avoids creating the wrong expectation.
Review every source in the Sources list. Use the visibility controls to confirm that hidden items are not blocking the video and that an old webcam or microphone source is not being sent by mistake. If you are not using a camera or microphone, remove those sources or mute them rather than relying on memory.
For audio, use the Audio Mixer to identify the Media Source. Play the file and watch for movement on its meter. A moving meter confirms that OBS is receiving audio, but it does not prove that the audio is balanced. Listen through headphones for distortion, excessive game sound, missing commentary, or a music track that overwhelms speech.
If you add a microphone, monitor it separately and avoid creating an echo by monitoring the same signal through more than one path. A microphone is optional for a prerecorded loop. YouTube lists microphones, headsets, and webcams as common hardware for gaming and casual live streams, but they are not requirements for repeating a local file.
Before changing quality settings, make sure the source itself is suitable. YouTube’s current encoder settings guidance covers its recommendations for live encoding, resolutions, bitrates, and RTMPS. Available upload capacity, the movement in the game footage, and the output format all affect the sensible choice. Do not copy a single bitrate as a universal answer.
If you are building an always-on channel rather than one event, keep a written record of the scene, source path, audio sources, and output settings. That makes it easier to restore the setup after an update or a change of computer. It also makes a night-time failure easier to diagnose than a scene containing unnamed sources.
Connect OBS to YouTube
Open YouTube Studio and enter the Live Control Room. Create a new stream or select the event you have prepared. YouTube will provide a stream URL and a stream key for the encoder workflow.
In OBS, open Settings and select Stream. Choose the YouTube service if it is available in your version, or use the custom server option when YouTube’s current instructions call for it. Enter the stream URL and stream key exactly as provided. Treat the stream key as confidential: anyone who has it may be able to send content to the event.
YouTube recommends RTMPS for secure ingestion. Follow the current settings shown in YouTube Studio and its documentation rather than reusing details from an old event. If the URL, key, or selected service does not match, OBS may appear ready while YouTube receives no usable feed.
The encoder connection is separate from the ordinary YouTube Loop control. You are not asking the watch page to repeat a video. You are asking OBS to send the scene, including the repeated Media Source, as the live signal.
If your channel has not streamed before, complete the activation and eligibility checks well in advance. YouTube says first-time live activation may take up to 24 hours. Check the current live-streaming eligibility and setup information for the account requirements that apply to your channel.
For a longer-running channel, decide how you will handle the stream key. A reusable key can simplify repeated events, while an event-specific key can make separation clearer. The choice depends on how you organise the channel, but in either case keep the key out of public notes, screenshots, and shared documents.
Preview the stream and test movement
Start the Media Source in OBS and confirm that the picture and audio are present. Then start the encoder connection, but use YouTube’s preview in Live Control Room before making the event public or relying on it as your main broadcast.
The preview should show the same composition you expect viewers to receive. Look for a black screen, the wrong scene, a missing overlay, stretched video, or a source that has not started. Check the audio indicator and listen to the preview if the control room provides monitoring for your event.
Test representative movement. A static menu can look fine while fast gameplay produces rendering problems, dropped frames, or an audio mismatch. Watch a section with the motion and sound that your audience will actually see. YouTube recommends checking the stream before starting and monitoring stream health while live.
Run the file through its end if you can do so safely before the planned broadcast. The most important question is whether the first frame returns and whether the audio resumes. If the loop is long, at least test the Media Source with a short copy or a controlled sample that has the same file properties. Do not infer successful looping from a few seconds of initial playback.
Check OBS statistics during the test. A rising dropped-frame count, encoding strain, or an unstable connection needs attention before the event. Also check upload capacity and leave headroom rather than using every available part of the connection. YouTube’s streaming tips recommend testing the upload path and monitoring the feed.
Open the event from the channel or watch page as a viewer would. Confirm that it is accessible, that the title and visibility are correct, and that the picture and sound are present outside the control room. A private test can reveal a problem without sending an unfinished feed to the intended audience.
If the stream uses DVR, viewers may be able to pause, rewind, and continue from where they paused, subject to the event’s settings and YouTube’s behaviour. That viewer control is separate from the Media Source loop. It does not make the source repeat for everyone at the same point.
Start the YouTube Live stream
Once the preview is correct, the loop has been observed, and the event details are ready, start the stream according to the Live Control Room workflow. Keep OBS open and visible during the first part of the broadcast so you can see whether the source continues to move and whether the audio meter behaves normally.
Do not immediately leave the computer just because the first image appeared. Check stream health, dropped frames, encoder warnings, and the public watch page. A feed can connect successfully and still develop a problem when the source reaches its end, when the network changes, or when the computer becomes overloaded.
For a continuous channel, choose a monitoring routine that is realistic for you. You might check the event from another device, inspect OBS statistics at planned intervals, and listen for the loop join. There is no setting that replaces testing the actual file and connection.
If the broadcast stops, stop sending content from OBS after the event has stopped on YouTube, following YouTube’s ending guidance. If you are making a local recording for an archive, confirm that the recording is intact before closing OBS. YouTube’s live-streaming tips cover previewing, monitoring, checking event access, and ending the encoder feed.
StreamNeo removes the need to keep your own computer running for this particular uploaded-file workflow: you upload the video, provide the YouTube stream key, and the broadcast can run with automatic monitoring and restart handling. It is YouTube-only, so you should still check the event in YouTube and confirm that your content and channel setup meet the current platform requirements.
If you want to send the same programme to another platform as well, that is a different production decision. Read how to stream the same video to YouTube and Facebook at once before assuming that one YouTube connection covers both destinations.
For a channel made from several prepared files, plan the order and joins before you go live. An FFmpeg playlist file is another technical workflow, and how to add a playlist file to an FFmpeg YouTube stream may be more relevant if you are not using OBS. The important distinction remains unchanged: the repetition must be produced by the encoder or streaming workflow, not by the normal watch-page Loop control.
If your content is devotional, educational, or a local channel rather than gaming, the same boundary still applies. The guide to a 24/7 devotional songs YouTube channel covers a different content use case, but the practical checks are familiar: prepare the source, verify the audio, test the loop, preview the feed, and monitor the event.
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 loop a YouTube video during a live stream?
YouTube’s documented Loop or Repeat controls apply to ordinary video and playlist playback. They are not documented as a way to insert repeated uploaded footage into an incoming Live broadcast. To broadcast a repeated gaming video, put the local file in an encoder such as OBS and send the resulting feed to YouTube.
How do I repeat a video on YouTube?
For normal playback, open the video and use YouTube’s current Loop control, or use the playlist Loop control when watching a playlist. On supported devices, the equivalent may be called Repeat. That repeats playback for the viewer and is different from repeating a file in a Live production workflow.
Do I need a capture card for a local gaming video?
No. If the gaming video is already saved on your computer, OBS can add it directly as a Media Source, so a capture card is not required for that file. A capture card can be relevant when bringing video from a separate console or device into the computer, but it is not needed merely to loop an existing local file.
Why should I preview the stream if the video plays in OBS?
OBS confirms what the encoder is composing, while YouTube’s preview confirms what YouTube is receiving. The connection can have problems that are not visible in the local preview, and a file can fail at its end even after playing correctly at the beginning. Preview the event, test representative movement and audio, check the loop transition, and monitor stream health before relying on it.