User Datagram Protocol (UDP)

The User Datagram Protocol (UDP) is a connectionless transport-layer protocol defined in RFC 768. It provides a best-effort (“no guaranteed delivery”) service: UDP sends independent datagrams without establishing a session, and it does not guarantee delivery, ordering, or duplicate protection. Applications must handle any reliability or sequencing they require.

Why UDP is “lightweight”

UDP’s minimal design includes only a small fixed header and intentionally avoids connection setup and built-in reliability mechanisms. As a result, UDP can reduce latency and overhead compared with transport protocols that maintain connection state (e.g., TCP).

Key learning terms (within UDP)

• Datagram
• Connectionless
• Best-effort
• Transport-layer
• Port number

Footnotes

1. RFC 768 — User Datagram Protocol - Summarizes UDP’s connectionless, best-effort, no ordering/reliability characteristics. ↩ ↩²

UDP service characteristics (what UDP does—and does not—provide)

UDP is defined as an unreliable connectionless transport on top of an unreliable network-layer service.2 Concretely:

1. No connection establishment (connectionless)
   UDP does not perform a handshake to set up state between endpoints before sending.2

2. No guaranteed delivery / no retransmissions (unreliable, best-effort)
   UDP does not guarantee that datagrams arrive; loss and duplication are possible and not handled by UDP itself.2

3. No guaranteed ordering
   Because datagrams are independent, they may arrive out of sequence at the receiver.2

4. Integrity checking via checksum (error detection, not recovery)
   UDP includes a Checksum for integrity verification. UDP can detect corruption but does not automatically retransmit or repair lost data.2

Implications for application design

Since UDP doesn’t provide end-to-end reliability or ordering, many real-time applications either:

• tolerate occasional loss/reordering, or
• implement their own selective reliability, buffering, timestamps, or forward error correction at the application layer.

[Pro Tip]{type="tip" title="Pro Tip"} If you need “every byte, in order,” UDP is the wrong tool by itself—use TCP or add application-layer reliability. UDP is ideal when freshness matters more than perfect completeness.2 {type="tip"}

Footnotes

1. The User Datagram Protocol — Computer Networking: Principles, Protocols and Practice - States UDP is defined in RFC 768 and highlights no delivery guarantee and no out-of-sequence protection. ↩ ↩² ↩³ ↩⁴

2. RFC 768 — User Datagram Protocol - Summarizes UDP’s connectionless, best-effort, no ordering/reliability characteristics. ↩ ↩² ↩³ ↩⁴

3. UDP: User Datagram Protocol [RFC 768] - Notes connectionless nature, lack of handshaking, and possibility of loss/out-of-order delivery. ↩ ↩² ↩³

4. What is UDP? | Azion - Discusses UDP as connectionless without handshake/ack/retransmission/ordering and notes typical real-time use. ↩

UDP header format (8 bytes) and fields

A UDP packet consists of a fixed 8-byte UDP header followed by the application payload.2 The header has four 16-bit fields:

These fields are documented in common explanations of UDP structure and align with standard UDP packet layout discussions.3

UDP pseudo-header (checksum computation detail)

For checksum computation, UDP uses information from the IP header (often described as a pseudo-header) to strengthen error detection. This pseudo-header is not transmitted as part of the UDP datagram.

[Warning]{type="warning" title="Warning"} The presence of a UDP checksum means UDP can detect some corruption, but it does not guarantee delivery, ordering, or recovery from loss. Applications still must handle missing datagrams.2 {type="warning"}

Footnotes

1. User Datagram Protocol - Wikipedia - Describes UDP datagram structure and the four header fields. ↩ ↩²

2. UDP: User Datagram Protocol [RFC 768] - Notes connectionless nature, lack of handshaking, and possibility of loss/out-of-order delivery. ↩ ↩²

3. RFC 768 — User Datagram Protocol - Summarizes UDP’s connectionless, best-effort, no ordering/reliability characteristics. ↩ ↩²

4. User Datagram Protocol (UDP) Packet Header — NetworkLessons - Explains UDP header fields and checksum behavior using concrete port/length examples. ↩

5. The User Datagram Protocol — Computer Networking: Principles, Protocols and Practice - States UDP is defined in RFC 768 and highlights no delivery guarantee and no out-of-sequence protection. ↩

UDP in practice: where it’s used

Because UDP minimizes overhead and avoids connection/state management, it’s widely used in low-latency and real-time contexts (where waiting for retransmissions can increase perceived delay).

Common examples include:

• DNS lookups (typically over UDP on port 53)
• VoIP (voice over IP)
• Online gaming
• Real-time media streaming (often built atop UDP using RTP/RTCP)

These use cases and motivations (speed/low overhead with tolerable loss) are repeatedly highlighted in networking resources that discuss UDP’s role in real-time applications and its lack of delivery guarantees.3

UDP and modern transport: QUIC (context)

Many modern web systems use QUIC, which is built to provide reliability and congestion control while still running over UDP. QUIC’s motivation is often described as improving the web experience by adding features that UDP itself lacks.

Footnotes

1. What is UDP? | Azion - Discusses UDP as connectionless without handshake/ack/retransmission/ordering and notes typical real-time use. ↩

2. UDP: User Datagram Protocol [RFC 768] - Notes connectionless nature, lack of handshaking, and possibility of loss/out-of-order delivery. ↩

3. UDP Protocol Explained: Meaning, Header Format, IoT Uses & Security - Lists common UDP use cases and explains UDP’s lightweight rationale. ↩

4. Comparing QUIC and UDP for Enterprise Networks — Lightyear - Explains typical use where QUIC adds reliability/congestion control while leveraging UDP for real-time transport. ↩