Netlify Edge Functions are JavaScript or TypeScript functions that run on Deno at Netlify's network edge, in the location closest to each visitor, rather than in a single serverless region. They are the tool for work that has to happen before or around the response: redirects, auth checks, geolocation, personalisation, and streaming. In 2026 the more common question is not what they are, but how they differ from plain Netlify Functions, and which one your code belongs in. Here is the honest version.
What are Netlify Edge Functions?
Netlify Edge Functions are Deno-based functions that execute at the edge of Netlify's network, close to the user. Because they run on Deno, an open, web-standards runtime, you get APIs like fetch, Request, and Response rather than the full Node.js surface. They sit in front of your site and can read or rewrite a request before it reaches your pages, which makes them the right home for middleware-style work: redirects, A/B tests, locale routing, bot filtering, and auth gates.
Netlify Edge Functions vs Netlify Functions: what is the difference?
The short version: Netlify Functions are regional serverless functions on AWS Lambda, and Netlify Edge Functions run on Deno at the edge. The practical differences:
- Where they run: Functions run in one AWS region. Edge Functions run at the point of presence nearest the visitor.
- Runtime: Functions give you the Node.js environment and the npm ecosystem. Edge Functions give you Deno and web-standard APIs, so Node-only packages may not work.
- Timeouts: Functions are built for request and response work with a short execution window. Edge Functions are meant to be light and fast, running on every matching request.
- Free limits: the free tier includes 125,000 serverless function invocations and 1,000,000 edge function invocations a month, so edge work has far more headroom.
- Best use: reach for Functions when you need real packages, longer work, or a backend-style API. Reach for Edge Functions for redirects, personalisation, streaming, and anything that should happen close to the user.
Netlify documents the runtime and limits in its Edge Functions overview.
Is Netlify free, and are Edge Functions included?
Yes. Netlify's free Starter plan is genuinely free with no card required, and Edge Functions are included on every plan, the free one included. The Starter tier gives you 100 GB bandwidth, 300 build minutes, 125,000 serverless function calls, and 1,000,000 edge function calls a month, plus deploy previews, custom domains with SSL, and the global CDN. Paid plans start at the Pro tier, around 19 US dollars per member per month, and move to credit-based usage above the included limits.
When should you use Netlify Edge Functions?
Use Edge Functions when the work needs to happen close to the user or before the page renders:
- Use them for geolocation redirects, locale routing, A/B tests, auth and bot checks, request and response rewriting, and streaming responses.
- Use plain Netlify Functions instead for API endpoints, work that needs npm packages or Node built-ins, database calls, and anything longer-running.
- Keep them small. An Edge Function runs on every matching request, so heavy logic there is paid on every hit.
How do Netlify Edge Functions compare to Vercel and Cloudflare?
All three run code at the edge, but on different runtimes. Netlify Edge Functions use Deno. Vercel's Edge runtime uses V8 isolates and now runs on Vercel Functions after its 2025 change, which we cover in the Vercel Edge explainer. Cloudflare Workers also use V8 isolates and have the widest edge network. If you are weighing the platforms rather than the runtimes, our Netlify vs Vercel comparison and the broader cloud hosting breakdown go deeper. For the runtime layer specifically, see the edge compute directory.
FAQ
What is the difference between Netlify Functions and Edge Functions?
Netlify Functions are regional serverless functions on AWS Lambda, built for API and backend work with the Node.js runtime. Edge Functions run on Deno at the network edge, close to the user, and are built for redirects, personalisation, and streaming. Functions give you npm packages; Edge Functions give you speed and web-standard APIs.
Are Netlify Edge Functions free?
Yes. Edge Functions are included on every Netlify plan, including the free Starter tier, which covers 1,000,000 edge function invocations a month. That is far more headroom than the 125,000 serverless function invocations on the same free tier. Usage above the included limits moves to credit-based pricing on paid plans.
What runtime do Netlify Edge Functions use?
Netlify Edge Functions run on Deno, an open, web-standards runtime. You write JavaScript or TypeScript against APIs like fetch, Request, and Response, rather than the full Node.js surface. Packages that depend on Node built-ins may not run, so check compatibility before porting server code.
When should I use an Edge Function instead of a Function?
Use an Edge Function when the work should run close to the user or before the page renders: redirects, geolocation, locale routing, A/B tests, auth checks, and streaming. Use a regular Netlify Function for API endpoints, database work, and anything that needs npm packages or a longer execution window.
The short version: Netlify Functions are your regional serverless backend, Netlify Edge Functions are your fast, Deno-powered layer at the edge. Most sites end up using both, Functions for the API and Edge Functions for the redirects and personalisation in front of it. Pick by where the work needs to happen, not by which one sounds newer.