# Edge Functions are now generally available

**Published:** December 15, 2022 | **Authors:** Edward Thomson, Nathan Rajlich, Sean Massa, Javi Velasco, Kiko Beats, Damien Simonin Feugas, Marc Greenstock, Angela Zhang

---

> **Note:** This changelog entry is historical. Edge Functions are deprecated for new projects. Use [Vercel Functions](https://vercel.com/docs/functions) with the Node.js runtime and [Fluid compute](https://vercel.com/docs/fluid-compute). Use [Routing Middleware](https://vercel.com/docs/routing-middleware) for request-time routing before a response completes.

During the private beta, we’ve made Edge Functions **faster**, more **flexible**, and **more compatible** with Node.js:

- Major infrastructure optimizations for improved performance
- Support for

`cache-control`

[standard](https://vercel.com/docs/headers)

for function responses

- Added ability to express

[region preference](https://vercel.com/blog/edge-functions-generally-available#regional-edge-functions)

- Added support for

[WebAssembly workloads](https://vercel.com/blog/edge-functions-generally-available#support-for-webassembly)

- [Increased function size limits](https://vercel.com/blog/edge-functions-generally-available#increased-workload-size-and-improved-infrastructure)

for Enterprise and Pro teams

We’re excited to announce that beginning today, Edge Functions are now generally available so you can start executing more efficiently with instant “cold starts” to your functions for a better end-user experience.

For current projects, see [Vercel Functions](https://vercel.com/docs/functions), [Fluid compute](https://vercel.com/docs/fluid-compute), and the [Edge Runtime reference](https://vercel.com/docs/functions/runtimes/edge).

---

📚 **More updates:** [View all changelog entries](/changelog/sitemap.md) | [Blog](/blog/sitemap.md)