Latency is the delay between something happening in front of your camera and your viewers seeing it — measured in seconds.
Latency describes the gap between a real-world event and the moment viewers see it. Your audio and video must be captured, encoded, uploaded over RTMP, processed by the platform, distributed through a CDN and finally decoded on the viewer's device. Every link in that chain adds delay.
Your encoder buffers a small number of frames before output. Your keyframe interval determines how quickly a new viewer can start decoding. The platform's transcoding pipeline adds a second or two. The player itself buffers several seconds to protect against network jitter — this is usually the single largest contributor and the part you cannot control.
On Twitch, open the Creator Dashboard → Settings → Stream and set Latency mode to Low Latency. Keep your keyframe interval at 2 seconds, use CBR rate control, and stream over wired Ethernet. Chasing latency by lowering the keyframe interval below 2 seconds costs bitrate and usually breaks platform requirements.
High latency makes viewer interaction feel disconnected — you ask chat a question and the answer arrives half a minute later. Lower latency keeps the stream feeling live, which is the entire reason viewers choose live content over a VOD.
Slightly. A shorter buffer gives viewers less protection against network jitter, so viewers on weak connections may buffer more often. For most channels the interaction benefit outweighs it; if a large share of your audience reports buffering, switch to Normal.
Delays that long usually indicate Normal latency mode combined with a long keyframe interval, or a viewer-side player buffering aggressively. Check your latency mode first, then confirm the keyframe interval is set to 2 seconds.
No. Latency is buffering and routing delay; dropped frames are frames discarded because the upload could not keep up. They are separate problems with separate fixes.