To loop one MP4 on YouTube Live in OBS, add it to a scene as a Media Source and enable Loop. This can save you from converting the file separately before streaming, but OBS still encodes the outgoing live feed for YouTube.
Use Media Source for one local video. If you need several files to play as a repeating playlist, use OBS’s VLC Video source instead; it depends on VLC being installed, with a matching 64-bit version for 64-bit OBS.
Source looping is not live encoding
A loop control tells OBS what to do when a file reaches its end: play it again. It does not send the original MP4 directly to YouTube as a file, and it does not remove the live encoder step. OBS plays the media as part of a scene, then sends that scene as a live stream through an encoder connection.
That distinction is what “without re-encoding” should mean in this workflow. You may avoid a separate pre-stream conversion to make the MP4 suitable for loading into OBS. You should not assume bit-for-bit pass-through from the file to YouTube. The outgoing stream is encoded using settings compatible with YouTube’s live ingest requirements, and YouTube also transcodes live streams into viewer formats.
For example, a devotional channel can load a finished bhajan video and let OBS repeat it overnight rather than first making a second converted copy. OBS still needs to encode the live output. For other ways to organise prerecorded programming, see this guide to running a recorded lesson stream around the clock.
A file’s MP4 extension alone cannot guarantee smooth playback. MP4 is a container, and a particular file can still have codec or decoding issues on a given system or OBS build. If the picture stutters, audio is missing, or playback fails, check the file and OBS playback before changing YouTube settings.
Add one local MP4 as a Media Source
Create or select the scene that should carry the video. In the Sources area, add a Media Source, give it a recognisable name such as “Main loop”, and select the local MP4 file. OBS documents MP4 among the formats supported by Media Source. The source is intended for media playback in a scene, which is the appropriate path for one file.
Keep the source and file easy to identify. A filename such as morning-bhajans-final.mp4 is less likely to be mistaken for an earlier export than video2.mp4. Store the file in a location that will remain available whenever OBS runs, rather than on a removable drive that may be disconnected. If you move or rename the file later, revisit the source properties and select its new location.
When adding the source, choose whether it should be visible immediately if OBS offers that option. Then check the preview. If the video is larger or smaller than the canvas, use the preview’s transform controls to fit it sensibly; avoid stretching it until people or text look distorted. A portrait video on a landscape canvas may need a deliberate layout, such as a background behind it, rather than an automatic crop.
Media Source is a single-file playback choice. It is not the way to queue a folder of separate MP4s and expect OBS to cycle through each one. If your schedule needs distinct lessons, announcements, or music videos to play one after another, use a playlist-capable source and verify its order separately.
Enable Loop and verify playback
Open the Media Source properties and turn on Loop. OBS describes this setting as replaying the file when playback completes. Apply the change, then let the file reach its ending in the preview if practical. Confirm that it begins again and that the transition is acceptable; the loop setting repeats the media but does not edit out a gap, black frame, or abrupt audio ending already present in the file.
Check both picture and sound. Confirm that the source is visible in the scene and that its audio appears in the OBS audio mixer. Play a representative section with speech or music rather than relying only on the first frame. If there is no meter movement, inspect the source’s audio settings and the mixer. If there is meter activity but no sound in a local recording or test, check the audio output routing and track settings.
Pay particular attention to the file boundary. A video that fades to black for several seconds will do so on every repetition; a track that ends sharply will sound abrupt each time. If the seam is distracting, fix the edit and export a replacement file. Loop does not crossfade the end into the beginning or repair source content.
Do not treat a short preview as proof that an overnight broadcast will behave exactly the same way. It can establish that the file opens, the loop is enabled, and the audio is present. A longer test is useful for spotting repeated gaps, decoding trouble, or a scene that gets covered by another source. The test should use the same scene and settings you intend to broadcast.
Configure OBS for YouTube Live
Connect OBS to the YouTube Live event or stream using the encoder workflow YouTube provides. Keep the stream key private; enter it only in the intended OBS field, and revoke it if you believe it has been exposed. YouTube’s live encoder settings guidance covers connection setup and recommended settings. For the conventional OBS workflow, use RTMPS, which YouTube recommends as a secure extension to RTMP.
In OBS, select the YouTube service or the appropriate server and key arrangement supplied for your event. Do not assume a key from a previous broadcast is the right one for a new event: confirm the event and connection details in YouTube Live Control Room. Once connected, OBS sends the composed scene, including the looping Media Source, rather than handing YouTube the local MP4 to replay.
Choose encoder output settings with the current YouTube guidance in view. YouTube lists H.264, H.265/HEVC, and AV1 for RTMP/RTMPS live video, along with AAC or MP3 audio and constant bitrate (CBR). Its recommended keyframe interval is two seconds and should not exceed four seconds. The recommended video bitrate varies with codec, resolution, and frame rate, so use the current table rather than treating one bitrate as suitable for every channel.
For a first setup, keep the scene and output uncomplicated. A single looping video, its audio, and a stable connection are easier to diagnose than several moving layers and filters. If OBS reports encoding overload or the stream drops, check the OBS log and the output settings before concluding that the MP4 loop itself is at fault. This guide to OBS encoding overload checks explains a separate failure mode that can interrupt a stream even when a source is playing.
Check the outgoing stream requirements
A source file and a live feed have different jobs. The MP4 is the media OBS decodes for playback; the outgoing feed is what OBS encodes and sends to YouTube. Settings that satisfy one part do not automatically satisfy the other. A file may play in the OBS preview while the live connection is configured with an unsuitable codec, bitrate mode, or keyframe interval.
YouTube’s settings table supports up to 60 frames per second for the listed RTMP/RTMPS encoder settings. It specifies CBR and gives audio settings by format: for stereo, 44.1 kHz and 128 kbps; for 5.1, 48 kHz and 384 kbps, with 5.1 over RTMP/RTMPS limited to AAC. These are published encoder settings, not a promise that every source needs the highest available frame rate or surround sound. Match the output to the material and YouTube’s current recommendations.
For a simple music or ambience loop, there may be little motion in the picture, but the outgoing feed remains a live encoded stream. Low motion does not turn it into a file upload. Set the video resolution and frame rate deliberately, then use YouTube’s bitrate guidance for that combination. If you are comparing encoder settings for a continuous broadcast, this bitrate guide for a 24/7 FFmpeg stream is relevant to the ingest side, though its FFmpeg workflow is not the same as OBS.
RTMPS is the straightforward recommended route for ordinary OBS-to-YouTube streaming. HLS is not a shortcut for pointing YouTube at a looping MP4. YouTube’s HLS ingest documentation calls for a specific segment-based workflow with muxed audio and video, M2TS segments, a changing media playlist, HTTPS, and supported codecs. Google’s HLS ingestion documentation describes those requirements. Use HLS only if you are deliberately implementing that workflow, not just because a source file is an MP4.
DASH is another supported encrypted ingest protocol with its own encoder workflow. Both HLS and DASH are segment-based and generally have higher latency than RTMP. Most people trying to repeat one local video from an OBS scene do not need to choose either. YouTube’s protocol comparison is the place to check if you have a specific reason to use an alternative ingest protocol.
Use VLC Video for multiple files
If you want several videos to play in sequence, add a VLC Video source rather than treating Media Source as a playlist. OBS’s VLC Video source can load multiple files and has playlist controls, including Loop Playlist and Shuffle Playlist. Loop Playlist repeats the list; shuffle changes its order. For a planned sequence of lessons, keep shuffle off and inspect the order before going live.
VLC Video has a dependency that Media Source does not: VLC must be installed for the source to work. OBS specifically notes that 64-bit OBS requires 64-bit VLC. Install the matching architecture, restart OBS if needed, and check that the source’s playlist controls are available. If the source is blank or cannot load media, first verify VLC installation and bitness before rebuilding the playlist.
| Your need | OBS source | What repeats | Extra requirement |
|---|---|---|---|
| One local MP4 | Media Source | The single file when it finishes | Select the file and enable Loop |
| Several files in a fixed sequence | VLC Video | The playlist when it reaches its end | VLC installed; match its 64-bit version to 64-bit OBS |
| Several files in a changing sequence | VLC Video | The playlist with shuffle enabled | Check the order and resulting transitions before broadcast |
A playlist gives you more flexibility, but it also adds more places to check. Confirm that every item opens, the sequence is right, and Loop Playlist is enabled. A missing file can interrupt the intended schedule even if the first item plays correctly. For a channel built around a repeating set of recorded classes, this guide to streaming recorded coaching classes on YouTube in India offers a related planning perspective.
Preview and monitor the stream
Before a public broadcast, run a test with representative video motion and audio. Check the scene in OBS, start the connection using the intended settings, and inspect YouTube Live Control Room for stream health and incoming signal information. YouTube recommends testing before an event and monitoring stream health; its guidance is especially useful because a clean OBS preview is not the same as confirmation that YouTube is receiving a healthy feed.
During the test, check the start of the file, a normal middle section, and the loop boundary. Watch for a frozen image, a black interval, missing sound, or a visible pause between repetitions. If you have a playlist, test a transition between two files as well. Keep notes on any change you make so that you can tell whether a new issue came from the source, the scene, or the encoder output.
For an always-on channel, plan what happens when the computer restarts or OBS closes. The Media Source loop only governs playback while the scene is running; it does not itself launch OBS, reconnect to YouTube, or recover a Windows session. If you need to keep a local OBS workflow available after a restart, see how to keep an OBS YouTube stream running after a Windows restart.
If managing the local computer through the night is the specific weak point, StreamNeo can remove that particular burden: you upload the video, provide your YouTube stream key, and the channel can continue without your computer running, with monitoring and automatic restart if the broadcast drops. It is for YouTube, and it does not change the distinction between looping the source and encoding the outgoing feed. Check the current YouTube requirements and test your content before relying on any setup for a long-running channel.
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
Does OBS loop an MP4 without encoding it?
Loop makes OBS replay the local file when playback finishes, and it can spare you a separate conversion before loading the source. It does not make the live output unencoded: OBS still sends an encoded stream to YouTube using compatible output settings.
Should I use Media Source or VLC Video?
Use Media Source for one local MP4 and enable Loop. Use VLC Video when you need multiple files in a playlist; install VLC and match its 64-bit version if you use 64-bit OBS.
Does the loop remove black frames or audio gaps?
No. Loop repeats whatever is in the file, including a pause, black frame, or abrupt audio ending at the boundary. Edit and replace the file if you need a cleaner transition.
Can I use HLS to loop an MP4 on YouTube?
Not by simply selecting the MP4. YouTube’s HLS ingest path uses segments, a playlist, and specific format and codec requirements, so a normal OBS Media Source loop is a different workflow. For the usual local-file setup, configure OBS and use RTMPS as YouTube recommends.