What is low latency? Meaning, contexts, and why it is not always the same thing
Low latency means the delay between an action and its result is small enough that the system feels fast for the job. The important part is that “small enough” changes with context. In a contribution workflow, it may mean fast transport between endpoints. In viewer playback, it may mean reducing the gap between the event and the screen. In an interactive session, it may mean people can respond to each other without awkward delay.
That is why the phrase causes confusion. Teams use “low latency” as if it were one fixed number, but in practice it is a relative term. It only becomes useful when you ask what kind of workflow is involved and where the delay is being measured.
Quick answer: what does low latency mean?
Low latency means there is very little delay between source and outcome relative to the needs of the workflow. It does not automatically mean real time, and it does not automatically mean the system is stable, scalable, or the best choice for every kind of video delivery.
| Context | What low latency usually means | What people often confuse it with |
|---|---|---|
| Transport | Fast movement of media between systems | Overall workflow quality |
| Playback | Small delay between live event and audience playback | No buffering or perfect reliability |
| Interaction | Fast enough response for conversation or participation | Mass-scale one-to-many delivery |
Low latency is about delay, not about one protocol or one platform
The term describes an outcome, not a single technology. Different systems reach low latency in different ways, and each one makes trade-offs around resilience, playback compatibility, scale, or interactivity. That is why it is more useful to define the job first than to assume one protocol wins all low-latency work.
Low latency is not the same as real time
People often use those two phrases interchangeably, but they are not identical. Low latency means delay is reduced. Real time usually implies a tighter expectation where participants can react almost immediately. A workflow can be low latency without feeling truly real time, especially when playback buffering or multi-stage delivery is still involved.
Low latency is not the same as reliability
A very fast workflow can still be fragile. It may break under packet loss, scale poorly, or become unstable under load. That is why experienced teams do not evaluate low latency by the smallest possible number alone. They evaluate whether the delay is acceptable while the workflow remains usable.
Where teams usually get confused
Most confusion comes from collapsing different jobs into one phrase. Contribution, playback, and interaction are not the same problem. A team may say it needs low latency when what it really needs is better contribution transport, lower player delay, or a true interactive path between participants.
If you are deciding how to implement low-latency delivery in practice, use the broader guide at low-latency. That page is the better route when the question has moved from “what does the term mean?” to “how should the workflow be designed?”
FAQ
What is the simplest definition of low latency?
It means the delay between an action and its visible or audible result is very small for the specific use case.
Does low latency always mean interactive?
No. A stream can be lower latency than normal playback without being interactive enough for two-way participation.
Does low latency guarantee a better viewer experience?
No. Viewer experience also depends on stability, buffering behavior, playback support, and the overall workflow design.
Final practical rule
Use “low latency” as a meaning word first, not a marketing word. Decide whether you are talking about transport, playback, or interaction, then choose the implementation path that fits. When the question becomes architectural, continue with the practical guide at /low-latency.