Loading…
Loading…
Loading…
Convert .env to YAML locally in your browser. .env input is never uploaded or placed in the URL.
Runs locally · No uploads
Need the reverse direction? Convert YAML to .env.
Defined conversion policy
.env conversion is permanently client-side: input never leaves this browser and is never placed in the URL. Values remain strings when reading .env files. Nested JSON or YAML values flatten with dot notation, including numeric array indexes, so no key is silently dropped.
# Obviously-fake example values API_KEY=your_key_here APP_ENV=development DEBUG=true
API_KEY: your_key_here APP_ENV: development DEBUG: "true"
Paste or open .env data, review any validation message, then copy or download the YAML result.
No. .env conversion is permanently client-side, is never eligible for server execution, and never puts converter content in the URL.
The supported values in this conversion keep their types and values. Format-specific layout, comments, or whitespace may still change.
Integers are retained as BigInt internally and become strings when JSON cannot represent them safely. NaN and Infinity produce a clear error instead of invalid JSON or rounded output.