Protocols
Saved & recent

WebTransport

Also called: WebTransport API, WebTransport over HTTP/3

WebTransport gives web applications access to streams and datagrams for communication with a server. The browser API and the protocols used on the wire are separate specifications. The HTTP/3 binding uses QUIC to provide reliable streams and datagrams that do not guarantee delivery, within an established WebTransport session.

For example, a browser game can send reliable inventory changes on a stream and disposable position updates as datagrams. As inspected in November 2026, the W3C API was a July 2026 Candidate Recommendation Snapshot, while the HTTP/3 binding was Internet-Draft revision 17. Those statuses describe evolving specifications, not a final RFC or universal browser support.

Read first
QUIC
Related
HTTP/3, QUIC, WebSocket, WebRTC data channel
Further reading
reliable streams unreliable datagrams browser JavaScript API W3C CR Snapshot · July 2026 WebTransport over HTTP/3 IETF Internet-Draft 17 · November 2026 QUIC connection browser–server transport server
WebTransport’s browser API exposes reliable streams and unreliable datagrams through a separate HTTP/3 wire binding over QUIC. Shown statuses are the inspected July 2026 W3C Candidate Recommendation Snapshot and November 2026 Internet-Draft revision 17, not final RFC or universal support claims.

View in the full Protocols collection