Hi all,
following this thread: How do I get HTTP/3 enabled on my site?
Still no update for the “newer” HTTP3 (tls 1.3) support?
Even the cheapest hosting nowadays seems got the http3 protocol, which can improve performances, supporting multiplexing and removing /reducing handshake.
Will this be enabled also on Vercel?
EDIT: I’ve seen that TLS 1.3 is enabled, so why still no http3?
Even Vercel itself still loads on http2
Hi Den,
TLS 1.3 and HTTP/3 are related, but they are not the same thing.
TLS 1.3 means the HTTPS handshake can use the newer TLS version. HTTP/3 specifically means the site is being served over QUIC/UDP instead of HTTP/1.1 or HTTP/2 over TCP.
A quick way to test what your site is actually negotiating is:
curl -I --http2 https://yourdomain.com
curl -I --http3 https://yourdomain.com
or in Chrome DevTools:
Network tab → right click columns → enable Protocol
If you see h2, that is HTTP/2. If HTTP/3 is active, you’d usually see h3.
From the current Vercel docs I can find, Vercel explicitly documents TLS 1.2 / TLS 1.3 support, but I don’t see HTTP/3 listed as a supported CDN protocol yet:
So I would not assume HTTP/3 is available just because TLS 1.3 is enabled. This looks more like a platform feature request / roadmap question than something you can enable per project with next.config.js or DNS settings.
Hi @ryux1 , thanks fro the reply.
You hit the nail on the head.
As I mentioned in my post, even though the two things aren’t directly connected, I don’t understand the logic of supporting only TLS 1.3 and not HTTP/3. This is especially true when even the cheapest shared hosting providers ($10–$20/month) offer HTTP/3 by default.
Of course, there’s no personal setting for that, being a platform lack…
My post was just a rant, hoping that someone in Vercel reads it and acts to solve the gap 
Hi Den,
Yep, fair point. I mostly replied to clarify the TLS 1.3 vs HTTP/3 difference for anyone else reading the thread.
I agree there probably isn’t anything to configure at the project level right now. It would be nice to have HTTP/3 support on Vercel too, or at least a clear note in the docs about the current status.
Thanks for raising it.