What is User Datagram Protocol (UDP)?

What is User Datagram Protocol (UDP)?

User Datagram Protocol (UDP) is a network protocol that operates at the transport layer of the Internet Protocol (IP) suite. It's designed to provide a lightweight and low-overhead method for sending datagrams, or chunks of data, across a network.

Unlike the Transmission Control Protocol (TCP), which provides reliable and ordered data delivery, UDP is a connectionless protocol. This means it doesn't establish a connection between the sender and receiver before data transmission. Instead, UDP treats each datagram as an independent unit, with no guarantee of delivery or order.

One of the key advantages of UDP is its simplicity and efficiency. UDP has lower overhead and latency by eliminating the need to establish and maintain a connection than TCP. This makes it ideal for applications that require fast and real-time data transmission, such as online gaming, streaming media, and voice-over IP (VoIP) services.

However, the lack of reliability in UDP can also be a drawback in certain scenarios. Since it does not provide acknowledgments or retransmissions, any lost or corrupted packets may go unnoticed. This makes UDP less suitable for applications that require guaranteed delivery, such as file transfers or email.

UDP is often used with other protocols, such as IP and application layer protocols like Domain Name System (DNS) and Simple Network Management Protocol (SNMP). These protocols can utilize UDP's speed and low overhead for efficient data transfer.


UDP (User Datagram Protocol) and TCP (Transmission Control Protocol) are both transport layer protocols used in computer networks. While they serve the same purpose of facilitating communication between devices, there are several key differences between UDP and TCP.

Connection-oriented vs Connectionless

TCP is a connection-oriented protocol, which means it establishes a reliable, two-way communication channel before data transmission begins. It ensures that all packets are received in order and without errors. UDP is connectionless, meaning it does not establish a dedicated connection before sending data. Each packet is treated as an independent unit and can be sent without prior knowledge of the receiver's state.


TCP provides reliable data transmission by implementing error detection, error correction, and flow control mechanisms. It guarantees that all packets are received in the correct order and without loss or corruption. UDP, on the other hand, does not provide built-in reliability mechanisms. It does not guarantee delivery, and packets may be lost, duplicated, or out of order.

Ordering and congestion control

TCP ensures the ordered delivery of data packets, meaning the receiver receives and reconstructs the data in the same order as it was sent. UDP does not guarantee ordering, and packets may arrive at the destination in any order. Similarly, TCP has congestion control mechanisms to avoid network congestion and prevent data overflow, whereas UDP does not have built-in congestion control. UDP applications need to implement their congestion control mechanisms if necessary.


TCP has a higher overhead compared to UDP. TCP includes additional information in each packet to ensure reliability, such as sequence numbers, acknowledgments, and checksums. In contrast, UDP has a lower overhead as it does not include these additional mechanisms. This makes UDP a lightweight protocol, suitable for applications requiring low latency and tolerant to packet loss.

Use cases

TCP is commonly used for applications requiring reliable and ordered data delivery, such as web browsing, file transfers, and email. It is also used for protocols that rely on a continuous data stream, such as streaming media. UDP is preferred for applications prioritizing speed and low latency over reliability, such as real-time communication, video streaming, online gaming, video conferencing, and voice-over IP (VoIP).

Firewall traversal

Because TCP establishes a connection before data transmission, traversing firewalls and network address translation (NAT) devices is generally easier. UDP, being connectionless, may encounter more difficulties in traversing firewalls and NAT devices, as they typically rely on tracking connections. However, techniques like UDP hole punching can overcome these challenges.

Header size

The UDP header is smaller than the TCP header. The UDP header consists of only four fields: source port, destination port, length, and checksum. This smaller header size contributes to UDP's lower overhead and faster transmission than TCP.

What are the advantages of using UDP over TCP?

UDP has several advantages over TCP in certain scenarios. Here are a few more:

