For a local 4K 60fps gaming highlights playlist, use OBS Studio with its VLC Video source: add the clips in order, enable looping if you want the list to repeat, and send the scene to YouTube Live with the stream URL and key from YouTube Studio. Install VLC before adding the source, and match its 64-bit architecture to 64-bit OBS.
Prepare YouTube Live access and the event first, then test a representative section of the playlist before scheduling viewers to arrive. YouTube’s recommended ingest settings are not a promise that every viewer will receive 4K60; playback quality depends on YouTube’s transcodes and each viewer’s device and connection.
Prepare YouTube Live access and event
Check that your channel is eligible to go live and complete any verification or activation steps shown in YouTube Studio. First-time live streaming is not necessarily available immediately: YouTube says enablement may take up to 24 hours. Do not leave this until minutes before a planned broadcast. Sign in early, follow Studio’s prompts, and wait for the feature to become available before relying on it for an event.
Once access is ready, open the live streaming area in Studio and create or schedule a stream. Scheduling gives you an upcoming watch page to share and lets you set the title, description, visibility and intended audience in advance. If you are testing the workflow rather than inviting viewers, choose a visibility setting appropriate to that test. Check the current YouTube instructions for creating a live stream because Studio’s labels and available options can change.
Treat the title and description as useful information for the viewer, not a substitute for a functioning stream. Say that the broadcast is a gaming highlights playlist, whether it repeats, and what sort of footage viewers will see. Set the audience accurately. If you are scheduling a public stream, review the watch page from a viewer’s perspective and confirm the start time and time zone before sharing it.
You will need the encoder details from Studio when you connect OBS: a stream URL (sometimes labelled server URL) and a stream key. The key is a credential that permits an encoder to send a feed to your channel. Keep it private, do not put it in a public document or screenshot, and reset it in Studio if you believe it has been exposed. The YouTube encoder setup guide explains where to find these details and how they are used.
A useful preparation checkpoint is that the channel can access Live Control Room, the event has the correct audience and visibility, and you know where its encoder settings are. You do not need OBS connected yet. If you are planning a longer channel rather than a single event, the practical concerns around repeating local files are similar to those in this guide to playing podcast MP4 files continuously with OBS.
Install matching 64-bit VLC
OBS’s VLC Video source relies on VLC being installed on the computer. It is not a standalone player built into OBS, so adding the source without VLC may leave you unable to use it. OBS documents that the source supports a playlist of media items and requires VLC; see the OBS media sources documentation.
Check whether the OBS installation is 64-bit, then install the matching 64-bit VLC build from VideoLAN’s official download page. On a 64-bit Windows system, the usual OBS Studio desktop installation is 64-bit, but check the build you actually use rather than assuming. A mismatch between application architectures can prevent OBS from detecting or loading VLC correctly. Close OBS during installation, install VLC, and reopen OBS afterwards.
Avoid installing a random codec bundle to solve a VLC detection problem. First confirm that VLC itself launches and can play one of your clips. Then check that OBS and VLC have the same architecture and restart OBS. If OBS was already open during installation, a restart is a sensible first troubleshooting step.
Before building the scene, make sure the highlight files are local and readable by the account running OBS. Files on a removable drive or network share can become unavailable during a broadcast if the drive disconnects or the machine loses access. Keep the playlist folder in a stable location and avoid renaming or moving its files after adding them to the source.
Add an OBS VLC Video source
Create a scene for the broadcast, then use the Sources dock to add a VLC Video source. If that source type is missing, return to the installation checks: VLC must be installed and the architecture must match OBS. This is distinct from adding an ordinary Media Source; VLC Video is the source intended for a list of items.
Open the source properties and add the local video files you intend to play. The source maintains a playlist, so you can arrange the list there rather than building a separate scene for every clip. OBS describes the difference from a single Media Source this way: “Unlike Media Source, you can create a playlist of items, similar to an Image Slideshow.” Add only files you have permission to broadcast, including both gameplay footage and any soundtrack or other audio included with it.
Set the source to loop if you want playback to return to the beginning of the playlist after the final item. OBS lists looping as on and shuffling as off by default, but inspect the properties rather than relying on defaults. For a highlights programme with an intended sequence, leave shuffle off. For a varied background rotation, shuffle may be appropriate, but it changes what viewers see next and can make it harder to check a known transition during testing.
Make the source visible in the scene and confirm that the preview displays video. If the source has sizing controls, fit it to the canvas as needed, then inspect the edges for unwanted black bars, cropping or a stretched picture. A 4K source in a canvas with different dimensions may need careful framing. Do not stretch footage simply to fill the preview if it distorts the image; preserving the original proportions is generally preferable to making characters or interface elements look unnaturally wide.
Order and loop the highlight files
Put the files in the sequence you want the audience to experience. For example, you might place a short opening clip first, then group highlights by game or match, and finish with a clip that works as a transition back to the start. The exact sequence is editorial: OBS will play the list, but it cannot decide whether a repeated opening feels abrupt or whether a particular clip belongs at the end.
Check the start and end of each file before adding it. A clip with a long silent lead-in can look like a frozen stream, while an abrupt end may create a black frame or silence between items. Play the files locally in VLC and note any unexpected aspect ratio, audio level change or blank section. If you trim or export revised clips, update the source playlist to point at the final files.
Looping the list means the playlist repeats; it does not repair gaps or inconsistencies inside the individual files. Test the hand-off from the final clip to the first, including the audio. If the last clip ends with a loud sound and the first begins quietly, that contrast will recur each time the playlist wraps. You can also use a separate holding scene, but switching scenes manually makes the setup less unattended and should be tested as its own operation.
For an ordered series of individual sources rather than a VLC playlist, compare the workflow in setting up multiple OBS media sources as a continuous playlist. The distinction matters: a VLC Video source keeps its list in one source, whereas multiple scene sources require you to manage how and when each item appears. Choose the arrangement you can inspect and maintain reliably.
Check soundtrack levels in OBS while representative clips play. Watch the audio meter for activity and listen through the same output path you will use for testing. A meter moving does not establish that viewers can hear clean audio, so listen for clipping, unexpectedly quiet clips and doubled sound. If the footage has no audio, decide deliberately whether silence is acceptable rather than assuming that a moving video alone makes a complete broadcast.
Set the 4K60 encoder settings
The files’ resolution and frame rate are only part of the chain. The OBS canvas, output resolution, frame rate, encoder, bitrate and available upload capacity also affect what OBS sends. For a 4K60 output, use settings that your OBS installation and computer can sustain, then verify them with a representative test. There is no universal computer specification that guarantees a particular playlist will encode smoothly.
YouTube’s current encoder guidance recommends H.264 at 35 Mbps for 4K/2160p at 60 frames per second. For AV1 or H.265, it lists a bitrate range of 10–40 Mbps for that resolution and frame rate. These are YouTube ingest recommendations, not a guarantee of quality at the viewer’s end. Codec availability depends on the encoder and computer, so use an option your setup can actually encode and test it rather than selecting a codec solely because it is newer.
YouTube’s general guidance calls for constant bitrate (CBR), a recommended keyframe interval of two seconds, and says not to exceed four seconds. It recommends RTMPS for the connection. Apply the settings in OBS’s output and stream configuration, checking that the chosen output resolution and frame rate are actually 2160p and 60fps if that is the intended feed. Consult YouTube’s live encoder settings for the current codec-specific guidance before going live.
Keep the source footage in view when deciding whether to enable HDR. A basic SDR highlights playlist does not become HDR because an output setting is changed. Only configure HDR when the footage and the complete encoding path support it and you have checked the result. Otherwise, use a straightforward SDR workflow and avoid introducing an extra colour issue that is hard to diagnose during a live event.
Upload capacity deserves a real test, not a guessed headroom formula. A connection that looks fast in a general speed test may still fluctuate, and other household or office traffic can compete with the encoder. Run the stream at the intended settings, observe YouTube’s reported stream health, and repeat the test at a time and on a connection resembling the planned broadcast. If the feed is unstable, reduce the output demands or resolve the connection issue before promoting the event.
Connect OBS to YouTube Live
In OBS, open Settings and then the Stream section. Select YouTube or the service setup appropriate to YouTube Live. Depending on the OBS version and connection method, you may sign in or enter the server URL and stream key manually. If entering them manually, copy the exact URL and key displayed for the scheduled stream in Studio; do not reuse details from a different event without checking that they are the intended ones.
Treat the stream key like a password. Anyone with access to it may be able to send an encoder feed to the channel, so avoid sharing it with collaborators who do not need it. If OBS offers to store the key, keep your computer account protected and do not publish screenshots of the settings window. If you suspect the key has been copied, manage or reset it through YouTube Studio and update OBS with the replacement.
Save the settings and start the OBS stream when you are ready to test or broadcast. Starting OBS sends the feed to YouTube; it is not the same as confirming that the scheduled public event has begun for viewers. Check Live Control Room and follow the controls presented there to preview and start the event. YouTube’s guidance on managing live streams covers the Studio side of that hand-off.
If OBS reports a connection failure, check the stream key and URL carefully, then confirm that the scheduled event is the one you intend to use. Do not paste a key into chat or a public support post to ask someone to inspect it. When the credentials are correct but the feed still does not connect, check the connection and OBS output configuration before changing several settings at once; changing one variable makes the cause easier to identify.
Test playback and stream health
Test before the event with a section containing both motion and audio. A static title card will not reveal whether fast gameplay produces encoding strain, and a silent clip will not test the audio path. YouTube advises setting up an encoder well ahead of the event, starting it at least 15 minutes before the scheduled start, checking the Live Control Room preview before going live, and monitoring stream health and messages. The YouTube live-stream tips are worth checking alongside your own preflight.
In the preview, inspect the picture for the right framing, motion and colour, and listen for audio. Confirm that the playlist advances as expected and that its loop returns from the last item to the first. Keep OBS visible long enough to see whether the system can sustain the chosen output without warning messages or obvious stutter. YouTube’s stream-health indicators are useful evidence about the incoming feed, but they do not replace watching and listening to the programme.
A private or unlisted test can help you check the viewer experience without announcing a public event, if the available Studio controls suit your needs. Open the test on another device or browser and confirm that the actual playback is acceptable there. A local OBS preview can look correct while the YouTube ingest or viewer playback reveals a problem, so test the whole path.
If YouTube reports missing audio, first verify that the VLC source is producing audio and that OBS is sending the expected audio track. The issue may be in the clip, source, mixer or output settings. For a related fault pattern, see how to diagnose missing audio in a YouTube loop stream. Do not assume that a green video preview proves the audio has reached YouTube.
When the test looks right, write down the settings that worked and avoid last-minute changes without retesting. At the planned start, begin the OBS feed early enough to review the incoming preview, then use Studio’s event controls to go live. During the broadcast, keep an eye on stream-health messages and playback. If a problem appears, prioritise a stable feed over preserving a nominal 4K60 label: a lower output that actually plays cleanly may be more useful than an unstable one.
After the event, stop the encoder when the broadcast has ended and confirm the stream has finished in Studio. YouTube says streams shorter than 12 hours are automatically archived; check the current archive and visibility controls rather than assuming a particular replay setting. If the goal is a continuous channel rather than a single scheduled programme, plan how you will monitor it and recover from interruptions. This guide to common live-streaming challenges covers broader failure planning.
A playlist that depends on a computer staying on and a local copy of every file may not suit a channel that must keep running while you are away. StreamNeo removes that specific burden by turning an uploaded video into a YouTube-only 24/7 stream, so the creator’s computer does not have to stay on for the broadcast. It is a different workflow from the OBS and VLC setup described here, and you should still check the files, channel access and stream plan before relying on any arrangement.
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’s VLC Video source work without VLC installed?
No. The VLC Video source depends on VLC being installed on the same computer as OBS. Install the matching architecture, including 64-bit VLC when using 64-bit OBS, then restart OBS and check that the source is available.
Why is YouTube Live not enabled yet?
YouTube says first-time live-streaming enablement may take up to 24 hours. Complete the account steps in Studio early and wait for access to appear; do not plan on starting a first broadcast immediately after requesting activation.
Will every viewer see the highlights in 4K at 60fps?
No. Your encoder sends an ingest feed, and YouTube transcodes streams into formats for different devices and network conditions. Use the recommended encoder settings as a starting point, then test both the incoming stream health and playback on a viewer device.
Does a playlist loop automatically, and should I shuffle it?
OBS’s VLC Video source supports looping and shuffle controls, and its documented defaults are looping on and shuffling off. Check the source properties yourself and choose based on the programme: a planned highlights sequence usually needs shuffle off, while a varied rotation may suit shuffle.