TodayTools

Compare protocols

QUIC vs TCP: why the web is moving to QUIC

Donate
What brings you here?

The difference at a glance

QUIC

QUIC transport protocol

Best for: The web on phones and Wi-Fi

Connects and locks in one round trip.
  1. Hello + keys, from You
  2. Reply, from Server
  3. Data, from You, locked

TCP

Transmission Control Protocol

Best for: SSH, databases and data centres

A handshake first, then a separate TLS setup before data.
  1. SYN, from You
  2. SYN-ACK, from Server
  3. TLS hello, from You
  4. TLS reply, from Server
  5. Data, from You, locked

The short answer

TCP and QUIC both deliver data reliably and in order. TCP is built into the operating system and needs a separate TLS handshake on top. QUIC runs over UDP with TLS 1.3 built in, so a secure connection opens in one round trip, streams do not block each other when a packet is lost, and the connection survives a change of network. HTTP/3 runs on QUIC.

Which one fits you?

Tick everything that is true for you.

What do you need?

Your pick shows here

Tick one or more lines and we weigh them for you.

QUIC and TCP side by side

QUIC vs TCP: differences row by row
What differsQUICTCP
Runs onUDPIP directly
EncryptionAlways, TLS 1.3 built inNone; TLS is added on top
Secure connection setup1 round trip, 0 when resuming2 round trips with TLS 1.3
StreamsMany, each recovers on its ownOne byte stream
Lost packet effectOnly its own stream waitsEverything behind it waits (head-of-line blocking)
Network changeSurvives, using connection IDsBreaks; the connection is tied to IPs and ports
Where it livesUsually in the app or libraryIn the operating system kernel
StandardRFC 9000 (2021)RFC 9293 (first RFC 793, 1981)

Watch each one work

Each page plays the real packets on a map, step by step, with every header explained.

Test yourself

Each line describes one of the two. Which one?

Question 1 of 8

Runs on

UDP

Questions people ask

Is QUIC faster than TCP?

QUIC opens secure connections sooner and copes better with loss, so pages often load faster on mobile and Wi-Fi. On a clean wired link, bulk speed is similar.

Why does QUIC use UDP?

Routers and firewalls only pass the protocols they know. UDP gets through almost everywhere, and QUIC builds its own reliability on top, so it could ship without changing every device on the internet.

Can firewalls see inside QUIC?

Much less than with TCP. Almost all of the QUIC header is encrypted, so middleboxes cannot read or change sequence numbers or acks.

Will QUIC replace TCP?

For web traffic, it is already common. TCP will stay for many other uses for a long time.

More comparisons

Donate