Dotenv (.env) Parser & Converter

How lines are read

A # starts a comment at the start of a line, or after a space, so KEY=abc#1 keeps abc#1 while KEY=abc #note gives abc. Quotes around a value are removed, and \n becomes a line break only inside double quotes. A value cannot span several lines, and a later duplicate key overrides an earlier one. References such as ${HOME} are copied as written: Node's dotenv does not expand them either, while tools such as Docker Compose do. Every value is a string, so PORT=3000 becomes "3000".

Kubernetes and shell output

A ConfigMap is for settings, not passwords or API keys. For those, create a Secret, which kubectl create secret generic app-env --from-env-file=.env does directly; its values are only Base64-encoded, so restrict who can read it. The ConfigMap name must be lowercase letters, digits, -, and ..

In the shell script, each value is in single quotes, so the shell expands nothing when the file is sourced: a password such as pa$word or a value with backticks arrives unchanged. A single quote inside a value is written as '\'', which closes the quote, adds an escaped quote, and reopens it. Load the script with source or .; running it as a separate process sets the variables only in that process.

How to use it

1. Paste your .env file contents.
2. Select output format (JSON, export, or ConfigMap).
3. Copy the formatted config.

Privacy & limitations

Secrets and environment keys stay strictly in your browser.