TCP
Transmission Control ProtocolBest for: Files, web pages and email
- SYN, from You
- SYN-ACK, from Server
- ACK, from You
- Part 1, from You
- Part 2, from Youlost
- Part 2 again, from You
Compare protocols
Best for: Files, web pages and email
Best for: Calls, games, live video and DNS
TCP opens a connection first and makes sure every byte arrives, in order, resending anything lost. UDP just sends each packet and hopes for the best, with no handshake and no resends. TCP is for web pages, email and files, where every byte matters. UDP is for calls, games, live video and DNS, where speed matters more than a missing packet.
Tick everything that is true for you.
Your pick shows here
Tick one or more lines and we weigh them for you.
| What differs | TCP | UDP |
|---|---|---|
| Connection | Yes, a three-way handshake (SYN, SYN-ACK, ACK) first | No, the first packet carries data |
| Delivery | Guaranteed: lost segments are sent again | Not guaranteed: a lost datagram is gone |
| Order | Bytes arrive in the order they were sent | Datagrams may arrive out of order |
| Header size | 20 to 60 bytes | 8 bytes |
| Speed control | Flow and congestion control slow it down on a busy path | None built in; the app decides |
| Broadcast and multicast | No, one to one only | Yes |
| Typical uses | Web (HTTP/1.1, HTTP/2), email, SSH, file transfer | DNS, voice and video calls, online games, QUIC and HTTP/3 |
| Standard | RFC 9293 | RFC 768 |
Each page plays the real packets on a map, step by step, with every header explained.
Each line describes one of the two. Which one?
Question 1 of 8
Connection
Yes, a three-way handshake (SYN, SYN-ACK, ACK) first
UDP starts sending at once and never waits for lost packets, so it has less delay. On a clean network the raw speed is similar. TCP feels slower when packets are lost, because it holds later data until the missing piece is resent.
HTTPS with HTTP/1.1 or HTTP/2 uses TCP port 443. HTTP/3 uses QUIC, which runs on UDP port 443. Browsers try HTTP/3 when the server offers it and fall back to TCP.
Most DNS questions go over UDP port 53 because they are small. DNS switches to TCP for large answers and for zone transfers between servers.
A resent packet with an old position or old sound arrives too late to help. UDP lets the app skip it and play the next one, which keeps the call or game smooth.