Reduced latency: UDP does not perform extensive error checking or retransmission of lost packets, which reduces latency. UDP can deliver better performance by minimizing delays in time-sensitive applications like online gaming or VoIP, where real-time communication is crucial.

No congestion control: Unlike TCP, UDP does not have built-in congestion control mechanisms. While this may seem to be a disadvantage, it can be advantageous in some situations. For example, in scenarios where packet loss is tolerable, such as live video streaming, UDP can provide a smoother experience by not slowing down the transmission for congestion control.

Broadcast and multicast support: UDP supports broadcasting and multicasting, allowing applications to send data to multiple clients simultaneously. This is useful when data must be distributed to multiple recipients, such as video streaming to multiple viewers or networked multiplayer games.

Simple implementation: UDP is simpler than TCP, which requires fewer system resources and can be more easily integrated into different applications. This simplicity makes UDP a popular choice for applications where speed and efficiency are critical, such as realtime communication, multimedia streaming, and IoT (Internet of Things) devices.

While UDP offers these advantages, it also has some limitations. Since UDP does not provide error checking or retransmission of lost packets, it's unsuitable for applications requiring reliable data delivery, such as file transfers or web browsing. Additionally, UDP doesn't guarantee the order of packet delivery, so UDP may not be the best option for applications that rely on strict sequencing of packets.

How does UDP provide error handling?

While UDP itself doesn't provide error handling, app developers can implement their error-handling mechanisms on top of UDP. Here are some common approaches:

  • Application-Level Error Handling: The application layer can include error detection and recovery mechanisms. For example, checksums or hash functions can detect errors in the received data. If an error is detected, the application can request a retransmission or take appropriate action based on the application's specific requirements.

  • Sequence Numbers: Applications can assign sequence numbers to each piece of data sent over UDP. The receiver can use these sequence numbers to determine whether packets are missing or out of order. If a packet is missing, the application can request a retransmission. Sequence numbers can also be used to reorder packets at the receiver's end.

  • Timeout and Retransmission: Applications can implement a timeout mechanism to detect lost packets. If a packet is not received within a certain time frame, the application can assume it is lost and request a retransmission. This can be combined with sequence numbers to ensure that lost packets are retransmitted in the correct order.

  • Forward Error Correction (FEC): FEC is a technique where redundant data is added to the original data before transmission. This allows the receiver to recover from errors without requiring retransmissions. UDP-based applications can implement FEC algorithms to provide error recovery capabilities.

  • Error Correction Codes: Error correction codes, such as Reed-Solomon codes, can detect and correct errors in UDP packets. These codes add redundant information to the data, allowing the receiver to identify and fix errors. However, implementing error correction codes can introduce additional overhead and complexity.

While these error-handling mechanisms can improve the reliability of UDP-based applications, they can't guarantee the same level of reliability as TCP. UDP is still susceptible to network congestion, packet loss, and other issues that can affect data delivery.

UDP Use Cases

While UDP lacks the reliability features of TCP, it has various use cases where its speed and simplicity are advantageous. Some common use cases include:

  • Real-Time Applications: UDP is commonly used in real-time applications where low latency is crucial, such as video and audio streaming (think Zoom or Facetime), online gaming, and VoIP services (like Whatsapp and Google Hangouts). These applications prioritize speed over reliability, as minor data loss or delay is more acceptable than retransmissions and increased latency.

  • IoT (Internet of Things): UDP is often used in IoT devices or sensor networks where real-time data from multiple sources needs to be transmitted quickly. UDP's simplicity and low overhead suit applications requiring a lightweight data transmission protocol.

  • DNS (Domain Name System): UDP is the primary protocol for DNS queries. DNS servers handle a high volume of queries, and UDP's low overhead and connectionless nature make it well-suited for this purpose. In cases where a response exceeds the maximum size of a UDP packet, TCP may be used instead.

  • DHCP (Dynamic Host Configuration Protocol): DHCP servers use UDP to assign IP addresses and network configuration parameters to client devices. UDP allows for faster and more efficient IP address assignment, eliminating the need for establishing a TCP connection for each client.

  • Network Monitoring and Management: UDP is commonly used in network monitoring and management systems, where speed and efficiency are critical. UDP is often used for sending network statistics, monitoring data, and alerts between network devices and management systems. Its low overhead and connectionless nature make it suitable for quick and lightweight communication in these scenarios.

  • Broadcast and Multicast Applications: UDP is frequently used in broadcast and multicast applications, where data needs to be sent to multiple recipients simultaneously. Unlike TCP, which requires a separate connection for each recipient, UDP allows for efficient one-to-many or many-to-many communication. This makes UDP suitable for live video streaming, online conferencing, and event broadcasting applications.

