# Edge Config is now Global Config By Steven Van · 2026-07-29 The rename ships a new @vercel/global-config SDK, a GLOBAL\_CONFIG environment variable, and higher store and write limits on every plan. [Vercel]() has renamed Edge Config to Global Config, a change it says better reflects its role as a globally replicated data store with ~1ms reads in every region for runtime configuration such as feature flags, redirects, and experimentation settings. The store itself is unchanged, and existing projects need no action: connected stores and the EDGE\_CONFIG environment variable keep working. - A new server-side SDK, **@vercel/global-config**, replaces **@vercel/edge-config** as a drop-in package. It reads GLOBAL\_CONFIG by default and falls back to EDGE\_CONFIG, so it works with stores connected before or after the rename. - Connecting a store to a project now creates a GLOBAL\_CONFIG environment variable instead of EDGE\_CONFIG. - Store size limits rise to **1 MB** on every plan, up from 8 KB on Hobby, 64 KB on Pro, and 512 KB on Enterprise. - Pro and Enterprise teams can now create unlimited stores, up from 3 and 10, with up to 100 writes per hour (about 2,400 per day), up from 480 per day. Pricing is unchanged. Teams still on the old SDK should upgrade before connecting a new store, since @vercel/edge-config only reads EDGE\_CONFIG by default. Full details are in the [migration guide](). [![]()]() ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() Sources [Original source]() [Read Edge Config is now Global Config on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-edge-config-is-now-global-config