UDP: Connectionless Transport Explained

What UDP Is

UDP (User Datagram Protocol) is a much simpler transport protocol than TCP - it sends data without first establishing a connection, without guaranteeing delivery, and without guaranteeing the order data arrives in.

No Handshake, No Guarantees

TCP:  handshake -> reliable, ordered delivery -> connection close
UDP:  just send the datagram - no setup, no delivery guarantee, no ordering

UDP simply fires data off toward its destination. If a packet is lost along the way, UDP itself does nothing about it - there's no retransmission, no acknowledgment, and no built-in mechanism to detect the loss at all.

Why "Unreliable" Is Often a Feature, Not a Flaw

TCP's reliability comes at a cost: handshakes add delay, and retransmitting lost data means waiting. For some applications, an old, late-arriving piece of data is actually worse than simply dropping it and moving on - which is exactly the trade-off UDP is built for.

Where UDP Is the Right Choice

• Live video/voice calls - a momentarily glitchy frame is far better than the whole call freezing to wait for a retransmission.
• Online gaming - an outdated position update is worse than no update at all; the next one will arrive shortly regardless.
• DNS lookups - small, quick queries where the application itself can simply retry if no response arrives.

A Much Smaller Header

UDP's header carries only source port, destination port, length, and a checksum - a fraction of TCP's header complexity, since there's no sequence number, acknowledgment number, or window size to track. This simplicity is part of why UDP has lower overhead and lower latency than TCP.