What is the default port for UDP?

The default port for UDP (User Datagram Protocol) is 0. UDP is a connectionless protocol that does not require a dedicated port for communication. Unlike TCP (Transmission Control Protocol), which has well-known port numbers for specific services, UDP does not have a default port number. UDP packets are identified by the source and destination IP addresses and the source and destination port numbers specified within the packet's header. This flexibility allows UDP to be used for a wide range of applications and services. Application developers can choose any port number for their UDP-based applications if another service or application hasn't already reserved it.


NTP (Network Time Protocol) utilizes UDP as its underlying transport protocol for transmitting time synchronization information.

NTP leverages the characteristics of UDP to transmit time-related data between devices in a network. The NTP client sends time synchronization requests to the NTP server using UDP packets. The server responds with UDP packets containing the requested time information.

The use of UDP in NTP allows for faster transmission of time data compared to other protocols that require establishing a connection and ensuring reliable delivery. Since time synchronization is a critical aspect of many networked systems, the low-latency nature of UDP is beneficial in ensuring timely updates of device clocks.

However, the use of UDP in NTP also means that there is a possibility of packet loss or corruption during transmission. NTP includes error detection mechanisms such as the UDP Checksum to mitigate this. The UDP Checksum helps ensure the integrity of data transmitted over the network by calculating a checksum value based on the packet contents and verifying it at the receiving end. The packet may have been altered during transmission if the checksum field does not match.

Developers implementing NTP in their applications must know the UDP characteristics and potential transmission errors. By utilizing the UDP Checksum and other error detection mechanisms, they can ensure the reliability and integrity of time synchronization data.

Another important aspect of NTP's relationship with UDP is the use of port numbers. UDP uses port numbers to identify a device's destination application or service. NTP uses port number 123 as the default port for communication between NTP clients and servers. This allows devices to differentiate between NTP traffic and other UDP traffic.

NTP also includes security and authentication mechanisms to ensure the trustworthiness of time information. This is especially important when malicious actors attempt to tamper with time synchronization for nefarious purposes.

NTP provides cryptographic authentication mechanisms to verify the identity of NTP servers and prevent unauthorized servers from providing time information. It uses symmetric key cryptography or public-key cryptography to authenticate the server and protect against man-in-the-middle attacks.

Additionally, NTP includes access control lists (ACLs) to further restrict access to time information. ACLs allow administrators to specify which devices can query their NTP server and synchronize clocks. This helps prevent unauthorized devices from disrupting the time synchronization process.

By leveraging UDP as its transport protocol and incorporating security and authentication mechanisms, NTP provides a reliable and secure method for time synchronization in distributed systems. Application developers can utilize NTP to ensure accurate and consistent timekeeping while mitigating the risks associated with UDP's characteristics.

PubNub provides developers with a scalable, secure, and feature-rich platform for building real-time applications. By leveraging our infrastructure, SDKs, and extensive library of tutorials, developers can focus on creating innovative and engaging user experiences. At the same time, PubNub takes care of the underlying complexities of real-time communication so you can focus on building sticky apps that engage users.

Check out our Github or sign up for a free trial you’ll get up to 200 MAUs or 1M monthly transactions for free.