netlify-edge-functions

Create a TypeScript or JavaScript file in netlify/edge-functions/ that exports a default handler receiving a Request and Context, plus a config export with a path pattern. The function runs on Netlify's Deno-based edge network close to users.

Use edge functions for low-latency work like geolocation, auth checks, redirects, and A/B testing. Use serverless functions for long-running operations up to 15 minutes, heavy Node.js dependencies, database-heavy work, or tasks needing over 512 MB memory.

A file in netlify/edge-functions/ with no path binding deploys but never runs, with no build error or warning. Confirm it declares a path inline via export const config or has a matching [[edge_functions]] entry in netlify.toml.

Cache headers on an edge function response have no effect unless the function opts in with cache: "manual" in its config. Without that flag the response is never cached regardless of headers set.

Functions declared in netlify.toml run first in file order, then inline-config functions run alphabetically by filename, and caching functions run last. Declare functions in netlify.toml in your desired order to guarantee deterministic execution.

Edge functions are limited to 50 ms CPU time per request, 512 MB memory per deployed set, a 40-second response header timeout, and 20 MB compressed code size. Workloads exceeding these belong in serverless functions.