Does vercel support websockets now that we have fluid compute?

https://vercel.com/docs/limits#websockets

I’m so confused.

https://vercel.com/guides/do-vercel-serverless-functions-support-websocket-connections This article doesn’t explicitly say whether websockets are actually supported or not.

https://vercel.com/blog/an-introduction-to-streaming-on-the-web#streaming-on-vercel This article says vercel supports web streams. It was written on Jun 22, 2023.

But then we have this comment:

https://community.vercel.com/t/websoket-connection-detail/756/2

But if you can’t keep a connection for too long and the whole point of streaming responses is to allow for responses that take too long, what’s even the point?

And then we have this:

https://community.vercel.com/t/can-sse-be-implemented-with-only-next-js-api-routes/11063/3

If server sent events are supported now thanks to fliud compute, my understanding is that websockets are too? But I don’t see that explicitly said anywhere. In fact, if anything, I see the opposite:

https://vercel.com/docs/limits#websockets

This article was last updated on October 22, 2025, and according to the https://vercel.com/docs/fluid-compute#enabling-fluid-compute article

“As of April 23, 2025, fluid compute is enabled by default for new projects“.

Maybe this info in the limits article is outdated? Or are websockets actually not yet supported?

WebSockets are still not supported on Vercel, even with Fluid Compute enabled. The key distinction is streaming responses (which work great with Fluid Compute) are not the same as WebSocket connections (which require persistent, bidirectional connections that serverless functions can’t maintain).

What Fluid Compute enables:

Longer execution times for functions
Better support for server-sent events and streaming responses
Improved performance for long-running operations

What it doesn’t change:

WebSocket connections are still not supported
The serverless architecture still doesn’t allow persistent connections

But you can still have realtime features with your Vercel project by using one of the external providers listed in that first guide you linked

https://vercel.com/guides/do-vercel-serverless-functions-support-websocket-connections

I hope that helps!

https://vercel.com/docs/limits#websockets

I’m so confused.

https://vercel.com/guides/do-vercel-serverless-functions-support-websocket-connections This article doesn’t explicitly say whether websockets are actually supported or not.

https://vercel.com/blog/an-introduction-to-streaming-on-the-web#streaming-on-vercel This article says vercel supports web streams. It was written on Jun 22, 2023.

But then we have this comment:

https://community.vercel.com/t/websoket-connection-detail/756/2

But if you can’t keep a connection for too long and the whole point of streaming responses is to allow for responses that take too long, what’s even the point?

And then we have this:

https://community.vercel.com/t/can-sse-be-implemented-with-only-next-js-api-routes/11063/3

https://vercel.com/docs/limits#websockets

This article was last updated on October 22, 2025, and according to the https://vercel.com/docs/fluid-compute#enabling-fluid-compute article

“As of April 23, 2025, fluid compute is enabled by default for new projects“.

Maybe this info in the limits article is outdated? Or are websockets actually not yet supported?

What Fluid Compute enables:

Longer execution times for functions
Better support for server-sent events and streaming responses
Improved performance for long-running operations

What it doesn’t change:

WebSocket connections are still not supported
The serverless architecture still doesn’t allow persistent connections

But you can still have realtime features with your Vercel project by using one of the external providers listed in that first guide you linked

https://vercel.com/guides/do-vercel-serverless-functions-support-websocket-connections

I hope that helps!