User Datagram Protocol (UDP)

What is User Datagram Protocol (UDP)?

User Datagram Protocol (UDP) is a communications protocol that is primarily used to establish low-latency and loss-tolerating connections between applications on the internet.

UDP speeds up transmissions by enabling the transfer of data before an agreement is provided by the receiving party. As a result, UDP is beneficial in time-sensitive communications, including voice over IP (VoIP), domain name system (DNS) lookup, and video or audio playback.

UDP is an alternative to Transmission Control Protocol (TCP). Both UDP and TCP run on top of IP and are sometimes referred to as UDP/IP or TCP/IP. However, there are important differences between the two. For example, UDP enables process-to-process communication, while TCP supports host-to-host communication.

TCP sends individual packets and is considered a reliable transport medium. On the other hand, UDP sends messages, called datagrams, and is considered a best-effort mode of communications. This means UDP doesn't provide any guarantees that the data will be delivered or offer special features to retransmit lost or corrupted messages.

UDP provides two services not provided by the IP layer. It provides port numbers to help distinguish different user requests. It also provides an optional checksum capability to verify that the data arrived intact.

User Datagram Protocol features

User Datagram Protocol has attributes that make it beneficial for use with applications that can tolerate lost data. Below are some examples:

  • It allows packets to be dropped and received in a different order than they were transmitted, making it suitable for real-time applications where latency might be a concern.
  • It can be used for transaction-based protocols, such as DNS or Network Time Protocol (NTP).
  • It can be used where a large number of clients are connected and where real-time error correction isn't necessary, such as gaming, voice or video conferencing, and streaming media.

UDP header composition

UDP uses headers when packaging message data to transfer over network connections. UDP headers contain a set of parameters -- called fields -- defined by the technical specifications of the protocol.

The User Datagram Protocol header has four fields, each of which is 2 bytes. They are the following:

  • source port number, which is the number of the sender;
  • destination port number, the port to which the datagram is addressed;
  • length, the length in bytes of the UDP header and any encapsulated data; and
  • checksum, which is used in error checking -- its use is required in IPv6 and optional in IPv4.
UDP header format
The composition of the four UDP header fields: source port, destination port, UDP length and checksum

How UDP works

UDP uses IP to get a datagram from one computer to another. UDP works by gathering data in a UDP packet and adding its own header information to the packet. This data consists of the source and destination ports on which to communicate, the packet length and a checksum. After UDP packets are encapsulated in an IP packet, they're sent off to their destinations.

Unlike TCP, UDP doesn't guarantee the packets will get to the right destinations. This means UDP doesn't connect to the receiving computer directly, which TCP does. Rather, it sends the data out and relies on the devices in between the sending and receiving computers to correctly get the data where it's supposed to go.

Most applications wait for any replies they expect to receive as a result of packets sent using UDP. If an application doesn't receive a reply within a certain time frame, the application sends the packet again, or it stops trying.

UDP uses a simple transmission model that doesn't include handshaking dialogues to provide reliability, ordering or data integrity. Consequently, UDP's service is unreliable. Packets may arrive out of order, appear to have duplicates or disappear without warning.

Although this transmission method doesn't guarantee that the data being sent will reach its destination, it does have low overhead and is popular for services that don't absolutely have to work the first time.

Applications of UDP

Lossless data transmission

UDP can be used in applications that require lossless data transmission. For example, an application that is configured to manage the process of retransmitting lost packets and correctly arrange received packets might use UDP. This approach can help to improve the data transfer rate of large files compared to TCP.

In the Open Systems Interconnection (OSI) communication model, UDP is in Layer 4, the transport layer. UDP works in conjunction with higher-level protocols to help manage data transmission services, including Trivial File Transfer Protocol (TFTP), Real Time Streaming Protocol (RTSP) and Simple Network Management Protocol (SNMP).

Gaming, voice and video

UDP is an ideal protocol for network applications in which perceived latency is critical, such as in gaming, voice and video communications. These examples can suffer some data loss without adversely affecting perceived quality. In some cases, however, forward error correction techniques are used in addition to UDP to improve audio and video quality, despite some loss.

Services that don't need fixed packet transmission

UDP can also be used for applications that depend on the reliable exchange of information but should have their own methods to answer packets. These services are advantageous because they're not bound to fixed patterns to guarantee the completeness and correctness of the data packets sent. Users can decide how and when to respond to information that's not correct or sorted.

Multicasting and routing update protocols

UDP can also be used for multicasting because it supports packet switching. In addition, UDP is used for some routing update protocols, such as Routing Information Protocol (RIP).

Fast applications

UDP can be used in applications where speed rather than reliability is critical. For instance, it might be prudent to use UDP in an application sending data from a fast acquisition where it's OK to lose some data points.


TCP and UDP are part of the TCP/IP protocol suite, which includes a number of protocols for carrying out network communications.

Comparison chart of TCP and UDP
Compare some of the main differences between TCP and UDP.

TCP has emerged as the dominant protocol used for the bulk of internet connectivity due to its ability to break large data sets into individual packets, check for and resend lost packets, and reassemble packets in the correct sequence. But these additional services come at a cost in terms of additional data overhead and latency.

In contrast, UDP is considered a connectionless protocol because it doesn't require a virtual circuit to be established before any data transfer occurs. The communication protocol just sends the packets, which means it has much lower bandwidth overhead and latency. With UDP, packets may take different paths between sender and receiver. As a result, some packets may be lost or received out of order.

UDP characteristics include the following:

  • It is a connectionless protocol.
  • It is used for VoIP, video streaming, gaming and live broadcasts.
  • It is faster and needs fewer resources.
  • The packets don't necessarily arrive in order.
  • It allows missing packets -- the sender is unable to know whether a packet has been received.
  • It is better suited for applications that need fast, efficient transmission, such as games.

TCP characteristics include the following:

  • It is a connection-oriented protocol.
  • It's the most widely used protocol on the internet.
  • It guarantees that no packets are missing and all sent data makes it to the intended recipient.
  • It sends packets in order so they can be stitched back together easily.
  • It's slower and requires more resources.
  • It has a bigger header than UDP.
  • It is best suited for apps that need high reliability, and transmission time is relatively less critical.
This was last updated in October 2021

Continue Reading About User Datagram Protocol (UDP)

Dig Deeper on Network Infrastructure

Unified Communications
Mobile Computing
Data Center