.env ↔ JSON Converter

Bridging .env files and JSON

A .env file is a flat list of KEY=value lines that tools load into environment variables. JSON is structured and typed. Converting between them is handy when you want to feed env values into a config system that reads JSON, or generate a .env from a settings object. The conversion is simple on the surface and full of small traps underneath.

Example

.env input:

# database
DB_HOST=localhost
DB_PORT=5432
DEBUG=true

JSON output:

{
  "DB_HOST": "localhost",
  "DB_PORT": "5432",
  "DEBUG": "true"
}

Everything is a string

The biggest gotcha: environment variables are always strings. Note DB_PORT comes out as "5432", not the number, and DEBUG is the string "true", not a boolean. That matches how the OS actually hands these to your process. If you want typed JSON, you have to coerce after converting, and decide which keys are numbers or booleans.

Quotes, comments, and flat keys

Comment lines starting with # are dropped. Values may be quoted to preserve spaces or special characters, and the quotes are usually stripped on conversion. Going from JSON back to .env only works cleanly for flat objects, a nested object has no natural .env representation and must be flattened with a key naming scheme you choose.

FAQ

How are nested JSON objects handled? They cannot map directly, since .env is flat. You either flatten keys like DB_HOST or JSON-encode the value into a single string.

Are secrets safe to paste? .env files routinely hold credentials, so avoid pasting production secrets into any external tool and prefer a placeholder sample.