.env ↔ JSON Converter
{
"NODE_ENV": "production",
"PORT": "3000",
"APP_NAME": "Rangdom Tools",
"GREETING": "Hello, $USER",
"DATABASE_URL": "postgres://localhost:5432/app",
"SECRET_KEY": "abc123"
}Turn a .env file into JSON
Paste a dotenv file — CI variables, a secret-manager export, a process.env fixture, or a container env block — and get a flat, pretty-printed JSON object of string values. Blank lines and full-line # comments are skipped, an optional leading export is stripped, and later duplicate keys override earlier ones. Single-quoted values stay literal while double-quoted values decode \n, \t, \r, \\, and \".
Quoting, comments, and limits
Keys must match [A-Za-z_][A-Za-z0-9_]*. In .env input, an inline # comment (a hash preceded by whitespace) is dropped from unquoted values. Out of scope and rejected with an inline error rather than guessed: dotted or nested keys, JSON arrays at the root, nested object or array values, multiline or heredoc values, and ${VAR} interpolation. Everything runs in your browser — nothing is uploaded.