For a 24/7 1080p lecture stream on YouTube, start by setting OBS to 1920×1080 at 30 fps, H.264, CBR and a 2-second keyframe interval. Treat that as a documented baseline to test, not a universal preset: the right bitrate depends on what your upload connection can sustain over time and what your lecture actually contains.
For a mostly still lecturer, slides and occasional gestures, 30 fps is usually a sensible first choice. Before leaving a broadcast running overnight, test the actual computer, encoder, audio and connection together; a setting that works for a short test may not suit continuous operation.
Set the canvas and output resolution
In OBS, set the base (canvas) resolution to fit the material and layout you are building. If your source is a 1920×1080 slide deck with a camera window, a 1920×1080 canvas keeps the working layout aligned with the intended stream size. If the camera or other sources have different dimensions, arrange and scale them on that canvas rather than assuming every source should be stretched to fill it.
Then set the output (scaled) resolution to 1920×1080 if you want the stream delivered in 1080p. The distinction matters: the canvas is the composition you arrange in OBS, while output resolution is the frame size sent to YouTube. If the canvas differs from output, OBS scales the finished composition. Scaling adds work and can soften text, so use a matching canvas and output where practical, and inspect small slide text at the final output size.
A lecture is often easier to read when the slides occupy most of the frame and the speaker remains visible without covering titles or equations. Check the composition with a representative slide, not only a blank background. If you use a recurring pre-recorded sequence rather than a live camera layout, the design decisions in streaming recorded services continuously on YouTube may also help you think through continuity and presentation, though the OBS settings still need testing for your own source.
If your computer struggles to scale or render the composition smoothly, consider whether 1080p is necessary for the source and audience. Lowering output resolution can reduce processing and bandwidth demand, but it also means viewers receive a smaller frame. Do not downscale a crisp slide deck without checking whether fine text remains legible on a phone. The aim is not to select the largest number in a settings menu; it is to deliver a readable picture that the complete setup can maintain.
Choose 30 fps for a static lecture baseline
Set OBS video to 30 frames per second as a starting point for a lecture dominated by slides, a seated speaker and limited movement. A 60 fps stream has more frames each second, but those extra frames may not provide a visible benefit for this material. OBS notes that 60 fps can be more taxing than 30 fps, which matters when an encoder and other applications must keep operating without interruption.
Frame rate is more consequential for rapid motion than for a lecturer pointing at a slide. If the stream includes demonstrations with fast hand movement, camera pans, writing on a board or moving footage, compare 30 fps and 60 fps using the same scene and a sustained test. The higher rate can make motion appear smoother, but it may raise encoding and delivery demands. Do not raise it just because a menu offers the option.
Keep the intended audience in mind as well. YouTube transcodes live streams for different devices and connection qualities, so the uploaded stream is not the only version viewers may receive. The YouTube guidance on live stream transcoding explains that delivery behaviour. That does not remove the need for a clean input: if your original upload drops frames or has unreadable text, a different playback rendition cannot restore the missing detail.
Use a representative section of the lecture to judge the result. Include a slide with small labels, a speaker speaking at their normal pace and any transition or demonstration that recurs. If 30 fps looks clear and stable for those scenes, there is little reason to spend additional processing headroom on a higher frame rate solely for its own sake.
Select H.264 and CBR
Choose H.264 as a broadly compatible starting encoder, then set rate control to CBR (constant bitrate). YouTube's current live encoder guidance lists H.264 settings, including bitrate recommendations, for live ingestion. CBR aims to keep the outgoing rate steady rather than varying it with each scene, which makes it a practical baseline for a service expecting a continuous feed.
CBR does not mean every frame has identical visual complexity or quality. A still slide is easier to encode than a scene with movement, but the encoder works within the chosen rate target. At a constrained bitrate, movement, noise or fine detail can show more compression. A clean camera feed, stable lighting and uncluttered slides help avoid spending bits on unnecessary visual noise.
For hardware encoding, OBS says supported hardware encoders can offload work from the CPU and are generally recommended for performance, while older encoder generations can give lower image quality at the same bitrate. That is a trade-off, not a guarantee that a GPU encoder is always preferable. A hardware encoder that remains stable on your machine may be more useful for a long session than a software encoder that leaves the system overloaded; conversely, a software encoder may produce a better picture at a given rate on a capable machine.
Test available encoder choices with your actual video and computer. Watch OBS for rendering or encoding lag and check the output from YouTube, rather than relying on a short local preview alone. Use a saved OBS profile to keep a tested YouTube configuration distinct from settings for other work; the OBS Studio overview covers profiles and stream setup. If the stream is actually a loop of recorded material rather than an on-air lecture, the operating choices differ; the article on switching between prerecorded videos on a cloud YouTube stream discusses that distinct workflow.
Set the keyframe interval
Set the keyframe interval to 2 seconds. YouTube recommends a 2-second keyframe frequency and says not to exceed 4 seconds in its live encoder settings guidance. In OBS, this is commonly entered in seconds in the output encoder settings; check the field label and selected encoder, since interface wording can vary.
A keyframe is a frame that can be decoded without first relying on earlier frames in the same way as intervening frames do. Regular keyframes help the delivery pipeline and playback systems make use of the stream. The setting is not a cure for weak upload capacity, encoder overload or a poor audio source, and it should not be adjusted casually in search of a sharper image.
If you switch encoders or create another OBS profile, verify the interval again rather than assuming the new profile inherited the tested value. Record the complete configuration somewhere you can refer to it, especially when a different operator may need to restore the channel after a restart. The simple baseline is a 2-second interval, then a test that confirms the encoder actually sends a healthy stream.
Choose a bitrate the upload can sustain
What bitrate should you use for 1080p on YouTube Live? YouTube lists 5 Mbps as a minimum and 14 Mbps as recommended for H.264 1080p30 in its live encoder guidance, current at the research desk's access on 3 October 2026. Those are platform figures, not a promise that an upload connection can sustain 14 Mbps or that every audience will receive a stable stream at that setting.
The practical choice is bounded by the connection's sustained upload capacity, not its best speed-test result. A speed test is a brief sample; a 24/7 stream has to continue while other devices may use the connection, network conditions change, and the router or provider has a poor period. Leave enough headroom for those variations and avoid setting the stream rate at the very top of the connection's measured upload. There is no universal headroom number that can be prescribed without observing the actual line over time.
Start with a bitrate that is appropriate to the footage and comfortably below the upload rate you can sustain in repeated tests. Then watch the stream for long enough to include the usual network conditions, with the computer and router in their normal operating state. If OBS reports dropped frames due to network issues, reduce the bitrate or improve the connection path and retest. If the image is too compressed while delivery remains healthy, you can compare a higher rate only if the connection has room to sustain it.
| What you observe | What to consider next |
|---|---|
| Stable delivery, readable slides, clear voice | Keep the tested rate and configuration; do not change settings without a reason. |
| Network-related dropped frames or repeated health warnings | Try a lower bitrate, a wired connection, or a more reliable upload path, then test again. |
| Stable delivery but blocky motion or noisy camera detail | Reduce visual noise or motion where possible; raise bitrate only if sustained upload capacity allows it. |
| Smooth video but unclear speech | Treat this as an audio capture or mix problem, not a reason to raise video bitrate. |
This table is a troubleshooting guide, not a diagnostic guarantee. A warning can have more than one cause, so read the OBS statistics and YouTube's stream health messages together. For a channel operated from a hosted machine, the article on monitoring YouTube RTMP stream health from an India-based VPS is relevant to delivery checks in that environment; a home broadband operator should still test their own route rather than assume the same results.
Remember that audio also consumes outgoing bandwidth, although it is small relative to video at the listed settings. YouTube lists AAC or MP3 for RTMP/RTMPS, 44.1 kHz for stereo and 128 Kbps for stereo audio. Use a clean, continuously present lecture voice and check levels at normal speaking volume. A microphone that clips, hums or cuts out needs attention at source; changing video bitrate will not correct it.
Use appropriate SDR video settings
For a standard SDR lecture, use progressive scan, square pixels, Rec. 709 colour and 8-bit video as the starting values in OBS. These match YouTube's recommended advanced video parameters for the cited H.264 guidance. Most lecture cameras and slide sources are intended for this sort of conventional SDR delivery, so do not switch colour spaces or HDR settings without a source and workflow that genuinely use them.
Keep the picture consistent. A bright window behind the speaker, flickering room lights or automatic camera exposure changes can make a fixed bitrate work harder and distract viewers. Lock exposure and white balance where the camera allows it, and ensure slide backgrounds and text have enough contrast. These are production checks, not encoding numbers, but they often improve perceived clarity more than an aggressive bitrate change.
YouTube's recommended advanced parameters also include two B-frames, one reference frame and CABAC for H.264. Not every encoder exposes the same controls, and some hardware encoders hide or constrain them. Apply a parameter only if the selected encoder supports it and OBS presents it clearly; do not force a profile or custom command that you cannot verify. The priority is an encoder configuration that sends a compatible and sustained stream, not matching every advanced field by guesswork.
If you are recording locally while streaming, treat recording settings separately from streaming settings. OBS recommends MKV for recording because an ungraceful stop is less likely to corrupt the entire file than with formats that need finalisation. A local archive still needs storage capacity and a recording process that can run as long as intended. The OBS standard recording guide explains the recording format choices.
Test the stream and inspect delivery
Before a public broadcast, test the complete route with representative content and audio. A useful test includes the slide transitions, camera movement, normal speaking level and the device and network arrangement you expect to use overnight. Verify that the right scene is live, the voice remains audible throughout, small text is legible, and YouTube reports healthy delivery. OBS recommends testing before going live; YouTube's live control room provides stream health messages that help identify delivery issues.
Look at OBS statistics while the test runs. Distinguish network drops from rendering lag or encoding lag, because each points to a different part of the system. Network drops call for investigation of upload capacity and network path. Rendering or encoding lag can indicate that the computer or selected encoder cannot keep up with the scene. Change one thing at a time and repeat the test, so you know whether the adjustment helped.
A continuous channel also needs a recovery plan. Enable OBS automatic reconnect and test what happens after a brief network interruption, rather than assuming it will behave as you expect. Check that the stream resumes in YouTube and that the correct scene and audio return. Official guidance does not prescribe one retry interval that fits every 24/7 production, so avoid presenting a particular retry setting as universal. A longer interruption, power loss or operating-system update may need an operator to intervene.
There is a separate issue if you expect YouTube to keep a recording of the whole broadcast. YouTube says streams shorter than 12 hours can be automatically archived, but a stream longer than 12 hours may not be captured at all, according to its live stream archiving guidance. Do not rely on one uninterrupted 24/7 event as your archive. If YouTube archives matter, plan shorter events and verify the current channel workflow; keep a separate local recording if preserving the full programme matters.
That local recording has its own failure modes: disk space can fill, a computer can stop, and recording continuously can add load. Use MKV as OBS recommends for more graceful recovery from an unclean stop, monitor available storage, and test that you can open the resulting files. If an operator cannot reliably keep a computer running through the full schedule, StreamNeo removes that specific burden by running an uploaded video as a YouTube live stream without needing the operator's computer switched on; the stream still needs an appropriate file and channel setup.
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 14 Mbps the best bitrate for every 1080p lecture stream?
No. YouTube lists 14 Mbps as its recommendation for H.264 1080p30, but your upload connection must sustain the selected bitrate and the source may have different demands. Start from the platform guidance, leave practical headroom, and test the actual stream; a lower stable rate is more useful than a higher rate that repeatedly drops.
Does a lecture need 60 fps?
Usually not as a starting point when the lecturer and slides have little motion. OBS notes that 60 fps can be more taxing than 30 fps, so compare both only when fast movement or a specific visual requirement makes the extra frames worthwhile. Judge the result on a representative test, including slide text and camera movement.
Will YouTube save a 24/7 livestream?
Do not rely on a single event lasting longer than 12 hours being archived. YouTube says shorter streams can be automatically archived and warns that a stream beyond 12 hours may not be captured. Segment the broadcast if YouTube archives are needed, and keep a separate local recording if you need a dependable copy of the full programme.
Should I use hardware encoding in OBS?
Use a supported encoder that stays stable on the computer you will actually run. Hardware encoding can offload CPU work, while OBS cautions that older-generation encoders can give lower image quality at the same bitrate. Test the available options with your lecture footage and inspect both OBS statistics and YouTube delivery before settling on one.