Menu
Important
Stay updated on React2Shell

Getting started with Edge Config

Last updated September 24, 2025

Edge Config is a distributed key-value store that allows you to store and retrieve data at the network edge, close to your users. It is designed for high performance and low latency, making it ideal for use cases such as feature flags, A/B testing, and dynamic configuration.

This guide will help you will create an Edge Config called at the project-level, through the Vercel dashboard. A token and environment variable , that stores the connection string, will be automatically created for you. You'll update the store with a key-value data pair and read the value of from a local Next.js project.

  • Install the Edge Config SDK:
  • An existing project. This quickstart uses Next.js, but you can use any supported framework with Edge Config storage
  • Install or update to the latest version of Vercel CLI
  1. Navigate to the Project you'd like to add an Edge Config store to. Click on the Storage tab, then click the Create Database button. Select Edge Config and click Continue.

    Create a new store by typing under Edge Config in the dialog that opens, and click Create.

    The name can only contain alphanumeric letters, "_" and "-". It cannot exceed 32 characters.

  2. Once created, select to see a summary of what was created for you. Notice the following:

    • If you select Project, you'll see that your project was connected to the Edge Config by using an environment variable. If you go to your projects's Settings > Environment Variables, you'll see the newly created environment variable.
    • If you select Tokens, you'll see a read access token. This token, along with your EDGE CONFIG ID, is used to create a connection string. This connection string is saved as the value of your environment variable. This enables you to use the SDK in your project to read the store's contents.

    If you're creating a project at the account-level, we won't automatically create a token, connection string, and environment variable until a project has been connected.

  3. Under Items, add the following key-value pair and click Save Items:

    You can see more information about what can be stored in an Edge Config in the limits documentation.

  4. Once you've created the store, you need to set up your project to read the contents of the store. This is detailed under Learn how to use this in code in the dashboard, but is described in the following steps in more detail.

    On your local machine, connect your Vercel Project. If you haven't already, install the Edge Config SDK, as mentioned in prerequisites.

  5. Using Vercel CLI, pull the latest environment variables, specifically , so that it's available to your project locally:

  6. Create a Middleware for your project by creating a new file called at the root of the project and if using Next.js, add the following code:

    requires at least Next v13.1 or enabling in .

  7. Run your application locally and visit to see your greeting. The middleware intercepts requests to and responds with a greeting, read from your Edge Config store.

Your project is now ready to read more key-value data pairs from the Edge Config using the SDK or Vercel REST API.

Your Edge Config uses the public internet for reads when you develop locally. Therefore, you will see higher response times. However, when you deploy your application to Vercel, the reads are optimized to happen at ultra low latency without any network requests.

Now that you've created an Edge Config store and read from it, you can explore the following:


Was this helpful?

supported.