# Edge Config is now Global Config

DevFeed: [Edge Config is now Global Config](<https://devfeed.tech/articles/edge-config-is-now-global-config-906.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/edge-config-is-now-global-config>)

Author: Luis Meyer

Published: 2026-07-29T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [migration](<https://devfeed.tech/topics/migration.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>)

Tags: [data](<https://devfeed.tech/tags/data.md>), [edge](<https://devfeed.tech/tags/edge.md>), [feature-flags](<https://devfeed.tech/tags/feature-flags.md>), [global](<https://devfeed.tech/tags/global.md>), [migration](<https://devfeed.tech/tags/migration.md>), [server](<https://devfeed.tech/tags/server.md>), [update](<https://devfeed.tech/tags/update.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel renamed Edge Config to Global Config and introduced a replacement server-side SDK and environment variable. The underlying store is unchanged, while limits have increased and existing projects remain compatible.

## Source excerpt

Edge Config is now Global Config. This rename better reflects that it is a globally replicated data store with ~1ms reads in every region, built for the configuration that applications read at runtime, such as feature flags, redirects, and experimentation settings. Global Config stores can now hold up to 1 MB on every plan, and Pro and Enterprise teams can create unlimited stores with more writes per day. The rename also ships with a new server-side SDK, @vercel/global-config, and a new environment variable. What changed Name: Global Config is the new name for Edge Config. The store itself is unchanged. Package: @vercel/global-config replaces @vercel/edge-config as a drop-in replacement. Environment variable: Connecting a Global Config store to a project creates a GLOBAL_CONFIG environment variable instead of EDGE_CONFIG. Limits: Raised on every plan. Pricing is unchanged. What you need to do Existing projects: no action required. Deployments, connected stores, and the EDGE_CONFIG environment variable continue to work. Upgrading proactively is safe. The new SDK reads GLOBAL_CONFIG by default and falls back to EDGE_CONFIG, so it works with stores connected before and after the rename. You can switch packages today without touching your stores. Creating stores and pushing new config values work without upgrading. Neither depends on which SDK version your project uses. Upgrade before connecting new stores to a project. Connecting a store now creates a GLOBAL_CONFIG environment variable, and the legacy SDK only reads EDGE_CONFIG by default. A project still on @vercel/edge-config cannot read a newly connected store. To upgrade, install the new package and update imports: New limits Limit Hobby Pro Enterprise Stores 1 (unchanged) Unlimited (was 3) Unlimited (was 10) Writes 250/month (unchanged) 100/hour (was 480/day) 100/hour (was 480/day) Store size 1 MB (was 8 KB) 1 MB (was 64 KB) 1 MB (was 512 KB) Pricing is unchanged at $3 per 1,000,000 reads and $1 per 100 writes. Se