Simple definition
QUIC is a modern transport protocol built over UDP and designed to reduce latency while multiplexing multiple streams.
Technical definition
QUIC integrates TLS security into the transport protocol, uses connection IDs, and manages multiple independent streams inside one connection. HTTP/3 uses QUIC instead of TCP.
How it works / role
The client contacts the server over UDP, negotiates the secure connection, and then opens multiple logical streams. Packet loss on one stream does not impose the same cross-stream blocking behavior seen when multiplexing over a single TCP connection. Connection IDs also help with certain network-path changes.
What is it used for?
Reduce connection-establishment time and improve modern web application behavior on variable networks.
Practical example
A browser uses HTTP/3 over QUIC to load multiple website resources through a single secure UDP-based connection.
Common issues
- UDP is filtered or rate-limited by a firewall
- Network inspection device does not understand QUIC
- Fallback to HTTP/2 over TCP hides the issue
- MTU or poor network quality causes excessive loss
Key takeaway: QUIC is not simply “HTTP over UDP”: it provides secure transport functions itself and is the transport foundation for HTTP/3.