Skip to content

WebTransport · HTTP/3 · QUIC

WebTransport tester and echo server status

Enter any WebTransport URL to connect from your browser, send a message on a stream or as a datagram, and see the reply. The public echo server that used to run on this domain is no longer running here, so use the buttons to fill in a documented public server instead.

Tool updated · Facts checked

Browser capabilities

Detected by checking which properties exist, not by guessing from the browser name. "Present" means the browser exposes it, not that it works with every server.

WebTransport features detected in this browser
FeatureResultCheck used

Opens one throwaway attempt to a loopback address (127.0.0.1) and closes it, to see which options the browser reads. Nothing leaves your machine.

Use https://host:port/path. The server must support WebTransport over HTTP/3.

Self-signed certificate (optional)

SHA-256 of the DER-encoded leaf certificate. Per the spec and MDN, the certificate must use ECDSA P-256 and be valid for less than two weeks. Leave empty to use normal certificate validation. Shared links never contain the hash value.

State: idle


Results

Measured from this browser to this server. One sample is one sample, not a benchmark.

Session ready
–
Stream echo (round trip)
–
Datagram echo (round trip)
–

Connection timeline

More about the tester: WebTransport tester page. History and alternatives: public echo servers.

The idea

What does an echo server prove?

If the same bytes come back, every hop in the path worked: DNS, UDP, QUIC, HTTP/3, the certificate and the origin check. That is why an echo server is the first thing to point a new client at.

An echo round trip A browser sends a message to a server on a stream (blue) or as a datagram (amber). The server sends the same bytes back, shown in teal-green, and the browser receives the echo. Browser Echo server send "hello" on a stream or send "hello" as a datagram ✓ echo received: "hello" DNS, UDP, QUIC, HTTP/3, certificate and origin all worked.
The idea behind an echo server: send a message, get the same bytes back. It proves the whole path works. Conceptual illustration, not a measurement.
Text version
  1. The browser sends "hello" to the server on a stream (blue) or as a datagram (amber).
  2. The echo server sends the same bytes back (teal-green).
  3. The browser shows the echo. If it arrives, DNS, UDP, QUIC, HTTP/3, the certificate and the origin check all worked.

The API in 15 lines

How do you talk to an echo server?

From a browser, you open a WebTransport session, then send bytes on a stream or as a datagram. An echo server returns them, which proves the whole path works: DNS, UDP, QUIC, HTTP/3, certificate and origin checks.

  • One QUIC connection carries many independent streams, so one stalled stream does not block the others
  • Datagrams give you unreliable, unordered delivery for latency-sensitive data
  • Servers must support HTTP/3, and a page must run in a secure context

New to the protocol? Start with what WebTransport is.

Example
// Example: echo one message over a bidirectional stream.
const transport = new WebTransport('https://example.com:4433/echo');
await transport.ready;

const stream = await transport.createBidirectionalStream();
const writer = stream.writable.getWriter();
await writer.write(new TextEncoder().encode('hello'));
await writer.close();

const reader = stream.readable.getReader();
const decoder = new TextDecoder();
for (;;) {
  const { value, done } = await reader.read();
  if (done) break;
  console.log('echo:', decoder.decode(value, { stream: true }));
}
transport.close();

Start here

What is a WebTransport echo server, and where do I find one now?

An echo server accepts a WebTransport session and returns the bytes you send on streams and datagrams. It lets you confirm that a client library, a browser, or a network path works before you build on it. The old public one is gone, so these are the replacements.

Running WebTransport on edge or serverless platforms? See WebTransport and serverless.

History

What did the old webtransport.day echo server do?

It was a free, community-run public echo server, announced in July 2022 on the Chromium web-transport-dev group. Developers pointed WebTransport clients at it to check that a browser, library or network worked without running a server of their own. Chrome's WebTransport documentation and a few project READMEs linked to it.

By mid-2025, users on the same group reported that it no longer resolved. We could not confirm the exact shutdown date. The full story, with sources, is on the echo server page.

Guides

Latest WebTransport guides

What else is here

An independent resource for realtime web developers

WebTransport Day is an independent resource for web developers building realtime apps: WebTransport and the web platform, plus hands-on coverage of the AI coding tools developers use to build them.

  • WebTransport: tester, echo servers, serverless and edge support.
  • Guides: sourced explanations and how-tos.
  • Tools: the tester and the server checklist.
  • AI coding: AI coding tools for web and realtime developers.

Frequently asked questions

Is the webtransport.day echo server still running?

No. The public WebTransport echo server that used to be served from this domain is no longer running here. This site is now an independent developer resource and is not affiliated with the original service.

What can I use instead of the old public echo server?

Use the browser tester on this site to test any WebTransport server you can reach, and see the echo server page for other public test servers and open-source servers you can run yourself.

Can I run a WebTransport echo server on Cloudflare Workers or another serverless platform?

We found no provider documentation describing a serverless function layer that can act as a WebTransport server. The serverless and edge page lists what each provider documents and the date it was checked.

Do I need an echo server to build with WebTransport?

No, but a server that returns what you send is the quickest way to confirm a client works. You can run one locally with a library such as the examples in the local testing guide.

Test a WebTransport server in your browser

Free, client-side, no account. Your messages go straight from your browser to the server you choose.

Type to search. Esc closes.