YouTube ultra-low latency is a broadcast setting in YouTube, not an OBS encoder preset. In OBS, use a supported ingest protocol and codec, constant bitrate (CBR), a two-second keyframe interval and a bitrate that matches your chosen resolution and frame rate.
Those encoder settings help YouTube receive a correctly configured stream, but they do not select the platform’s latency mode or guarantee a particular delay. Choose ultra-low latency separately in YouTube Live Control Room, and first check that its limitations suit your broadcast.
What ultra-low latency changes—and what it doesn’t
Latency is the time between an action in your broadcast and a viewer seeing it. YouTube’s ultra-low latency mode is intended to reduce that delay compared with the other latency choices in its broadcast settings. It can make a live chat exchange or a spoken response feel more immediate, but the viewer’s network and playback conditions still matter.
OBS controls a different part of the path. It captures or composes your video and audio, encodes them, and sends the resulting stream to YouTube. Codec, resolution, frame rate, bitrate and keyframe interval describe that outgoing contribution. They matter for ingest quality and compatibility, but they do not turn on YouTube’s ultra-low-latency mode.
This distinction is useful when reading guides or looking through encoder menus. An encoder may offer a preset labelled “low latency”, or a setting that reduces local encoding delay. That label describes the encoder’s work, not the latency selection on YouTube. Do not treat it as a substitute for choosing a mode in Live Control Room.
A practical example: a devotional channel can configure OBS to send H.264 video at YouTube’s recommended bitrate for its selected output, with CBR and two-second keyframes. The operator still has to select ultra-low latency in YouTube’s broadcast settings if that is the intended mode. Conversely, selecting ultra-low latency in YouTube does not make an incorrect bitrate or unstable upload connection reliable.
YouTube publishes its encoder settings and bitrate recommendations. The important approach is to keep the two decisions separate: configure OBS for a supported, steady feed, then choose a YouTube latency mode suited to the event and its limitations.
Choose YouTube’s latency mode in Live Control Room
Set the broadcast latency in YouTube’s live setup, rather than hunting for a special OBS profile. In Live Control Room, create or open the broadcast and review the latency option in its stream settings. The available options and page layout can change, so use YouTube’s current controls and help rather than relying on an older screenshot.
The basic sequence is: prepare the broadcast in YouTube, select the desired latency mode, then configure OBS to send the stream to the correct YouTube destination. If the broadcast already exists, confirm its settings before starting. An OBS service configuration can connect to YouTube, but it does not make the platform latency choice on your behalf.
Latency is a trade-off rather than an encoder quality setting. Lower viewer delay is useful when viewers need to follow a live event closely or take part in conversation. A prerecorded music or ambience loop with little interaction may have less reason to prioritise the lowest delay. Consider whether the difference matters to the audience before choosing it.
YouTube’s Live Streaming API documentation describes the supported broadcast latency field and its limits; see the LiveBroadcasts reference. If you manage a channel through a workflow other than the standard Control Room, the API reference can help you understand that platform-side setting. It remains separate from the encoder parameters in OBS.
There is no special bitrate that enables ultra-low latency. Select bitrate for the codec, resolution and frame rate you actually send, using YouTube’s recommendations as a starting point. A value higher than the table suggests is not a reliable shortcut to lower delay, and an upload that cannot sustain the chosen rate can create stream-health problems.
Configure OBS for YouTube ingest
In OBS, set the streaming service to YouTube or the appropriate YouTube ingest configuration for your workflow. Confirm the destination and stream key carefully; a correctly configured encoder sent to the wrong destination will not produce the intended broadcast. Treat the key as private, and do not place it in a screenshot, public chat or article.
For RTMP-based streaming, YouTube recommends RTMPS. The protocol determines how OBS sends the feed; it is not the latency mode. Follow the YouTube configuration and connection details shown for the broadcast, especially if you are using a custom server field or a workflow that does not use OBS’s standard YouTube service selection.
OBS labels and available encoder choices can vary by version, operating system and hardware. Look in the streaming output controls for the encoder, rate-control method, video bitrate and keyframe interval. Do not assume that every reader has the same graphics card or sees the same menu names. The relevant requirements are the output characteristics, not a particular vendor’s preset name.
Pick a codec that YouTube accepts for the selected ingest setup and that your computer can encode consistently. YouTube lists H.264, H.265/HEVC and AV1 as video codec options. Availability on your machine can depend on its hardware and software. If you are unsure, a supported H.264 path is a straightforward starting point; use a more specialised option only when you have verified that OBS, the encoder and YouTube ingest all support it in your setup.
Do not raise the output resolution just because the encoder offers it. The video source, scene, computer and upload connection all need to support the chosen output. For a simple fixed-camera stream, a stable 1080p or 720p output can be more useful than a higher resolution that produces dropped frames or a weak connection. For a longer-running music or local information channel, the considerations in choosing a video format for a 24/7 YouTube stream may help you assess what the source file and output need to do.
Set codec, CBR and keyframe interval
Set rate control to CBR in OBS. Constant bitrate aims to keep the outgoing video rate steady rather than letting it swing with scene complexity. This gives YouTube a predictable contribution to receive. It does not make the connection itself constant, nor can it correct for insufficient upload capacity, packet loss or computer overload.
Set the keyframe interval to two seconds. YouTube recommends a two-second keyframe frequency and says not to exceed four seconds. A keyframe is a complete reference frame in the encoded stream; other frames can depend on it. The interval affects how the stream is structured and is a published ingest recommendation, not a dial for directly choosing viewer latency.
When a field accepts seconds, enter 2. If the field expects frames, consult the encoder’s display and calculate the equivalent for the output frame rate; do not type “2” into a frames field assuming it means seconds. For example, the interval is measured in frames in some controls, so the intended duration depends on how many frames OBS sends each second. Check the resulting setting before broadcasting.
YouTube’s encoder guide gives a maximum of four seconds for the keyframe interval, but the recommended value is two seconds. There is little reason to choose the maximum when setting up a fresh stream against YouTube’s guidance. Keep the keyframe choice the same whether you select normal, low or ultra-low latency in YouTube; it is an ingest configuration, not a latency-mode switch.
For codec selection, match the capability of the local encoder to the ingest requirements and your intended output. Hardware encoding can reduce the work done by the computer’s processor, while software encoding may be available where a hardware option is not. Neither category alone establishes a universally correct choice. Test the actual scene and audio on the machine that will run the broadcast.
You can also read how RTMP destinations work if the distinction between a platform destination and encoder settings is unclear. The practical check is that OBS is sending the intended stream to YouTube using a supported protocol and codec, with CBR and a two-second keyframe interval applied to the output.
Choose bitrate for resolution and frame rate
Set the bitrate according to the resolution and frame rate of the outgoing stream, and check YouTube’s published table for the codec. The values below are H.264 recommendations from YouTube’s encoder guide. They are not a promise of visual quality, a universal rule for all codecs, or a special requirement for ultra-low latency.
| H.264 output | YouTube’s recommended video bitrate |
|---|---|
| 720p at 30 fps | 8 Mbps |
| 720p at 60 fps | 8 Mbps |
| 1080p at 30 fps | 14 Mbps |
| 1080p at 60 fps | 17 Mbps |
If you use H.265/HEVC or AV1, consult the corresponding column in YouTube’s current table rather than copying an H.264 number. The table’s recommendation depends on the codec as well as output size and frame rate. Audio is configured separately from the video bitrate; the figures here refer to video.
The choice between 30 and 60 frames per second depends on the material. A mostly static devotional image, study timer or ambience scene may not need the extra motion detail of 60 fps. A live presenter moving around a room, or a local event with faster action, may benefit from it. Higher frame rate changes the bitrate recommendation and may add work for the encoder, so choose based on what viewers will actually see.
Bitrate is not only a YouTube setting. Your upload connection must be able to sustain the outgoing rate along with other internet use on the same connection. Leave practical headroom rather than planning to consume all available upload capacity with the stream. If household use, mobile-network variation or background backups compete for bandwidth, lower the output resolution or frame rate and test again.
This matters especially on a shared or variable connection. The checklist in our OBS guide for an Indian internet connection can help you think through connection stability as well as the number shown in OBS. A bitrate that matches the recommendation on paper still needs a connection that can deliver it steadily.
When the stream health indicator reports issues, do not respond by raising the bitrate automatically. First check the connection, dropped frames, encoder load and whether the output is appropriate for the available upload. A lower bitrate or less demanding resolution may give viewers a more consistent picture than a larger contribution that repeatedly struggles to reach YouTube.
Check ultra-low latency limitations
Ultra-low latency is not available for every combination of broadcast features and output. YouTube’s API documentation says that ultra-low latency does not support closed captions or resolutions above 1080p. If your broadcast needs captions or needs an output above 1080p, do not plan around ultra-low latency; choose a mode compatible with those needs and confirm YouTube’s current guidance.
YouTube’s encoder help also says 2160p streams cannot use the improve-for-low-latency option and are set to normal latency. That is a separate practical limit worth noting if you are considering a 4K broadcast. It does not mean that choosing an OBS encoder setting will override the platform’s behaviour.
Think about the audience before you trade away features. A live discussion may put value on a quicker response, while a community event may depend on captions for access. A high-resolution nature or music stream may be designed around picture detail and not need a short delay. Neither mode is universally better; the right choice depends on the purpose of the channel.
Do not infer additional promises from the word “ultra-low”. It does not guarantee an exact delay for every viewer, and changing OBS to a low-latency encoding preset cannot make that guarantee. Viewers may have different networks, devices and playback conditions. Treat the mode as a platform choice with trade-offs, then validate the experience with a test broadcast.
Test stream health before going live
Test with the same OBS computer, encoder, output settings and network that you will use for the actual broadcast. Include audio and movement similar to what viewers will encounter. YouTube specifically advises testing before the live stream, with audio and movement like the planned event. A still image alone will not expose every problem that may appear when there is motion or a changing scene.
Check the stream in YouTube’s preview and review the stream-health messages. Confirm that the picture is arriving, audio is audible and in sync, and the output resolution and frame rate are what you intended. Watch for dropped frames or encoder overload in OBS as well as issues reported by YouTube. A clean preview is useful evidence, but it is not a promise that conditions will remain unchanged through a long broadcast.
For an event with chat or spoken interaction, have someone view the stream and report whether the delay feels acceptable. Do not confuse the delay of the preview in your own Control Room with what a viewer sees on a separate device. Make the test useful: open the stream as a viewer, listen on headphones, and try the same sort of movement and speech planned for the live programme.
If the test is unstable, change one thing at a time. Reduce output resolution or frame rate if the computer or connection cannot sustain the current output, then consult YouTube’s bitrate recommendation for the revised setting. If there are audio problems, check the audio source and OBS mixer separately. After each change, repeat the test instead of assuming that one correction fixed every issue.
For a channel that must continue through the night, local OBS settings are only part of the operational plan. The computer, power, connection and operator still matter. If avoiding a running computer is a requirement, a cloud-based workflow such as StreamNeo removes the specific need to leave your own machine switched on for the broadcast; it does not change YouTube’s latency selection or replace checking the ingest settings.
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
Do OBS settings turn on ultra-low latency?
No. OBS encodes and sends the stream, while YouTube’s latency mode is selected in the broadcast settings. CBR, codec, bitrate and keyframe interval help configure ingest; none of them selects ultra-low latency by itself.
What keyframe interval should I set in OBS?
Use two seconds, as YouTube recommends, and do not exceed four seconds. If OBS asks for frames rather than seconds, make sure the value represents a two-second interval at your chosen frame rate.
Is there a special bitrate for YouTube ultra-low latency?
No. Choose a bitrate from YouTube’s table for your codec, resolution and frame rate. The H.264 recommendations include 14 Mbps for 1080p30 and 17 Mbps for 1080p60; these are ingest recommendations, not a latency switch.
Can I use captions or a resolution above 1080p with ultra-low latency?
YouTube’s API documentation says ultra-low latency does not support closed captions or resolutions above 1080p. YouTube also says 2160p streams are set to normal latency when using the low-latency improvement option, so check the current official guidance when planning the broadcast.