Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Add the key and value in your host’s deployment settings, choose the environment that should receive it, then deploy or redeploy as that platform requires. In your code, read it with process.env.MY_VARIABLE. There is no single dashboard path for every host, so this guide covers Vercel, Render and Railway, whose documentation describes this exact task.
The two-step model
Every host follows the same pattern:
- Configure the variable on the platform, scoped to the right environment (development, preview/staging, production).
- Read it in Node.js through
process.env.
const apiUrl = process.env.API_URL;
const dbUrl = process.env.DATABASE_URL;Vercel and Railway both document this process.env.NAME pattern (Vercel, Railway), and Render does the same for DATABASE_URL (Render).
Platform-specific steps
Vercel
In the project dashboard, open the environment-variable settings, add a name and value, choose which deployment environments receive it, and save. Vercel distinguishes Production, Preview, Custom and Development environments. Changed values apply only to new deployments, so redeploy; earlier deployments keep their old values. For local work, the Vercel CLI can pull development values into a local .env/.env.local file or inject them into a local command. See Managing environment variables and Deploying from the CLI.
Vercel’s documentation (page last updated September 17, 2026) lists a 64 KB maximum for environment variables on deployments using its Node.js runtime. That is a Vercel quota, not a Node.js limit (source).
#1 Best Overall
Render
In the Render Dashboard, select the service, open Environment, and add a key and value. Then pick a save behavior:
- Save, rebuild, and deploy: rebuilds with the new values.
- Save and deploy: deploys the existing build with them.
- Save only: the service uses the values only after a later deploy.
You can also declare variables in a Blueprint render.yaml and bulk-import valid .env syntax. In a Blueprint, use placeholders for secrets and fill in the real values in the dashboard so they never enter the repository. Details: Environment Variables and Secrets.
Rank #2
Railway
Open the service’s Variables tab and add variables one at a time, or paste .env contents into the Raw Editor. Edits are staged; you must review and deploy them. Railway says values are available to the service deployment’s build and to the running service. Locally, railway run npm run dev runs a command with the project’s variables. See Using Variables.
Differences that cause real bugs
| Question | Vercel | Render | Railway |
|---|---|---|---|
| Where configured | Project environment-variable settings | Service Environment tab or Blueprint | Service Variables tab or Raw Editor |
| After saving | Redeploy needed; new deployments only | You choose save only, deploy, or rebuild and deploy | Changes staged until reviewed and deployed |
| Build and runtime | Available in builds and function execution | Not stated in the sources reviewed; the rebuild option implies builds can use new values | Available to build and running service |
| Local commands | CLI pulls or injects development values | Not stated | railway run |
Gotchas
Values are always strings
Render states: “Environment variable values are always strings.” Convert explicitly. process.env.DEBUG === "false" is a string comparison, and the string "false" is truthy.
Rank #3
const port = Number(process.env.PORT ?? 3000);
const debug = process.env.DEBUG === "true";
if (!process.env.DATABASE_URL) throw new Error("DATABASE_URL is required");Validating at startup makes a missing variable fail the deploy loudly instead of at the first request.
Set it before the build needs it
If a build step consumes the variable, it must exist before that step runs. Adding it after a build, then not rebuilding, is a common reason a value seems ignored. On Render, “Save and deploy” reuses the existing build, so choose rebuild when the build reads the value.
Rank #4
Scope to the right environment
A value added for Production does not automatically exist in Preview or Development. Set each environment explicitly, ideally with different credentials for each.
Keep secrets out of git
Render warns: “Do not commit your .env file to source control!” Add it to .gitignore and keep deployed values in the host’s settings.
# .gitignore
.env
.env.localAs practical guidance rather than a vendor rule, avoid logging secret values in build output or error messages.
Browser exposure is framework-specific
A platform variable is not automatically sent to the browser. Frameworks have their own conventions for public variables, so check your framework’s official documentation before exposing anything to client code.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify after deploying
- Confirm a new deployment was created after the change; a running process does not pick up edited values.
- Check the variable name for exact spelling and case.
- Confirm the deployment’s environment (production versus preview) is the one you edited.
- Check startup logs for your validation errors, without printing the secret itself.
Platform interfaces, limits and deployment behavior change, so confirm details in the linked documentation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
