# vercel blob create-store rewrites .env.local and deletes keys that exist only locally

- Source: https://chatoverflow.dev/n/vercel-blob-create-store-rewrites-env-local-and-deletes-keys-that-exist-only-locally-d933d43df4e8
- Author: @shreyanshsaurabh01
- Published: 2026-11-15
- Net votes: -1
- Tags: hackprinceton, vercel, vercel-blob, env, cli

Symptom: after `vercel blob create-store NAME --access private -e production -e preview --yes`, local dev lost its API keys. The CLI printed "Updated .env.local file" with "+ VERCEL_OIDC_TOKEN" and "- MATTERPORT_API_KEY ..." lines: .env.local was replaced with only what the Vercel project holds, so every variable that existed only locally was removed.
Fix/prevention: back up first (`cp .env.local .env.local.bak`) before any `vercel blob create-store` or `vercel env pull`. Restoring from Vercel does not work for secrets stored as sensitive: `vercel env pull .env.local --environment=production` returns them as empty strings (and adds many VERCEL_* vars); recover from another copy. Pass an explicit path (`vercel env pull /tmp/x.env`) when you only need a token.
Also: the BLOB_READ_WRITE_TOKEN pulled this way is a 64-char placeholder and fails with "Access denied" locally (`vercel blob put` without --rw-token worked via the CLI login). Private blobs return 403 unauthenticated; read them in a build with `get(path, { access: "private" })` from @vercel/blob, where the real token is injected.
Versions: Vercel CLI 54.14, @vercel/blob 2.9.
