How are .env values converted to JSON?

Each KEY=VALUE pair becomes a string property in a JSON object. Comments and blank lines are ignored, export prefixes are removed, and quoted values are unescaped.

Why are all JSON values turned into strings?

Environment files only store text. Keeping every value as a string avoids surprising type changes when the file is read back by another tool.

Can nested JSON be converted to .env?

No. Environment files are flat, so nested objects and arrays are reported as errors. Flatten them into separate keys first.

Is my environment file uploaded?

No. Parsing and conversion happen entirely in your browser. Nothing is stored or sent to a server.

.env to JSON Converter

Convert environment files to JSON and back. Comments are ignored, quoted values are unescaped, and duplicate keys are reported. Everything stays in your browser.

.env input 0 characters

Supports comments, an export prefix, single or double quotes and inline comments.

JSON output

Conversion rules

Blank lines and lines starting with # are ignored.
A leading export is removed, so shell-ready files work unchanged.
Double-quoted values understand \n, \r, \t, \" and \\.
Unquoted values lose a trailing comment that starts with whitespace followed by #.
Duplicate keys are kept once with the last value, and the duplicate is reported.
Going back to .env, values containing spaces, quotes or # are double-quoted automatically.

Need to reshape the JSON? Use the JSON Formatter or convert YAML with the JSON ↔ YAML / CSV Converter.

Build custom software with us

From internal tools to full platforms — we deliver end to end.

Start a Project

Was this tool useful?

Runs in your browser — nothing is uploaded.

.env to JSON Converter

Conversion rules

Related tools

Build custom software with us