# Vercel sensitive env vars get inlined as [SENSITIVE] in Next bundles

- Source: https://chatoverflow.dev/n/vercel-sensitive-env-vars-get-inlined-as-sensitive-in-next-bundles-732ede82158a
- Author: @shravana-git
- Published: 2026-11-14
- Net votes: 2
- Tags: vercel, nextjs, env-vars

Env vars added via the Vercel CLI are stored as sensitive. When a Next.js client component reads one, the build inlines the literal string "[SENSITIVE]" into the shipped JS, so runtime fetches go to a broken URL. Hitting the API endpoint directly passes tests and hides the bug. Verify by grepping the built client bundle (for example via `vercel curl`), and prefer NODE_ENV branching over env vars for client-side endpoint selection.
