Definition
A connectionless transport protocol that sends discrete data packets without establishing a session, confirming delivery, or guaranteeing order, trading TCP's reliability guarantees for minimal overhead and lower latency.
Key Points
- Sends each packet independently without first establishing a connection, meaning there's no handshake delay before data can start flowing and no persistent connection state maintained between endpoints
- Provides no built-in delivery confirmation, retransmission, or ordering guarantee, leaving an application to handle any of those concerns itself if it needs them, rather than receiving them automatically the way TCP provides
- Delivers meaningfully lower overhead and latency than TCP specifically because it skips the handshake, acknowledgment, and retransmission machinery TCP's reliability guarantees require
- Well suited to applications that can tolerate occasional packet loss or reordering in exchange for speed — real-time media, some sensor telemetry — rather than applications where completeness matters more than raw speed
- Provides the underlying transport that QUIC builds its own connection management, reliability, and encryption on top of, letting QUIC implement TCP-like guarantees through a different, more flexible mechanism than operating at the TCP layer directly would allow
Concept
A UDP sender transmits each packet as an independent unit without any prior handshake or ongoing connection state, and the receiver processes whatever packets actually arrive without any built-in mechanism to detect loss, request retransmission, or reorder packets that arrived out of sequence — any of that handling, if an application needs it, must be implemented by the application itself rather than provided automatically by the transport layer.
Explainer
The reason UDP has become the foundation for modern low-latency protocol design rather than being displaced entirely by TCP's reliability guarantees is that UDP's lack of built-in session and reliability machinery is exactly what gives a protocol like QUIC the flexibility to implement its own connection management, reliability, and encryption in a single combined handshake — building those capabilities at the application layer on top of UDP rather than being constrained by TCP's own fixed handshake and acknowledgment behavior at the transport layer itself. This is precisely why UDP and TCP represent genuinely different mechanisms for the same general transport function: UDP's minimal overhead makes it the right choice wherever an application either doesn't need TCP's guarantees or wants to implement its own more tailored version of them, as QUIC does, while TCP remains preferable wherever an application wants those guarantees provided automatically without building them itself. For CE verticals, UDP's low-overhead characteristics make it well suited to real-time and latency-sensitive field applications — sensor telemetry streams tolerant of occasional loss, and increasingly QUIC-based application traffic seeking QUIC's faster connection setup — where TCP's additional handshake and acknowledgment overhead would work against the application's actual performance priorities.
Cite this entry
UDP. ConnectedEarth Knowledge Base. https://connectedearth.space/knowledge-base/udp/ (updated 13 September 2026).