Step 1 / source
Choose the source
Drop one file here
Choose the dotenv assignments you want to turn into flat json object.
Checking publication status...LOCAL CONFIG CONVERTER / ENV TO JSON
ENV to JSON
Convert portable dotenv NAME=value assignments into a flat JSON object without running shell code or expanding variables.
Processed in this browserOne UTF-8 .env file up to 1 MB and 100,000 physical lines. Variable names and assignments must be unique; multiline shell syntax is rejected.
ENV - 1 MB
No file upload
This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
Original stays unchanged
The converter creates a separately named output. It never writes back into the source file.
Bounded work
One UTF-8 .env file up to 1 MB and 100,000 physical lines. Variable names and assignments must be unique; multiline shell syntax is rejected.
Plain-language method
How ENV to JSON works
The browser reads unique NAME=value lines, accepts an optional export prefix, decodes conservative single- and double-quoted values, ignores full-line comments, and never executes commands, substitutions, or variable expansion.
- 01Choose a valid source
Use portable variable names beginning with a letter or underscore. Keep each assignment on one physical line.
- 02Review the conversion choices
Indentation affects JSON whitespace only. A value such as 001 or false remains a string.
- 03Inspect the separate result
The result ends in _nirmion_tools.json and may contain secrets in readable text. Store and share it with the same care as the source ENV file.
Useful when
Practical jobs this tool handles
- Inspect non-production environment fixtures.
- Move approved settings into a JSON-based deployment system.
- Compare environment keys without shell execution.
Before converting
Check the source and destination rules
- Remove secrets that do not need conversion.
- Check escaped newlines and dollar signs.
- Protect the downloaded JSON from accidental sharing.
Know the boundary
Know what the destination format cannot keep
The output can expose credentials, tokens, and private endpoints as plain JSON. Nirmion processes locally, but browser downloads and backups still require secure handling.
Quick answers
Questions before you convert
The conversion contract is deliberately explicit.
Are $VARIABLE references expanded?
No. Expansion could depend on a shell and leak local state.
Are values typed?
No. Dotenv values remain JSON strings.
Can it execute export commands?
No. The optional export word is parsed only as assignment syntax.