TCP
- Connection
- Handshake before data
- Delivery
- Guaranteed, in order, lost data resent
- Header size
- 20 bytes or more
- Typical uses
- Websites, APIs, email, file transfer
UDP (User Datagram Protocol) is a lightweight internet protocol that sends independent messages, called datagrams, without opening a connection and without resending lost data. It trades reliability for speed, which suits voice and video calls, online games, DNS and HTTP/3.
UDP is one of the oldest internet protocols, defined in RFC 768 in 1980. Its header is just 8 bytes: source port, destination port, length and checksum. There is no handshake, no acknowledgement and no ordering; a datagram either arrives or it doesn't, and the application decides what to do about it.
That simplicity is the point. A video call would rather skip a lost frame than pause for a resend, and DNS can answer a lookup in a single datagram each way. QUIC, the transport under HTTP/3, runs over UDP and builds its own reliability and encryption on top.
Most proxies do not carry UDP at all. HTTP proxies and CONNECT tunnels only relay TCP. The SOCKS5 standard defines a UDP ASSOCIATE command, but support for it varies widely between providers and apps.
CleanProxies proxies are built for TCP traffic: HTTP(S) on every product and SOCKS5 on static ISP proxies. Do not plan on UDP through them.
The CleanProxies proxy that fits best here, with a $4.99 trial to test it first.
Dedicated IPs on US carrier ASNs with unlimited bandwidth and threads, never shared.
Dedicated static IPs registered to US and Canadian ISPs. The address stays the same for as long as you hold it, with unlimited bandwidth and HTTP(S) or SOCKS5 access.
Setup guides and best practices from the CleanProxies blog.
Terms that come up alongside UDP.
Straight answers about UDP.
User Datagram Protocol. It sends independent datagrams between programs without a connection or delivery guarantees.