Skip to main content

Vercel Sync

Vercel Sync lets you push variables from your local .env file to a Vercel project, or pull the project's environment variables down to your local file — all without leaving VS Code.

Setup​

1. Create a Vercel Token​

  1. Go to vercel.com/account/tokens
  2. Click Create Token
  3. Give it a name (e.g. vscode-env-manager) and choose a scope
  4. Copy the token

2. Enter Token in VS Code​

When you run Vercel Sync for the first time, the extension prompts you for:

  • Vercel Token — stored securely in the OS keychain via VS Code SecretStorage
  • Project ID — found in your Vercel project Settings → General → Project ID

These are saved and reused for all future syncs.

Pulling from Vercel​

Run ENV Manager Pro: Vercel Sync → Pull. The extension:

  1. Fetches the list of env vars for your project via the Vercel REST API
  2. Decrypts each variable individually (Vercel encrypts values at rest)
  3. Merges them into your active .env file — new keys are added, existing keys are left unchanged unless you choose to overwrite

Pushing to Vercel​

Run ENV Manager Pro: Vercel Sync → Push. The extension:

  1. Reads all variables from your active .env file
  2. Lists the existing Vercel vars to get their IDs
  3. PATCHes existing variables (update in place)
  4. POSTs new variables that don't exist in Vercel yet

Environments​

When pushing, the extension targets the preview environment by default. The Vercel API supports development, preview, and production — you can edit the push target in the extension's source if needed.

Security​

The Vercel token is stored via vscode.SecretStorage — it is never written to your workspace files, never logged, and never sent anywhere except the Vercel API.

warning

Push operations modify your live Vercel project. Always verify the Project ID before pushing to avoid updating the wrong project.