Where is the Vercel tokens page? (And where env vars actually live.)
Account tokens vs project env vars vs domains — the three Vercel places people mash together, with the URLs I actually use and the env-var mistakes that burn an afternoon.
Short answer:
- Account tokens (CLI / API): vercel.com/account/tokens
- Project env vars: open the project → Settings → Environment Variables (there isn't one global "all envs" URL that works for every project)
- Domains: vercel.com/dashboard/domains
If you only remember one of those, make it the tokens page. Everything else is one project deep.
Why this page feels harder than it is
Vercel is actually pretty good at navigation. The problem is that "where do I put the secret" splits into three different places:
- Your account — personal access tokens for the CLI and REST API
- Your team — shared settings, members, billing
- Your project — env vars, domains, git, functions, logs
So when someone says "the Vercel keys page," they might mean any of those. And depending on which one you need, the UI path is completely different.
The links I actually use
Tokens — vercel.com/account/tokens
Create a token, scope it, paste it into CI or the CLI. If a deploy script fails with 401, start here before you rewrite half the pipeline.
Dashboard — vercel.com/dashboard
Project list. This is where you click into the thing that owns the env vars.
Domains — vercel.com/dashboard/domains
DNS records, apex vs www, the 2am "why is SSL pending" rabbit hole.
Integrations — vercel.com/integrations
Marketplace stuff: Neon, Upstash, Blob, etc. If a storage or database "connection" suddenly broke after a team change, check here.
Usage / billing-ish views live under the account and team menus depending on plan. I don't memorize those URLs. I open the dashboard and follow the breadcrumb. Life is short.
Env vars: the mental model that helps
Env vars are per project, and then per environment (Production / Preview / Development). That's why there's no single "here's every secret you own" page — Vercel is intentionally not a password manager.
When something works locally and fails in production, 80% of the time it's:
- variable set only for Development
- typo in the key name (
DATABASE_URLvsDATABASE_URI) - Preview deploy looking at the wrong git branch / wrong env
- you rotated a key in Neon/Stripe/OpenAI and forgot to paste the new one into Vercel
None of that is fixed by a better search box. It's fixed by opening the right project settings and reading carefully for thirty seconds.
A tiny workflow that saves me weekly
- Need a token? Tokens page.
- Need an env? Project → Settings → Environment Variables.
- Need DNS? Domains.
- Need "why did this deploy fail?" Logs on the deployment, not the project overview.
Or: ⌘K on devlinkspad, type vercel, and stop re-deriving the path from muscle memory that was wrong anyway.
Related deep links
If you're wiring a full stack, you'll also end up on:
Same problem, different product. Same solution: stop hunting, start jumping.
devlinkspad is a free command palette for dashboard deep links. Not affiliated with Vercel.
Press ⌘K. Every dashboard, one keystroke away.