WebTransport
WebTransport is a technique that allows a webpage in the browser to exchange data with a server on an ongoing basis – in both directions and with very low latency. It is regarded as the modern successor to older methods for live connections and is used mainly for games, video conferencing, and real-time applications.
When you visit a webpage, this usually follows a fixed pattern. Your browser sends a request, the server responds once, and that’s it. For many applications, that’s not enough. An online game or a live chat needs a line that stays open and over which both sides can send something at any time on their own initiative. This is exactly the kind of permanently open line that WebTransport provides. It is an interface, meaning a defined set of commands that a webpage can use to establish such connections.
What has bothered developers about live connections so far
For persistent connections in the browser, there have mainly been two tools so far. WebSockets keep a line open and guarantee that every message arrives, and in the correct order. That sounds good, but it comes at a price. If a single data packet gets lost along the way, the connection waits until it has been resent. Everything that follows piles up in the meantime. Experts call this head-of-line blocking, meaning a blockage caused by the item at the front of the queue.
For an online game, this behavior is harmful. If a player’s position gets lost, it’s already outdated after 200 milliseconds anyway. You want the new position, not to have the old one resent. The second tool, WebRTC, can do exactly that, but it is very complicated to set up. It was originally designed for video calling between two users, not for connecting to a server.
WebTransport closes this gap. It offers both: a reliable channel like WebSockets and a fast, unsecured channel for data where timeliness matters more than completeness. Developers therefore no longer have to choose between two imperfect solutions.
QUIC as the foundation
WebTransport is built on HTTP/3, the newest version of the protocol that browsers and servers use to communicate. Underneath lies QUIC, a transport method developed by Google. The crucial difference from older methods: QUIC can send multiple independent data streams over a single connection. If a packet is lost in one stream, the others continue running undisturbed.
A connection in WebTransport knows two types of data. Streams are ordered data flows in which nothing gets lost – suitable for chat messages or game states. Datagrams are single small packets without any guarantee. They arrive quickly or not at all, and the order is not guaranteed. For position data in a shooter game, that is exactly right.
Another advantage lies in connection setup. QUIC encrypts from the very start and needs less back-and-forth between browser and server for this. As a result, setup is noticeably faster. In addition, a QUIC connection survives the switch from WiFi to mobile network, because it is not tied to a fixed address. Incidentally, a common misconception is that WebTransport is simply a faster WebSocket. It is its own interface with its own way of programming.
Cloud gaming, conferencing, and stock market data
WebTransport is most visible where milliseconds count. Cloud gaming services stream images from the data center to your screen and must send your keystrokes back immediately. Video conferencing providers also use the technology to transmit audio and video with as little delay as possible. In the financial sector, trading platforms use it to continuously push price data into the browser.
WebTransport is supported by Chrome, Edge, and Firefox. Safari caught up later, which is why many providers additionally keep a WebSocket variant available. In tech news, the term usually appears in connection with HTTP/3, QUIC, or announcements from streaming and gaming platforms. For you as a user, the technology remains invisible – you only notice it in that an application in the browser responds more smoothly than before.