vercel storage connects and manages project storage resources
Introduced 2026-09-08 · score 0.96
HOW TO USE IT
When connecting, checking, updating, or disconnecting a project storage resource, run `vercel storage <subcommand> <store>` with its name or ID. For mutations, review the environment-variable change set; use `--dry-run` to stop before applying it, and run `disconnect` interactively to confirm.
vercel storage connect <store> [--auth oidc] [--add-rw-token]vercel storage status <store>vercel storage update <store> [--auth oidc] [--add-rw-token] [--dry-run]WHY THIS HELPS
Connect, inspect, update, or disconnect a supported storage resource for a project and manage its environment-variable changes.
REQUIREMENTS AND LIMITATIONS
- Version: 59.12.0
- <store> (required): Storage resource name or ID; shared across Vercel Blob, Marketplace resources, and other first-party stores.
- --auth oidc: OIDC is the default authentication path.
- --add-rw-token: Explicitly request static credentials.
- --dry-run: Print the environment-variable change set without applying it.
- The same resource identifier (store name or ID) is used for Vercel Blob, Marketplace resources, and other first-party stores.
- Static credentials require explicit `--add-rw-token`.
- `disconnect` removes environment variables from the project, has no `--yes`, and always requires interactive confirmation.
- Non-interactive contexts can only use `disconnect` with `--dry-run`.
FIRST-PARTY EVIDENCE
Check the installed version and the source before using it. Entry JSON