.env to JSON Converter

Because that's what it actually is. A .env file has no type system — every value on the right of the = is plain text, so DEBUG=true and DEBUG=yes are equally just the three or four characters that follow the equals sign. This tool never guesses that a value "looks like" a boolean or a number and silently converts it; DEBUG=true becomes the JSON string "true", and PORT=8080 becomes the string "8080", not the number 8080. If your application needs real booleans or numbers, convert them explicitly in code after parsing — that's a decision this tool deliberately leaves to you instead of guessing.

Double-quoted values ( KEY="like this" ) get backslash-escapes unescaped — \n becomes an actual newline, \" becomes a literal quote, and \\ becomes a single backslash — matching the standard dotenv convention. Single-quoted values ( KEY='like this' ) and unquoted values are taken completely literally: no escape processing happens at all, so a backslash in KEY=C:\path stays exactly as two characters, a backslash and a "p". Only double quotes trigger unescaping.

.env files are flat by nature — every line is KEY=VALUE, with no way to represent structure. Rather than silently invent a flattening scheme you didn't ask for (like turning {"db": {"host": "x"}} into DB_HOST=x), this tool rejects the conversion and names the exact key holding the nested value, so you can flatten it yourself the way that makes sense for your project — or remove it.

No — and this matters more here than almost anywhere else on the site. .env files routinely hold database passwords, API keys, and tokens. Parsing in both directions happens entirely in your browser with plain JavaScript string processing; nothing you type or paste is ever sent to a server, saved, logged, or included in any analytics. Closing the tab clears everything.

A value is wrapped in double quotes only when it contains whitespace or one of the characters " ' # \ — anything that would otherwise make the line ambiguous to read back. Inside those quotes, a literal backslash or double quote is escaped so the result is valid to re-parse. Plain values like true, 8080, or localhost are written bare, since quoting them would add nothing but visual noise.

Yes. Blank lines and any line whose first non-whitespace character is # are skipped entirely when converting .env to JSON, matching how every real dotenv loader treats them. A line with no = sign at all is skipped too, rather than guessed at.