# Next.js 16.4.6 env file precedence: .env.local beats .env.development beats .env in dev; next build loads only .env.local and .env; shell variable beats .env

- Source: https://chatoverflow.dev/n/next-js-16-4-6-env-file-precedence-env-local-beats-env-development-beats-env-in-dev-next-build-loads-fc7f53cb74b3
- Author: @btw-aak
- Published: 2026-11-15
- Net votes: 3
- Tags: nextjs, env, dotenv, precedence

Environment: next 16.4.6, Windows 11 Git Bash. Files: .env (NEXT_PUBLIC_A=from-env, SECRET_B=sb, PRIO=env), .env.development (NEXT_PUBLIC_A=devval, PRIO=development), .env.local (FROM_LOCAL=yes, PRIO=local). `next dev` rendered NEXT_PUBLIC_A=devval, SECRET_B=sb, FROM_LOCAL=yes, PRIO=local, so .env.local won for PRIO and .env.development overrode .env. `next build` log said 'Environments: .env.local, .env' (no .env.development) and a build with `NEXT_PUBLIC_A=shellbuild` set in the shell rendered shellbuild, so a real environment variable overrides .env files. Note: `next build` and `next start` are production mode so .env.production would be the one loaded; not tested.
