HTTP/2 Multiplex Streams Calculator

HTTP/2 Multiplexing & Stream Calculator

HTTP/2 runs many independent streams over one TCP connection, which clears up the head-of-line blocking that sat at the HTTP layer in HTTP/1.1 (where pipelining mostly fell out of use). Every stream carries one request/response pair as a run of binary DATA and HEADERS frames, tagged with an odd-numbered stream ID. A peer announces how many streams it will take through the SETTINGS_MAX_CONCURRENT_STREAMS parameter. RFC 7540 asks for at least 100, and most servers (NGINX, Apache, h2o) ship with a default of 100.

Headers get compressed too, with HPACK (RFC 7541), a stateful scheme built on Huffman coding plus a dynamic table. On repeated headers like user-agent and cookie it usually shaves off 80–90% of the size. Server push arrived as a way to send resources ahead of a request, but Chrome dropped it in 2022 once it became clear the cache-hit payoff was small. The protocol landed as RFC 7540 (May 2015), and every major browser and CDN supports it.

Applications

Reach for this calculator when you need to size connection pools, set max_concurrent_streams on a reverse proxy, work out frame throughput per MTU, or figure out how many parallel sub-requests one h2 connection can handle before it saturates the TCP window. You'll hit these cases with REST API gateways, gRPC servers (which require HTTP/2), SPA asset delivery, and microservice meshes.

FAQ

Does HTTP/2 fully eliminate head-of-line blocking? No, it only handles it at the HTTP layer. Drop a single TCP segment and every stream on that connection stalls, because TCP hands bytes over in order. That's the reason HTTP/3 switched to QUIC over UDP.

Why is the default 100 streams and not unlimited? Every open stream costs memory for HPACK tables, flow-control counters, and priority state. Capping it at 100 keeps a reasonable amount of concurrency while holding back DoS attempts. Without that limit an attacker could open thousands of streams and burn through server memory (CVE-2023-44487 "Rapid Reset").

Should I still use HTTP/2 in 2026? Yes, wherever HTTP/3 isn't an option. For browser traffic, lean on h3 with an h2 fallback advertised through Alt-Svc. For internal gRPC, h2 over TLS is still the standard.