Boltdeployment

Environment Variables Not Loading - Undefined in Build

Resolve environment variable loading issues in Bolt deployments. Fix undefined variables in production.

1 min read Updated Applies to Bolt

What is going on

Environment variables are undefined in your deployed application even though they're set in the platform. API keys, database URLs, and other config values come back as undefined.

Variables work fine locally but disappear after deployment.

Error messages you might see

process.env.API_KEY is undefined
Fetch failed - API_URL is null
TypeError: Cannot read property 'split' of undefined

Common causes

  1. Using process.env.VAR instead of NEXT_PUBLIC_VAR for client-side access
  2. Environment variables set after build completes
  3. Wrong environment selected in deployment platform (staging vs production)
  4. Variable name mismatch between code and platform settings
  5. Quotes or special characters in env var value causing parsing issues

How to fix it

For client-side vars: prefix with NEXT_PUBLIC_ (e.g., NEXT_PUBLIC_API_URL)

For server-side only: use plain process.env.PRIVATE_VAR (won't leak to browser)

Set env vars BEFORE triggering redeploy in your platform

Test locally: create .env.local with same vars and run npm run build

Getting help takes about a minute

No hiring, no back and forth. A real person looks at your app.

  1. 1

    Describe it

    Tell us what you need in plain words. You don't have to be technical or have an account to start.

  2. 2

    Free 15-minute call

    A verified developer calls you. Many tasks are sorted right there, and it costs nothing.

  3. 3

    Pay after you approve

    If there is more to do, you get one fixed price up front. You pay only once you are happy.

Get help

Real people, reviewed by hand

Developers who do this every day

Every developer is approved by our team before they can take a task. Describe yours and the first one who is free picks it up.

Get help

Questions

What's the difference between .env and .env.local?

.env is version controlled, .env.local is git-ignored. Use .env.local for secrets locally

How do I set env vars in Vercel?

Settings > Environment Variables. Make sure you set them before deploying

Should secrets use NEXT_PUBLIC_?

NO! Use NEXT_PUBLIC_ only for public values. Secrets stay as plain process.env.VAR and are only available on server

Keep reading

Can't fix it yourself?
Real developers can help.

Get help