Get started with Edge Functions

This feature is in BETA.

The Edge Functions beta is enabled by default for all accounts. To try the feature, add edge functions code to your site.

# Create an edge function

To create an edge function to deploy with your site, write a JavaScript or TypeScript file stored in your edge functions directory.

For example, create a function file at netlify/edge-functions/hello.js:

export default () => new Response("Hello world");

export const config = { path: "/test" };

The file includes two parts:

  • The default export contains the handler function that runs when you make requests to the edge function. It often contains logic to modify requests and responses.
  • The config export configures the file as an edge function and provides the path on which the edge function will be invoked.

In this example, requests to /test will trigger the edge function and it will respond with Hello world.

If you have advanced configurations to declare, such as multiple edge functions on a given path, you can configure your edge function paths separately using a Netlify configuration file instead of including a config export in the function file. Learn more about edge function declarations.

# Edge functions directory

The default edge functions directory netlify/edge-functions/ is relative to your site’s base directory.

Alternatively, you can specify a custom edge functions directory with the edge_functions key in netlify.toml. For example, to use the my-custom-directory directory, add the following to the build section in netlify.toml:

edge_functions = "my-custom-directory"

# Edge functions with .jsx or .tsx

You also have the option to use .jsx and .tsx files for your edge functions. This can be helpful if you want your function to handle server-side rendering (SSR) at the network edge.

For example, this .tsx file contains the code to stream React SSR at the edge without a meta-framework:

import React from "";
import { renderToReadableStream } from "";
import type { Config, Context } from "";

export default async function handler(req: Request, context: Context) {
  const stream = await renderToReadableStream(
        <h1>Hello {}</h1>

  return new Response(stream, {
    status: 200,
    headers: { "Content-Type": "text/html" },

export const config: Config = {
  path: "/hello",

Looking for type definitions?

For TypeScript, you can import the types for the Context and Config objects from The types for the Request and Response objects are in the global scope.

# Test locally

You can use Netlify CLI to test edge functions locally before deploying them to Netlify.

  1. Ensure you have the latest version of Netlify CLI installed:

    npm install netlify-cli -g
  2. Launch Netlify Dev to start a development environment that executes edge functions on local requests:

    netlify dev
  3. Visit localhost:8888/test to execute the hello edge function declared for the /test route.

Changes to edge functions are applied on new requests.

  1. Edit hello.js to change the Response:

    export default () => new Response("Updated hello!");
    export const config = { path: "/test" };
  2. Save your updated function file.

  3. Reload localhost:8888/test and note that the response has changed.

To debug edge functions locally, launch Netlify Dev with the edge-inspect or edge-inspect-brk flag. For details, visit the CLI docs.

By default, the geo location used is the location of your local environment. To override this to a default mock location of San Francisco, CA, USA, use the --geo=mock flag. To mock a specific country, use --geo=mock --country= with a two-letter country code. For more information about the --geo flag, visit the CLI docs.

# Deploy

Use continuous deployment or Netlify CLI manual deploys to deploy your edge functions.

Use CLI version 12.2.8 or later for manual deploys

Manual deploys of edge functions are supported with Netlify CLI version 12.2.8 or later. Deploys made with older CLI versions will result in deployment errors.

If a project has TypeScript and JavaScript edge functions with the same name, for example, my-function.ts and my-function.js, the TypeScript function is ignored while the JavaScript function is deployed.

# Invoke

Invoke the deployed production version of your hello edge function declared for the /test route by accessing

Deploys of edge functions are atomic. This means that when a new deploy includes changes to function logic or declarations, the behavior of edge functions in old deploys won’t be impacted. Updates to edge functions move to production only when you publish a new production deploy.

# Monitor

To access logs for your production edge functions:

  1. In the Netlify UI, visit your site’s Edge Functions tab.

To access logs for other versions of your edge functions:

  1. In the Netlify UI, go to your site’s Deploys tab.
  2. Find the deploy of interest.
  3. Follow the Edge Functions link in the deploy detail page header.

# Log contents

Netlify provides a log of any console statements output by your edge functions. The log for each console statement includes the name of the edge function that generated the output.

# Date filter

By default, the Edge Function log displays a live tail of the latest activity in Real-time. You can also filter to review data from a specific time period, including the Last hour, Last day, Last 7 days, or select Custom to input a specific date and time range.

# Text filter

To make debugging easier, you can filter the logs by edge function name or path. If desired, you can also use pattern matching as part of your query.

# Log retention

Logs are retained for at least 24 hours of edge function activity, even after a new edge function deployment. This log retention period increases to 7 days for certain pricing plans.

# Log Drains

This feature may not be available on all plans.

You can connect your edge function logs to third-party monitoring services for analysis using Netlify’s Log Drains feature. Check out our Log Drains doc for more information.