.env to JSON Converter

No. The conversion runs entirely in your browser, so the values in your .env file never leave your device or get sent to a server. Nothing is logged.

Lines whose trimmed text starts with # are treated as comments and dropped, and blank lines are ignored. Only KEY=value lines end up in the JSON output.

Yes. A leading 'export ' (as in export KEY=value) is recognised and removed, so a line like export TOKEN=abc123 produces the clean key TOKEN with value abc123.

The line is split on the first equals sign only, so everything after it is kept as the value. That means URL=postgres://a=b parses to the value postgres://a=b rather than being truncated.

A single pair of matching surrounding single or double quotes is stripped from each value. So NAME="My App" becomes My App, while inner quotes and characters are left untouched.

No. Dotenv values are always strings, so PORT=3000 becomes the string "3000" and DEBUG=true becomes "true". This matches how process.env behaves at runtime.

A non-comment line with no equals sign, or one with an empty key, is invalid, so the tool shows an inline error naming the offending line and produces no output until you fix it.

Yes. Switch the direction to 'JSON to .env' and the tool writes KEY=value lines. Any value containing a space, a #, a quote or edge whitespace is wrapped in double quotes with embedded quotes and backslashes escaped.

When the same key appears twice, the last value in the file wins, which mirrors how most dotenv loaders behave. The earlier assignment is silently overwritten in the JSON output.