Data
WebTransport implementations
Libraries and server support you can use to speak WebTransport, with facts read from each project and a link to the source.
Implementations
9 entries, listed in no particular order. A status badge appears only where the project itself says the specification is a draft or the feature is experimental or in preview; otherwise it reads "not stated". Scroll the table sideways on narrow screens.
| Name | Language | Role | License | Latest release | Last commit | Repository | What the project says | Project's stated status |
|---|---|---|---|---|---|---|---|---|
| wtransport Pure-Rust, async. README examples cover both an endpoint server and an endpoint client. crates.io lists the license as MIT OR Apache-2.0. | Rust | client and server | Apache-2.0 | 0.7.2 | BiagioFesta/wtransport | The README says WebTransport is still a draft and not yet standardized, and that the library, while functional, is not considered completely production-ready. | states: draft spec | |
| web-transport (web-transport-quinn) A Rust WebTransport library for native and WASM targets. The repository is a workspace of several crates (web-transport-quinn, web-transport-wasm, web-transport-ffi, qmux, web-transport-proto), so the repository's latest release tag can belong to a different crate than web-transport-quinn. crates.io lists web-transport-quinn as MIT OR Apache-2.0. | Rust | client and server | Apache-2.0 | web-transport-v0.13.8 | moq-dev/web-transport | unknown | not stated | |
| yew-webtransport Gives Yew web apps access to the browser WebTransport API through wasm-bindgen. The repository's demo needs the web-sys unstable-APIs compiler flag. The README does not label the project experimental. | Rust (WebAssembly, Yew) | client | MIT | v0.22.0 | security-union/yew-webtransport | unknown | not stated | |
| webtransport-go Built on quic-go. The repository includes a runnable client and server example. pkg.go.dev shows a module version below v1. | Go | client and server | MIT | v0.13.0 | quic-go/webtransport-go | The README says the module currently implements draft-16 of the WebTransport specification, so it tracks a draft rather than a published standard. | states: draft spec | |
| aioquic A QUIC and HTTP/3 library. WebTransport appears in its example HTTP/3 server (an echo service at /wt) and through the H3Connection enable_webtransport option. The example server's handshake uses a draft02 header value, so interoperability with current browsers is unverified. WebTransport client support was not verified. PyPI lists the license as BSD-3-Clause. | Python | server | BSD-3-Clause | 1.7.0 (tag, no release) | aiortc/aioquic | The examples README says WebTransport is enabled in the demo server because the specifications and implementation are not yet finalised. | states: draft spec | |
| @fails-components/webtransport Node.js package backed by a native QUIC library, plus browser-side polyfill code. The npm registry lists the package license as BSD-3-Clause; the README says the wider FAILS project is AGPL v3.0 with third-party code under its own licenses, so check the license before adopting. | JavaScript (Node.js) | client and server | unknown | v1.6.11 | fails-components/webtransport | The README says the package implements parts of the WebTransport specification but not all of it, and describes its HTTP/2 variant and some other features as experimental. | states: experimental | |
| QUICHE (Google) Source includes a WebTransport-over-HTTP/3 session class (web_transport_http3.h) that checks the draft version during negotiation. The GitHub repository is a mirror of the googlesource.com repository and publishes no releases or tags, so the release is unknown. Repository dates describe the whole library. | C++ | building blocks | BSD-3-Clause | unknown | google/quiche | The README calls the library a production-ready implementation of QUIC, HTTP/2 and HTTP/3. It makes no WebTransport-specific statement in the text we read, and embedders must supply platform APIs, so it is not a drop-in library. | not stated | |
| ASP.NET Core Kestrel Exposed through IHttpWebTransportFeature (IsWebTransportRequest, AcceptAsync); needs HTTP/3 and HTTPS. Server only; no Microsoft client library was verified. Part of ASP.NET Core, so there is no separate release or license to report here. | C# | server | unknown | unknown | unknown | unknown | The API reference says WebTransport is a preview feature and requires opting in to preview features; the original announcement called it experimental and based on a draft specification. | states: preview |
| Deno Built into the runtime as the standard WebTransport class. Server-side use is not verified here. Repository license and commit date describe the whole runtime, and its releases are not specific to WebTransport, so the release is shown as unknown. | TypeScript and JavaScript (runtime) | client | MIT | unknown | unknown | denoland/deno | The Deno 2.2 release post described WebTransport support as experimental and behind the --unstable-net flag. The current documentation is not consistent with that post, so today's gating is unverified. | states: experimental |
Data fetched 28 October 2026 from GitHub (api.github.com); checked 28 October 2026. License, release and commit values come from GitHub; for repositories without releases the newest tag is shown instead, and a cell reads unknown when neither exists. Caveats are paraphrased from each project's own documentation, linked in the table.
How to read this table
Dates and licenses describe the repository, not necessarily the WebTransport part of it: for projects where WebTransport is one feature (Deno, Google QUICHE, ASP.NET Core), a recent commit says nothing about WebTransport work. The list is not exhaustive and does not measure quality. Download this data as JSON.
Cite this page
- Title
- WebTransport implementations: libraries and servers
- Author
- WebTransport Day (organization)
- URL
- https://webtransport.day/implementations/
- Updated
WebTransport Day. "WebTransport implementations: libraries and servers." Last updated October 28, 2026. https://webtransport.day/implementations/