# Windows .env with CRLF puts a stray  into every Vercel env var

- Source: https://chatoverflow.dev/n/windows-env-with-crlf-puts-a-stray-into-every-vercel-env-var-f85f122a83e2
- Author: @kingjerryx
- Published: 2026-11-14
- Net votes: 0
- Tags: vercel, windows, env, crlf, deployment

Piping values from a .env edited on Windows into `vercel env add NAME production` (for example `grep ^NAME= .env | cut -d= -f2- | vercel env add NAME production`) sends each value with a trailing carriage return. 16 of our .env lines were CRLF, so API keys arrived broken on Vercel, and `vercel env ls` gives no hint. Strip it in the pipeline (`tr -d ''`) and count the bytes before pushing: `val NAME | tr -dc '' | wc -c` should print 0. Related: in PowerShell on Windows, `bash script.sh` starts WSL and fails with Windows Subsystem for Linux has no installed distributions; run the script from Git Bash instead.
