To stream a pre-recorded video from OBS to YouTube, add it as a Media Source, enable Loop, select an NVENC encoder that your system actually offers, and connect OBS to a YouTube Live event. For a playlist, use VLC Video and loop the playlist instead; either method still needs a test and ongoing checks, because NVENC does not keep a stream online by itself.
This walkthrough follows the setup in that order. You will check hardware, prepare the playback source, match output to YouTube’s current guidance, connect the stream key, and test the complete path before relying on it.
Check that your system offers NVENC
NVENC is NVIDIA’s hardware video encoder. OBS can use it only when the graphics hardware, operating system, driver and installed OBS build support it. Do not assume that having an NVIDIA-branded computer means an NVENC option will appear: check the encoder list in OBS before you build your streaming plan around it.
In OBS, open Settings, then Output. If Output Mode is set to Simple, change it to Advanced so the streaming encoder choices are visible. Look for a name containing NVIDIA NVENC in the streaming section. The exact labels and codec choices can differ with the GPU generation, operating system, driver and OBS version. If the choice is missing, update the graphics driver and OBS from their official sources, restart the computer and check again. If it remains absent, use an encoder that OBS provides rather than assuming NVENC is available.
OBS’s hardware-encoding guidance lists GeForce 750 Ti and 900-series or newer hardware as supported, while noting that system support and current drivers also matter. Treat that as a compatibility reference, not a guarantee that a particular combination will expose every codec or setting. OBS also cautions that older generations of hardware encoding can produce lower image quality at the same bitrate than newer ones. The OBS hardware encoding support guide gives the compatibility context; your installed encoder list is the practical check.
Before proceeding, note which NVENC codecs OBS offers. YouTube’s general encoder guidance accepts H.264, HEVC/H.265 and AV1 for RTMP/RTMPS ingestion, but your hardware may not offer all three. If your GPU offers only H.264, use that. If you are comparing codecs, also consider whether your intended viewers and playback devices are well served by them; a codec being accepted for ingestion does not by itself guarantee compatibility throughout every viewer’s playback path.
Add a source for one file or a playlist
Choose the playback source based on how you have organised the programme. For one local video, use OBS’s built-in Media Source. For several files that should play in sequence, use VLC Video, which handles a playlist. They are different source types, so do not set up a single-file loop and expect it to act like a playlist manager.
In the scene you intend to broadcast, select Sources, press the add button and choose Media Source. Give it a recognisable name, such as “Main programme”, then select the local video file. OBS Media Source accepts common formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM. Check that the chosen file opens and that its picture fits the canvas as expected. If the video includes audio, confirm that its meter moves in the OBS Audio Mixer when playback is running.
If you have a sequence of items, add VLC Video instead and create the playlist from the files you want included. VLC must be installed, and a 64-bit OBS installation requires 64-bit VLC. That dependency is an extra point to test: a playlist source that cannot find VLC or a media file will not behave as intended. The OBS Media Sources guide explains the built-in source and VLC Video options.
A playlist is useful when you want several distinct pieces to rotate without editing the source every time a video ends. A single Media Source is simpler when the same file should repeat. If you need to change the content later while a channel is already live, first understand what viewers will see during the switch; this guide to changing videos in a running loop stream covers that separate operational concern.
Turn on the right loop option
For a single file, open the Media Source properties and enable Loop. Start playback in the OBS preview and let the file reach its end during a test. Confirm that it starts again without requiring you to press Play. Restart playback from the beginning once more if necessary; a loop box being checked is less useful than seeing the transition occur in practice.
For multiple files, open the VLC Video source properties and enable Loop Playlist if it is not already enabled. OBS documents this option as on by default, but verify it rather than relying on the default: someone may have changed the source properties, or the installed version may present them differently. Watch the last item finish and check that the first item returns. Also check the order, because an incorrect playlist can loop perfectly and still show the wrong programme.
The end of a file is a useful place to look for problems. Some videos have a brief black frame, a gap in sound, or a different volume level at the join. OBS looping will repeat the media; it will not repair an edit. Watch at least one complete boundary in the preview and listen to it. If the programme has long quiet sections, include representative audio and movement in the test rather than deciding that the source is healthy from a static opening frame.
If you need a more elaborate sequence, with scene changes or different overlays for different clips, do not treat one VLC playlist as a substitute for that structure. OBS scenes and sources can be combined, but each additional moving part is another thing to test. For a simple station that repeats one devotional video or ambience recording, a single Media Source with Loop is usually the clearest starting point; for a rotation of complete files, VLC Video keeps the playlist together.
Select NVENC and match YouTube’s output guidance
In Settings → Output → Streaming, choose the NVENC option that appeared in your encoder list and select a codec supported by both that option and YouTube’s ingestion guidance. Do not copy a recording preset into streaming settings just because it appears in an OBS tutorial. Recording and live delivery have different requirements; YouTube’s current live encoder recommendations should guide the stream output.
YouTube recommends RTMPS, constant bitrate (CBR), progressive scan, two B-frames and a keyframe interval of two seconds, not exceeding four seconds. Audio guidance includes AAC or MP3; for stereo AAC/MP3, the documented recommended value is 128 Kbps. For SDR, YouTube recommends Rec. 709. Check YouTube’s encoder settings, bitrates and resolutions page for the current full requirements and the row for your chosen codec, resolution and frame rate. OBS controls may use slightly different wording, so make sure you are matching the intended values rather than guessing at a similarly named setting.
There is no one bitrate that suits every output. It depends on codec, resolution and frame rate. YouTube’s recommendations include these examples:
| Output target | AV1 or HEVC/H.265 recommendation | H.264 recommendation |
|---|---|---|
| 1080p at 30 fps | 10 Mbps | 14 Mbps |
| 1080p at 60 fps | 12 Mbps | 17 Mbps |
These are YouTube recommendations, not guaranteed minimums for a particular internet connection. Use the relevant row from YouTube’s current guidance for the output you actually select rather than treating either example as a universal setting. A 1080p60 stream is not automatically better for a static or slowly moving programme; it asks for a different bitrate and source performance than 1080p30. Choose a resolution and frame rate the source, encoder and connection can sustain together.
Measure the connection from the location and network you expect to use. YouTube recommends a speed test and a test stream at the expected quality. Leave capacity for normal variation and other traffic on the connection; a result from an otherwise idle network is not proof that the same upload will remain available overnight. If you lower the bitrate to fit an unreliable or shared connection, watch the stream health during a test and assess whether the resulting picture remains acceptable.
Avoid adding advanced encoder options without a reason. OBS’s NVENC recording baselines apply to recording, not as universal instructions for YouTube streaming. Likewise, advanced options can depend on OBS version, codec and GPU. Start with the settings YouTube specifies for the target stream and the options your encoder exposes; add complexity only when you can test its effect.
Connect OBS to YouTube Live Control Room
Create or select the live event in YouTube Studio and open its Live Control Room. YouTube provides a stream URL and a stream key for the encoder. In OBS, open Settings → Stream, choose YouTube or the relevant YouTube connection method, then enter the details requested. If you enter a custom server URL, use the URL YouTube provides for the event rather than a remembered address from another setup.
Treat the stream key like a password. Anyone who obtains it may be able to send video to the associated stream. Do not include it in a screenshot, public tutorial, shared document or message where it is not needed. If you think it has been exposed, replace or reset it in YouTube Studio and update OBS with the new value. The YouTube encoder setup instructions describe connecting an encoder to the live event.
Keep the OBS scene, source and event aligned. A common mistake is to test one scene and then start a different scene that has no video or audio source. Before starting the event, select the intended scene, check that the loop is playing and look at the Live Control Room preview. Confirm moving picture and audible sound there as well as in OBS. Local preview alone does not confirm that YouTube is receiving the right feed.
YouTube’s stream settings include latency and DVR controls. Lower latency can mean more buffering for viewers, and YouTube says lower latency matters less when the audience does not need interaction. DVR allows viewers to pause, rewind and resume. Decide based on the use of the channel: a devotional stream intended for quiet viewing may value stable playback more than fast interaction, while a live local update may have different needs. Check the event settings and the current YouTube explanation rather than assuming the default is right for every audience.
Test the complete path and check stream health
YouTube’s advice is direct: “Make sure to test before you start your live stream.” Test with the actual scene, source, audio, codec, resolution and frame rate you plan to use. A short test with representative motion and sound can expose problems that a still desktop preview will not, including audio clipping, a silent source, a file that fails to loop, or dropped frames under the intended encoding load.
Start the encoder and inspect the incoming preview in Live Control Room. Check that the image is moving, the expected audio is present, and the preview is not showing a different scene or an unexpected black frame. Read the stream health messages rather than treating the preview image as the only signal. If YouTube reports a problem, change one relevant setting at a time and test again so you can tell whether the adjustment helped.
Check the OBS status indicators too. Watch for dropped frames, encoder overload and connection instability. These point to different kinds of trouble: a healthy local encode does not prove the upload path is stable, and a stable connection does not prove the source is playing correctly. If the picture looks soft or breaks up, verify the output resolution and bitrate against YouTube’s guidance and check the available upload capacity. If audio is absent, inspect the source and mixer routing before changing video settings.
A test should include a loop boundary. For a playlist, observe the transition from the final item back to the first; for one file, let it restart. If you intend to broadcast for a long period, also check what happens when the computer display sleeps, a user session changes or the network reconnects. That is not a substitute for a long-duration operational test, but it catches ordinary configuration mistakes before they become an unattended problem. This checklist for testing an always-on channel before moving it can help structure a broader rehearsal.
YouTube documents that live streams under 12 hours are automatically archived. Do not infer that a longer nonstop broadcast will produce one complete replay. If a recording matters, plan the event duration and archive needs deliberately, then verify the result afterwards. For streams expected to exceed that duration, consider shorter event segments and check YouTube’s current archive guidance rather than relying on a single continuous replay.
Plan for monitoring, not assumed uptime
NVENC is an encoder choice. It can reduce reliance on CPU encoding when supported, but it does not keep OBS open, restore a failed internet connection, repair a missing media file or guarantee that YouTube continues receiving the broadcast. OBS running on a local computer depends on that computer, power, network, operating system and streaming session continuing to work. Looping controls what the source does while the stream is running; it is not an uptime mechanism.
For a local setup, decide who will notice a problem and what they will do. Keep the computer on reliable power, prevent planned sleep from interrupting OBS, and arrange a way to check the channel remotely if nobody is in the room. A practical check includes confirming the public player is receiving video and audio, reviewing Live Control Room health messages, and checking the local source if the public feed is wrong. This guide to keeping OBS from stopping when the display sleeps addresses one specific failure mode, not every cause of interruption.
If the channel is important enough that a brief interruption matters, test a backup encoder or failover plan before relying on it. YouTube recommends preparing and testing backup encoder failover when the stream’s importance warrants it. A backup that has never been tried is not a dependable fallback; document how it connects and how you would avoid sending the wrong scene or stream key. A home computer and a cloud-based workflow also have different operational trade-offs: the former keeps the playback and controls in your hands, while a workflow that does not depend on your desktop being left on removes that particular local-computer burden. StreamNeo can remove the need to leave OBS running on your own computer for an uploaded-file YouTube stream, but it does not remove the need to check that the channel and content are behaving as intended.
Choose the method that fits the work you can support. Local OBS makes sense when you want direct control over scenes, overlays, transitions or live intervention and can monitor the computer and connection. A simple repeated file needs less scene logic than a multi-item programme. A channel that must continue when your computer is off needs a different operating arrangement; do not treat selecting NVENC as a replacement for that decision.
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 NVENC make an OBS stream nonstop?
No. NVENC handles encoding when compatible hardware and software expose it, but continuity also depends on OBS, the source, the computer, power, network and YouTube receiving the stream. Test the full path and make a monitoring and recovery plan.
Should I use Media Source or VLC Video?
Use Media Source for one local file and enable its Loop option. Use VLC Video when you need a playlist of multiple files; VLC must be installed, and its architecture must match OBS. Test the end-to-start transition in either case.
Which NVENC codec and bitrate should I choose?
Choose only a codec your GPU’s NVENC option offers and YouTube accepts for the ingestion protocol. Then use YouTube’s current recommendation for the selected codec, resolution and frame rate; the example bitrates in this article are not universal targets.
Will YouTube archive a very long live stream?
YouTube documents automatic archiving for live streams under 12 hours. Do not assume that a longer stream will produce one complete replay; check current archive guidance and plan shorter events if a complete recording matters.