OBS can send a pre-recorded video to YouTube for a long live session, but there is no single preset that suits every OBS version, computer, source video or internet connection. Create the event in YouTube Studio, enter its stream URL and key in OBS, then match the encoder settings to YouTube’s guidance and the upload capacity you have tested.
For a dependable start, use RTMPS, CBR and a 2-second keyframe interval where those controls are available. Test the whole playback path before going public, keep upload headroom and monitor both OBS and YouTube Studio. “All day” also has an archive caveat: YouTube says streams longer than 12 hours may not be captured as replays.
1. Create the live stream in YouTube Studio
First check that livestreaming is enabled for your channel. YouTube says a channel must be verified and must not have had a live-streaming restriction in the preceding 90 days. Check YouTube’s current livestreaming requirements if you are setting this up for the first time; eligibility and account status are separate from OBS configuration.
In YouTube Studio, create a new live stream or schedule one. Follow the prompts for its title, audience settings, visibility and schedule. Scheduling gives you a watch-page link to share in advance and lets you prepare the stream details before the broadcast. Check the event’s settings in Studio before you send a signal, particularly whether it is private, unlisted or public.
Choose the encoder workflow for an external encoder. YouTube Studio supplies a server URL and stream key for the event. Their labels can differ slightly as Studio changes, but the purpose is the same: the URL tells OBS where to send the feed, and the key identifies the stream it belongs to. YouTube’s encoder setup instructions walk through creating this hand-off.
A stream key behaves like a password. Do not put it in a public screenshot, a shared document or a scene title. If you think someone else has access to it, reset it in Studio and update OBS before broadcasting. YouTube explains how to manage stream settings and keys.
Keep the Studio event open during setup. You will use its preview and stream-health information to confirm that OBS is reaching YouTube and that the incoming picture and sound are usable. Creating the event does not itself start the encoder feed; OBS must be configured and started separately.
2. Connect OBS using the URL and key
In OBS, open the stream settings and select YouTube or a custom streaming service, depending on the options shown by your OBS version. If you select YouTube, follow its sign-in and event-selection flow if available. If you use a custom service, enter the server URL from Studio and paste the stream key into the key field. Choose the RTMPS URL when Studio provides it: YouTube recommends RTMPS for secure ingestion.
Take care not to paste the key into the URL field or include spaces at either end. A connection error at this stage may be a copied credential, an outdated key or an incorrect server choice rather than an encoder problem. If you regenerate the key in Studio, the saved key in OBS must be replaced as well.
Use one active OBS profile and scene collection for the intended event. A profile stores output and stream settings, while scenes and sources determine what OBS sends. Names and menu locations change between OBS releases, so treat the instructions here as a path through the settings rather than a claim that every installation has identical controls.
For a pre-recorded video, add it as a media source and confirm the source’s restart or loop behaviour matches the plan. If you are combining a video with a still image, title card or other elements, check the order and visibility of the sources. A video that ends without looping can leave you streaming a blank scene even though OBS remains connected. For a broader always-on workflow, see this guide to building a school announcement channel stream.
Do not press Start Streaming just to check whether OBS opens. The signal may already be arriving in Studio, and the event’s visibility controls determine who can watch it. Use an unlisted or private test event if you need to inspect the full hand-off without making the programme public.
3. Choose a codec and output target
Set your output resolution and frame rate to match what the audience needs and what the source contains. A 1080p source intended for a 30 fps presentation does not automatically benefit from being encoded at 60 fps. Higher resolution or frame rate can require more upload bandwidth and encoding capacity; choose based on the material, the connection and the computer’s ability to sustain encoding.
YouTube’s live encoder guidance lists H.264, H.265 (HEVC) and AV1 for RTMP/RTMPS ingestion. What OBS actually offers depends on the installed version, operating system and hardware. Use an encoder supported by your setup and compatible with the delivery path; do not assume every machine has the same hardware encoder or that a particular OBS profile is an official YouTube preset.
H.264 is a straightforward starting point when it is available and you want broad compatibility. HEVC or AV1 may be appropriate in supported workflows, but codec support, performance and YouTube’s bitrate recommendations differ. Consult YouTube’s live encoder settings for the current table rather than copying values from its separate video-upload guidance.
YouTube detects incoming encoder settings and transcodes the live feed for viewers’ devices. Your OBS output is therefore the source feed, not a guarantee that every viewer receives the same resolution. The target should be one your machine can encode continuously and your connection can send with margin. If the computer is already busy, reducing the resolution or frame rate may be more useful than increasing bitrate.
The intended video matters too. A mostly static devotional image with a bhajan soundtrack has different motion from a local news loop with clips and transitions, but it still needs a clean, stable signal. Avoid treating low motion as permission to ignore the recommended encoder format or test: a frozen source, a silent transition or a media file that reaches its end can undermine the stream even when the connection remains active.
4. Set bitrate, CBR and keyframe interval
YouTube recommends constant bitrate (CBR) for live encoding, a 2-second keyframe interval and an interval no longer than 4 seconds. In OBS, set rate control to CBR if the selected encoder exposes that option, then enter the keyframe interval in the encoder’s units. OBS labels and available choices can vary, so check what is actually applied rather than assuming a profile name has set it correctly.
Bitrate depends on the codec, resolution and frame rate. YouTube’s published H.264 guidance, for example, recommends 5 Mbps for 1080p at 30 fps. For H.264 at 720p and 60 fps, it lists 3 Mbps as a minimum and 8 Mbps as recommended. These are YouTube ingestion recommendations, not promises of picture quality, connection stability or compatibility with every computer. Check the table for your chosen format before setting OBS.
Then compare the target bitrate with sustained upload capacity. YouTube recommends leaving 20% headroom beyond the total outgoing bitrate. That margin is not spare bandwidth to consume casually: the measured connection may fluctuate, and other devices or activity on a shared line can reduce what OBS can send. If you are using a primary and backup feed, account for both when considering the total outgoing load.
For example, if you plan an H.264 1080p30 feed at YouTube’s recommended 5 Mbps, the connection should have more capacity than the stream’s bitrate rather than merely matching it. Measure upload under realistic conditions, ideally when the household or workplace is using the network as it normally would. A speed-test result is a snapshot, not a guarantee that the same capacity will be available through an overnight session.
If the stream health indicator reports network instability or OBS reports dropped frames due to network conditions, reduce the output bitrate or choose a less demanding resolution or frame rate, then test again. If OBS reports encoding overload instead, the bottleneck may be the computer rather than the internet connection; try a less demanding output or encoder setting and watch the indicators during playback. Do not raise bitrate to solve a problem that is not caused by insufficient video data.
5. Configure audio and test playback
Check OBS’s audio meters while the pre-recorded file plays. Confirm that the intended source is audible, that desktop or microphone audio has not been added accidentally, and that the level does not clip. If the programme contains speech, music or both, listen to the actual signal rather than relying on the meter alone. A stream can be connected and still be unusable because its audio is muted, too quiet or routed from the wrong source.
Use YouTube’s live encoder guidance for audio format and sample-rate requirements, and keep the OBS output consistent with supported settings. Avoid changing several audio properties at once: make one change, listen to the Studio preview, and confirm the recording or test capture sounds as intended. Check the transitions between clips as well as the loudest sections.
Test the complete segment, not just a still frame at the start. Include a representative passage with movement and sound, a transition, and the point at which the media source should loop or advance. YouTube recommends tests with audio and movement similar to the planned content. Confirm that the picture stays in the intended scene, the video does not pause unexpectedly, and audio continues throughout.
Watch the Live Control Room preview while the signal is incoming. The preview can take time to appear, so allow for processing rather than repeatedly changing settings at the first blank moment. Check that the event is showing the correct source and that the intended visibility setting is in place before you make it public.
A short test is useful, but it does not prove a computer or internet connection can run indefinitely. If the channel depends on the stream through the night, test for a realistic period and look for gradual problems: rising CPU use, dropped frames, storage filling up, a media source reaching its end, or another device saturating the connection. Record locally during testing if you need a reference copy of what OBS actually produced.
6. Check stream health before relying on it
Before the public start, use a checklist: Studio shows the expected preview; OBS has no unexplained dropped or skipped frames; audio is present; the correct video source is playing; and the event has the intended title and visibility. Watch for YouTube’s stream-health warnings and follow the issue it identifies. A stable-looking OBS window alone does not show whether YouTube is receiving a clean feed.
During the session, check both OBS and Studio periodically. OBS can indicate whether frames are being dropped or encoding is struggling; Studio gives you information about the signal received by YouTube. Also check the watch page from a separate device or browser when practical. That helps catch problems that are not obvious in the encoder preview, such as the wrong event being public or playback not reaching a viewer.
For a long session, plan for interruption rather than assuming one setting prevents it. Keep the computer powered, disable sleep or automatic shutdown for the duration, and avoid relying on a Wi-Fi connection if a stable wired connection is available. These are operational precautions, not guarantees. If a power cut, router restart or computer issue is plausible, decide in advance who will notice and how the stream will be restarted.
If a recording matters, enable local recording and verify that the file is growing and playable before leaving the stream unattended. YouTube recommends keeping a local archive as a backup. It also cautions: “If your stream exceeds 12 hours, it may not be captured at all.” If the replay is important, plan the live session and local recording around that limit rather than assuming an all-day broadcast will be available in Studio afterwards.
There is a trade-off between operating OBS locally and using a workflow that does not depend on keeping your computer running. Local OBS gives you direct control over sources and lets you test a familiar scene, but the computer, power and network remain part of the chain. When the specific problem is leaving a personal computer on for the full session, StreamNeo removes that requirement by running an uploaded video as a YouTube live stream without your computer staying on.
Keep rights and channel obligations in view as well. A video being pre-recorded does not exempt it from YouTube’s rules for live content or remove the need to have rights to the material, including music. Review YouTube’s livestream terms for current requirements; do not treat a successful encoder test as a rights check.
7. A practical preflight sequence
Use the same order each time so a failure is easier to locate. First open the Studio event and confirm its title, visibility and key. Next check OBS’s service and stream credentials, then the output resolution, frame rate, codec and bitrate. Confirm CBR and keyframe interval where available, then start the media source and inspect the meters and preview.
Allow the test signal to run through the elements most likely to fail: an audio passage, a transition and a loop or file end. Check that the preview remains live and that stream health is not showing an unresolved warning. If you make a change in response to a warning, restart the test section that exercises that setting rather than assuming the fix worked.
Before leaving the stream unattended, confirm the local recording is advancing if you have enabled it, the computer will not sleep, and storage space is adequate for the planned recording. Make sure you can reach the Studio event and the machine if you need to intervene. Keep a written note of the settings that passed testing, but do not assume they will remain suitable after a source video, network, computer or OBS version changes.
A long-running channel may use a repeated playlist rather than one video. Test the exact sequence and its repeat behaviour; a playlist hand-off is a different failure point from a single file. If your workflow includes more than one feed, this guide to managing concurrent streams on one channel may help clarify the scheduling side. For a computer-based radio playlist, see the practical Windows mini PC streaming setup.
The settings table is a starting reference, not a universal profile:
| Decision | Practical starting point | What to verify |
|---|---|---|
| Ingest protocol | RTMPS, as recommended by YouTube | OBS uses the URL supplied for this Studio event |
| Codec | A compatible option available in OBS, such as H.264 | YouTube’s current live table and the encoder your system supports |
| Rate control | CBR | OBS’s actual output configuration |
| Keyframe interval | 2 seconds recommended; no more than 4 seconds | The selected encoder accepts and applies the interval |
| Bitrate | Match YouTube’s live recommendation to codec and format | Sustained upload with YouTube’s recommended 20% headroom |
| Archive plan | Local recording if the replay matters | File is growing; streams over 12 hours may not be captured by 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
Does YouTube prescribe an OBS preset for all-day streaming?
No. YouTube documents encoder and ingest recommendations, including codec options, CBR, bitrate guidance and keyframe interval. OBS controls and encoders depend on its version and your hardware, so test settings that fit your actual source and connection.
What bitrate should I use for a pre-recorded YouTube stream?
Use YouTube’s live encoder table for the codec, resolution and frame rate you intend to send. For H.264, YouTube recommends 5 Mbps at 1080p30 and 8 Mbps at 720p60, with 3 Mbps listed as the minimum for the latter. Leave the recommended upload headroom and test under realistic network use.
Can YouTube save an all-day stream as a replay?
Not necessarily. YouTube says streams longer than 12 hours may not be captured at all, so keep a local recording if you need an archive and verify that it is being written. Do not assume the Studio replay will contain the full session.
What should I check if the stream drops frames?
Look at both OBS’s indicators and YouTube Studio’s stream health to distinguish network trouble from encoding overload. Network-related dropped frames may call for a lower bitrate or less demanding output; encoding problems may require reducing the computer’s workload or changing an available encoder. Retest the full playback path after making a change.