Protocol ExplorerGuidesPricing

UDP Protocol: Datagrams, Ports and Delivery Limits

User Datagram Protocol carries independent datagrams between applications. It adds port addressing and a checksum but leaves delivery, ordering and recovery to the application or a protocol built above it.

Updated · Editorial approach and simulation limits

A UDP header is small and message boundaries remain visible

A UDP header contains source port, destination port, length and checksum. The length covers the UDP header and payload. Unlike TCP’s byte stream, each UDP datagram preserves a message boundary for the receiving application.

A UDP packet may have a zero source port in some uses, and IPv4 and IPv6 checksum rules differ. A malformed length or checksum can cause a receiver to discard a datagram before the application sees it.

UDP does not provide reliable delivery

UDP has no handshake, acknowledgments, retransmissions, ordering or congestion control in its base header. A datagram can be lost, duplicated or delivered out of order. Applications that need reliability must implement it or use a transport such as QUIC.

A response in one UDP-based application does not turn UDP into a connection-oriented protocol. DNS, NTP, media and QUIC use different application behavior over the same datagram service.

Ports identify an application endpoint, not the whole service

Ports help a host deliver a datagram to a socket. A familiar destination port is only a hint about the application; services can use alternate ports, NAT can rewrite them, and one port can carry different protocols in different contexts.

When reading a trace, group datagrams by endpoint tuple and inspect the application payload if it is visible. For encrypted protocols, use endpoint logs or authorized keys. Protocol Explorer’s UDP lesson shows datagram delivery and does not promise that a real network will return a reply.

Explore UDP interactively

Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.

Open the UDP animation · Compare Free and Pro

Specification and source

For exact protocol requirements, consult the primary document: RFC 768: User Datagram Protocol. This page summarizes selected behavior and is not a substitute for the specification.

Related protocol lessons

Browse all transport protocols · Compare UDP-based QUIC with TCP