For a straightforward product-video loop on YouTube Live, use an MP4 as the local file in OBS, enable Loop on its Media Source, and send H.264 video with AAC stereo audio to YouTube. The MP4 is the source file OBS plays; it is not the format of the encoded live stream that OBS sends.
That distinction matters when a video plays locally but viewers hear nothing. Check the file, OBS audio meter and routing, then the outgoing encoder and YouTube’s stream health. MP4 is a practical supported source choice, not a cure for every audio fault.
Choose a local product-video source file
Start with the video you want OBS to play, rather than treating a filename extension as a full streaming setup. MP4 is a useful default for a product loop because OBS supports it as a Media Source, and YouTube also lists MP4 among supported upload formats. YouTube’s upload recommendations and its live encoder recommendations describe different stages, so an upload profile does not define the live output.
Before opening OBS, play the exported file on the same computer and listen through the full duration. Confirm that the intended soundtrack, narration or product demonstration audio is actually present. A video can look right while containing a silent or unintended audio track. If the file has several audio tracks, identify which one should be heard; do not assume the first track is the intended one.
Use an export with dimensions and frame rate suited to the material and to the live profile you can sustain. A rotating product on a plain background may not need the same visual detail as small text in a close-up demonstration. Keep labels legible, avoid unnecessarily fast cuts, and inspect the picture at the resolution viewers are likely to use. YouTube’s bitrate examples are recommendations, not a promise that a particular connection will carry them reliably.
MP4 is not the only conceivable container or source workflow. The relevant test is whether the media software you choose can read and loop the file reliably, whether its audio reaches the outgoing mix, and whether the encoded stream uses settings YouTube accepts. For OBS’s documented Media Source workflow, MP4 is a simple starting point. If you need to convert a legacy file first, this guide to converting FLV videos for a 24/7 YouTube stream discusses why checking the converted result matters.
Put the MP4 in an OBS Media Source and loop it
In OBS, add a Media Source to the scene that will carry the product video. Browse to the local file, then enable Loop in the source properties. OBS documents that the Media Source restarts playback when it reaches the end. That is the simple file-and-loop arrangement: OBS reads the file, displays it in the scene and handles the repeat.
Fit the source to the canvas and check that it is not hidden behind another scene item. If the video has a soundtrack, watch for the Media Source in the Audio Mixer while it plays. A moving meter is an early indication that OBS is receiving audio from that source; it does not yet prove that the correct track is selected for the stream or that viewers can hear it.
A playlist is a different need. OBS’s VLC Video source can play a playlist, and its Loop Playlist property repeats the list once it runs out of items. If your plan is one product video repeated indefinitely, a single Media Source with Loop is easier to inspect. If you rotate several demonstrations, a playlist may be more suitable, but you must still check the transitions and the audio of each item.
OBS’s Media Sources guide describes the source controls. Test after changing the file path or replacing an export: a source can point to an old file, or a newly exported file can differ in duration or audio from the version you checked. Keep the final file in a stable location before building the scene, so a later move does not leave OBS looking for a missing source.
Source container and live ingest are different layers
A container such as MP4 packages tracks in a file. In this workflow, the file is local media that OBS decodes and plays. OBS then encodes the scene into a live stream and sends that stream to YouTube. The outgoing codecs and transport settings are properties of that live broadcast, not consequences guaranteed by the source extension.
This is why “I have an MP4” does not answer whether YouTube will accept the stream or whether sound will reach viewers. A source may decode correctly while the outgoing encoder uses an unsupported combination, the audio is muted, or the wrong track is routed. Conversely, YouTube’s list of live codecs does not mean that you should turn the source file into a live ingest file yourself.
For the common RTMP/RTMPS workflow, YouTube’s encoder guidance lists H.264, H.265/HEVC or AV1 video, and AAC or MP3 audio. It recommends RTMPS as the secure RTMP variant. HLS is another ingest route for supported uses, with its own audio codec and segment requirements; choosing it does not fix a muted OBS source. For a simple compatibility-first OBS setup, use the usual RTMP/RTMPS path and H.264 with AAC stereo unless you have a specific reason and a tested configuration to do otherwise.
YouTube’s live encoder settings are the reference for current ingest guidance. If YouTube reports a stream-format error, treat that message as evidence about the outgoing stream configuration, not proof that the MP4 source container is wrong. The source file and the live stream need separate checks.
Set H.264 video and AAC stereo audio
In OBS’s output settings, choose H.264 for the live video encoder and AAC for audio. YouTube supports other live video codecs in its guidance, and MP3 is also listed for audio, but H.264 video with AAC stereo is a straightforward compatibility-first pairing for a basic product loop. This is a practical default, not a claim that other supported configurations cannot work.
Set the channel layout to stereo if the product video has ordinary left-and-right audio or mono narration placed in a stereo mix. YouTube recommends stereo audio at 44.1 kHz and 128 kbps for the relevant RTMP/RTMPS guidance. If you are producing in another workflow, check YouTube’s current official recommendations for that ingest route rather than carrying settings over by habit.
The words “AAC in the file” and “AAC in the live output” refer to different stages. A source MP4 may contain AAC-LC audio, which YouTube recommends for uploads, but OBS still makes an outgoing stream using its chosen audio encoder and settings. You can therefore have a source track that plays and still misconfigure the live output, or have a correct output codec with nothing audible routed into it.
Keep the setup deliberately plain while diagnosing. Avoid adding microphone capture or desktop audio unless you need it. If the video’s own track is the only intended sound, use that source as the sound path and verify the relevant OBS mixer and track assignment. Extra captures can add noise or duplicate sound without solving a silent source. YouTube’s recommended upload encoding settings are useful for preparing an upload file, but they are not a substitute for configuring live encoder output.
Check bitrate, keyframes and audio format
Use YouTube’s documented live recommendations as a starting point, then choose a profile that your upload connection can sustain without instability. Its RTMP/RTMPS encoder guidance recommends constant bitrate (CBR), a two-second keyframe interval, and says not to exceed four seconds. For stereo audio it recommends 44.1 kHz and 128 kbps. These settings describe the outgoing live stream, not the MP4 file’s container.
For H.264, YouTube’s current recommended bitrate examples include 8 Mbps for 720p30 or 720p60, 14 Mbps for 1080p30, and 17 Mbps for 1080p60. Treat these as YouTube recommendations, not guaranteed quality levels or minimums that every connection can maintain. If your upload connection is shared or variable, a lower, stable resolution and bitrate can be more useful than a higher setting that repeatedly strains the connection. Check the current table on YouTube’s official page before a significant broadcast because guidance can change.
| Live profile example | YouTube H.264 bitrate recommendation | A practical question to ask |
|---|---|---|
| 720p30 or 720p60 | 8 Mbps | Does this keep the product and any labels clear while leaving room for a stable upload? |
| 1080p30 | 14 Mbps | Does the extra detail matter for this product, and can the connection sustain it? |
| 1080p60 | 17 Mbps | Does the scene’s motion benefit from this profile enough to justify the greater upload demand? |
The values in the table are YouTube’s recommendations, not results from a test of your connection. For example, a tabletop product rotating slowly may not need a 60 fps profile. A demonstration with quick movement might benefit from it, but only if your encoder and connection handle the selected settings. Use YouTube’s encoder troubleshooting and setup guidance alongside the current encoder recommendations, and check stream health during a test.
If you are troubleshooting sound rather than picture, do not change video bitrate as a first response. Check the audio codec, sample rate, channel layout, source track and routing separately. A video can arrive smoothly while the audio path is silent or misdirected.
Preview the loop and listen for audio problems
Run the actual scene for a test before scheduling or starting the public broadcast. Watch and listen through at least one complete playback and the transition back to the start. Look for black frames, an abrupt cut, a pause, or a change in soundtrack at the boundary. The Loop control restarts playback, but official documentation does not promise that every export will make a gapless, frame-perfect transition. Inspect the result you will use.
Use a simple audio diagnosis in order:
- Play the source file outside OBS and confirm that the intended track is audible.
- In OBS, watch the Media Source’s mixer meter during playback. If it does not move, check the file’s audio track and the source’s playback settings.
- Confirm the source is not muted and that it is assigned to an audio track included in the stream output.
- Check the outgoing audio encoder and YouTube’s stream health for a format warning.
- Listen to a controlled stream or recording from the viewer side before relying on the setup.
The OBS meter answers whether OBS is receiving signal at that point in the chain. Local monitoring is a separate facility: hearing audio through your own speakers does not prove that the same sound is routed to the stream. Set up monitoring deliberately if you need it, select the intended monitoring device, and make a viewer-side test. OBS’s audio mixer guide explains meter and mixer behaviour; its audio sources guide covers source choices.
If the meter moves but the audience hears nothing, inspect track assignment and the stream output mix before re-exporting the video. If it does not move, focus first on the file, Media Source and source settings. If viewers hear an echo, look for the same device captured globally and again as a scene source; duplicate capture can create echo. Do not add more audio devices until you know which part of the path is failing.
For a channel that needs the product loop to continue when the operator’s computer is switched off, StreamNeo removes the specific burden of leaving OBS running on that computer; it does not remove the need to check the source audio, stream settings and actual viewer playback. This matters particularly for a 24/7 schedule, where an overnight test should include the loop boundary and audio path rather than just a quick glance at the opening frame. If you are deciding between a local computer and a hosted workflow, this comparison of cloud streaming and a Mac mini for Indian creators frames the operating trade-off.
A looping product video is also a content decision, not only an encoder setting. Make the first seconds understandable to someone who joins mid-loop, and ensure any offer, price or availability shown in the video remains current. YouTube’s policies and your own product obligations still apply; review the current official guidance for your stream and content rather than assuming a technical configuration settles those questions. For examples of planning the creative material itself, see how to make product videos for YouTube.
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
Is MP4 the YouTube Live ingest format?
No. MP4 is the local source file in this OBS workflow; OBS plays it and encodes the live output that goes to YouTube. YouTube’s live encoder recommendations apply to that outgoing stream, so check its video, audio and transport settings separately.
Does an MP4 guarantee that viewers will hear audio?
No. The file needs an audible intended track, OBS must receive and route it to the stream, and the outgoing encoder must use a supported audio configuration. Confirm the mixer meter and make a viewer-side test rather than relying on the extension or local monitoring alone.
Which settings are a sensible starting point for a basic product loop?
Use an MP4 Media Source with Loop enabled in OBS, then configure H.264 video and AAC stereo audio for the live stream. YouTube recommends CBR, a two-second keyframe interval, and stereo at 44.1 kHz and 128 kbps for its RTMP/RTMPS guidance; verify the current official settings and select a sustainable video profile.
Can I use a playlist instead of one looping file?
Yes. OBS’s VLC Video source can play a playlist and loop it after the final item. Test each clip’s sound and the transitions in the actual scene, because a working playlist control does not establish that every item has the intended audio or a clean boundary.