To make OBS launch a 4K 60fps YouTube Live stream when you sign in to Windows, configure OBS’s video and encoder settings, add OBS to Windows startup, and pass it the --startstreaming launch parameter. YouTube’s auto-start setting is a separate part of the process: launching OBS does not by itself prove that a broadcast has begun.
Set up and test each part before relying on it unattended. A 4K60 stream puts demands on the encoder, scene and upload connection, so the settings below are a starting configuration to validate on your own PC, not a guarantee that every machine or connection can sustain it.
Set OBS to output 3840×2160 at 60 fps
Open OBS and go to Settings > Video. Set Output (Scaled) Resolution to 3840x2160, and set Common FPS Values to 60. The output resolution is what OBS sends; the base canvas controls the space in which you arrange sources. If your canvas is a different size, OBS may scale it, so check the composition and text for softness or cropping in a test.
Use a scene that resembles the one you will actually broadcast. A still image with a modest audio visualiser has a different load from several animated browser sources, transitions and video layers. OBS notes that resolution, frame rate, encoder and scene complexity all affect the workload. Check the preview, dropped frames and rendering or encoding warnings while you test, rather than assuming that selecting 60 fps means the PC is maintaining it.
If a 4K output is not essential, consider whether 1440p or 1080p at 60 fps better fits your viewers and equipment. You can change the output resolution and test again; do not quietly lower the output while believing the service is receiving 4K. The distinction between canvas and output also matters when sources are reused. For a continuous visual loop, review the practical points in using the same ambience video in a 24/7 YouTube loop, then verify the actual OBS output separately.
Choose an encoder and bitrate for your setup
In Settings > Output, set the output mode to Advanced if needed, then choose an encoder available in your OBS installation. Depending on the PC, drivers and OBS version, choices may include hardware encoders such as NVIDIA NVENC, AMD AMF or Intel Quick Sync, or a software encoder. Hardware encoding can move work away from the CPU, but the available generation and quality vary. No one choice fits every PC.
YouTube’s published bitrate guidance for 2160p at 60 fps differs by codec. The figures below are YouTube recommendations, not a promise that an upload connection or encoder will sustain the stream. YouTube’s help page does not state a publication date for this guidance; figures are from the page as consulted in October 2026.
| Codec | YouTube-listed minimum for 2160p60 | YouTube-recommended bitrate for 2160p60 |
|---|---|---|
| AV1 or H.265 (HEVC) | 10 Mbps | 35 Mbps |
| H.264 | 14 Mbps | 50 Mbps |
Choose a codec supported by the encoder you have selected and accepted by YouTube’s current ingest guidance. Enter a bitrate appropriate to that codec and test whether the connection can sustain it with headroom. A speed test is only a snapshot: other household or office traffic, Wi-Fi variation and the route to YouTube can affect the real stream. If the upload fluctuates or YouTube reports poor health, try a lower output or bitrate and repeat the representative test.
YouTube’s general encoder guidance recommends RTMPS, constant bitrate (CBR) and a two-second keyframe interval, and says not to exceed four seconds. Match OBS’s available settings to YouTube’s current live encoder settings guidance. Some choices depend on codec and mode; do not assume a setting shown for one codec applies identically to another. For SDR, YouTube’s advanced guidance also covers progressive scan, square pixels, Rec. 709 and 8-bit colour. For stereo audio it lists AAC at 44.1 kHz. Check the current official page if your format differs or the interface has changed.
At 4K, YouTube uses normal latency; its low-latency optimisation is not available for 4K streams. If rapid chat interaction is central to your channel, factor that into the resolution decision. A practical way to diagnose 60fps problems is to change one variable at a time; the checks in this guide to YouTube Live 60fps stutter at a stable bitrate can help separate encoder load from other causes.
Create or select the YouTube stream for OBS
Before configuring OBS’s service connection, make sure live streaming is enabled for your channel and create or select the intended event in YouTube Studio’s Live Control Room. YouTube says first-time live streaming activation may take up to 24 hours, so do not leave channel eligibility and activation until the moment of a planned launch. See YouTube’s instructions to create a live stream with an encoder.
In YouTube Studio, select the stream or scheduled event and locate its stream key and server URL. In OBS, open Settings > Stream, select YouTube as the service, and connect using the option available in your version, such as account connection or stream key. If you use a key, treat it as a password: anyone who obtains it may be able to send a feed to your stream. Keep it out of screenshots and shared documents, and reset it in Studio if you believe it has been exposed. YouTube explains how stream keys connect an encoder to a live stream.
Confirm that OBS is using the intended stream and profile. A saved profile can contain different output settings, and an older scene collection may not have the scene you expect. If you manage more than one channel or event, label profiles and shortcuts clearly. Before scheduling an unattended start, manually connect OBS to a private or otherwise controlled test stream and confirm that Studio receives the picture and audio you intended.
Start OBS when you sign in to Windows
The simplest Windows method is a shortcut in your user Startup folder. First check Settings > Apps > Startup or Task Manager > Startup apps in Windows 10 or 11; if OBS is listed and enabled, that may be all you need to launch the application at sign-in. Microsoft documents the Startup folder method for apps that are not listed there.
To open your user Startup folder, press Windows key + R, enter shell:startup, and press Enter. Add a shortcut to OBS there. You can find the OBS shortcut in the Start menu, right-click it and choose Open file location, then copy or create a shortcut in the Startup folder. This applies to the account that signs in. The shell:common startup folder is for shortcuts intended for all users and may require administrator permission.
This step launches the OBS application, not necessarily the broadcast. If the PC is shared, consider who can sign in to the account and whether OBS should start for every user. A Startup-folder shortcut is easy to inspect and remove. If you need a deliberate delay, conditions or a logon trigger, Windows Task Scheduler can be used instead, but it requires careful configuration. For either method, make sure the intended Windows account is interactive and the desktop session is available to OBS.
Add and test OBS’s --startstreaming parameter
OBS supports a launch parameter that tells it to start streaming as it opens. To add it, locate the OBS shortcut you placed in Startup, right-click it and open Properties. In Target, leave the executable path intact, including its quotation marks, and add a space followed by --startstreaming after the closing quote. The target will resemble:
"C:\Program Files\obs-studio\bin\64bit\obs64.exe" --startstreaming
Your OBS installation may be in a different folder; use the path on your PC rather than copying the example blindly. In the shortcut’s Start in field, set the directory containing obs64.exe, as OBS advises for automated launches. This helps Windows start OBS with the appropriate working directory. See the OBS launch parameters documentation for the current instructions.
Test the modified shortcut by closing OBS completely and opening the shortcut manually. Confirm that the intended profile and scene load, and observe whether OBS attempts to connect. A parameter is only a request to OBS to begin streaming: it does not create a YouTube event, select the correct key, supply a missing network connection or override YouTube’s stream settings. If OBS opens but does not connect, inspect the stream settings and logs rather than repeatedly clicking or changing multiple settings at once.
Only enable this parameter in the sign-in shortcut after you have tested its effect with a controlled stream. If you need OBS to open for editing without going live, keep a second shortcut without --startstreaming, or temporarily remove the parameter from the Startup shortcut. Make the difference visible in the shortcut name so someone using the PC does not mistake a normal OBS launch for an intentional broadcast.
Check YouTube auto-start and the broadcast state
YouTube’s stream settings govern what happens when an encoder connects. In the Live Control Room, inspect the intended stream’s auto-start setting and decide whether an incoming encoder feed should begin the broadcast automatically. This is distinct from OBS’s launch parameter: --startstreaming asks OBS to send the feed, while YouTube’s auto-start setting determines whether that connection initiates the event. Check YouTube’s current interface and official instructions because controls can change.
Decide how you want to end the stream as well. Auto-stop is a separate YouTube stream setting; understand its effect before using it for a channel expected to remain available. A connection can drop and return, and you need to know what Studio will show during that sequence. Do not infer that the event is live merely because the OBS status bar says it is streaming. Confirm the stream state in YouTube Studio and check that the viewer-facing page behaves as intended.
For a scheduled broadcast, verify the event date and time, visibility and the stream attached to it. If you have set YouTube to wait for a manual start, OBS can be connected while the event has not yet been started. Conversely, with auto-start enabled, a connection made during a test may start the event sooner than expected. Use a private test or a separate controlled event, and keep the stream key for the production event out of test shortcuts and shared notes.
Run a private preflight and check recovery
Do not make the first test a sign-in after an overnight update. YouTube advises testing before a live stream and monitoring stream health and messages. Use a private or scheduled preflight that mirrors the real scene, audio and duration as closely as practical. Keep the first automated test supervised so you can stop it if the wrong event begins or the picture, sound or bitrate is not right.
A useful check follows the whole chain. Restart Windows and sign in to the account that will run the channel. Confirm OBS opens with the right profile and scene; confirm the correct stream is selected; and see whether the launch parameter initiates a connection. In Studio, check whether the stream is still waiting, has started, or reports an error. Inspect the incoming resolution and frame rate, audio, stream health and warnings. A desktop preview alone does not establish that YouTube is receiving a healthy 2160p60 feed.
Include realistic movement and sound in the test. A static slide may conceal dropped frames or audio problems that appear in the actual programme. If YouTube reports a problem, note the message and change one setting at a time. Check the encoder selection, CBR and keyframe settings, bitrate, network path and scene load. A stable bitrate does not necessarily mean smooth 60fps playback, so test both the ingest status and what a viewer sees.
Then test recovery deliberately while supervised. Briefly interrupt the network or stop and restart the OBS connection, and observe what OBS and Studio do. Verify whether OBS reconnects, whether YouTube resumes the intended event or waits for action, and whether audio and video return. There is no setting that makes every PC, network interruption or YouTube state behave identically; document the actual result and choose a recovery procedure someone can follow.
If this computer must remain on for every broadcast, account for Windows updates, power settings, login requirements and household or business network use. A Startup shortcut cannot run before the relevant user signs in, and an automatic start should not conceal an unattended failure. For a channel whose main job is to repeat a prepared file rather than operate an interactive OBS scene, compare the workflow with running a YouTube Live loop from a cloud server. That approach has its own trade-offs and is not a substitute for checking stream state or rights to the content.
If your actual need is to keep a prepared video broadcasting without leaving a PC powered and signed in, StreamNeo can remove that particular computer-at-night burden by taking an uploaded video and running it as a YouTube live stream; it does not replace OBS for a live, interactive scene or make YouTube settings unnecessary.
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 --startstreaming make YouTube go live automatically?
It tells OBS to start streaming when OBS launches, but YouTube’s auto-start setting is separate. Check the event’s state in Live Control Room and test the exact combination you plan to use. A successful OBS launch is not proof that the public broadcast is live.
Can my PC handle 4K60 because OBS offers the setting?
Not necessarily. Available encoder hardware, its generation, scene complexity and sustained upload all affect the result. Run a representative test and monitor YouTube’s stream health before relying on the setup.
Should I use H.264, H.265 or AV1?
Choose among codecs supported by both your installed encoder and YouTube’s current ingest options. YouTube’s recommended 2160p60 bitrate differs by codec, and image quality and performance vary by hardware generation. Compare with your own test rather than assuming one codec is best for every PC.
What if I want OBS to open without going live?
Use a shortcut without --startstreaming for ordinary editing, or remove the parameter from the Startup shortcut until you need it. You can also leave YouTube auto-start disabled and start the event manually after checking Studio. Keep the testing and production shortcuts clearly labelled.