ConversionParses by dotenv rules: export prefixes, hash comments, quoted values (double quotes may span lines and carry escapes). Optional type inference and nesting restore.

.env text.env

Load some data

JSON sourceJSON

Load data and the result will appear here

Environment variables → JSON config

.env to JSON

KEY=VALUE → JSON · dotenv-rule parsing · type inference · nesting restore · runs locally

🔒Processed locally in your browser — never uploaded or stored

No upload, no storage

JSON is processed in memory and never sent to a server.

Share via URL fragment

Share links encode data in the # anchor — never sent to a server.

Remember last edit

Optionally keep your last input locally; clear it with one click.

Why use .env to JSON

Parses like dotenv does

export prefixes, comments, quoted values and escaped newlines behave exactly as your app would read them.

Nesting restored

Flat keys like DB_HOST can be rebuilt into db.host nesting, with numeric segments becoming arrays.

Type inference

Numbers, booleans and null can be recognized automatically; very long numbers stay strings to protect precision.

Bad lines pinpointed

Lines that are not KEY=VALUE or have unclosed quotes get a line number — no eyeballing required.

Local · no upload

Environment variables and secrets stay in your browser; nothing is uploaded or stored.