TCP: definition, explanation, and why it matters

Definition

Transmission Control Protocol — the connection-oriented, reliable transport protocol that underpins most web and email traffic on the internet.

Plain-English explanation

TCP guarantees that bytes arrive in order, without duplicates, and without loss — at the cost of some latency and overhead. It handles retransmissions, ordering, and flow control transparently.

Almost everything in a browser (HTTPS, HTTP/2) runs over TCP. HTTP/3 is the first major exception, using UDP-based QUIC instead.

Real-world examples

• A web page load is dozens of TCP connections to fetch HTML, scripts, images, and APIs.
• An SSH session relies on TCP for ordered, reliable delivery of keystrokes and screen updates.

Why it matters

TCP's behavior — slow start, congestion control, retransmissions — explains why packet loss and high latency hurt throughput so much more than the raw lost bytes suggest.

Common misconceptions

• Myth: TCP is always reliable, so I don't have to worry about loss.
  Reality: TCP recovers lost packets, but at a heavy throughput cost. High-loss links deliver dramatically less than their bandwidth.

Frequently asked questions

What's the difference between TCP and UDP?

TCP is reliable, in-order, and slower to set up. UDP is fire-and-forget, lower latency, and used where missing data is preferable to delayed data.