Step 1 / source
Choose the source
Drop one file here
Choose the flat json environment object you want to turn into portable env assignments.
Checking publication status...LOCAL CONFIG CONVERTER / JSON TO ENV
JSON to ENV
Write one flat JSON object as portable dotenv assignments with safe variable names and deterministic quoting.
Processed in this browserOne UTF-8 .json file up to 1 MB. The root must be a non-empty flat object of scalar values with valid environment variable names; output is limited to 20 MB.
JSON - flat environment object
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 .json file up to 1 MB. The root must be a non-empty flat object of scalar values with valid environment variable names; output is limited to 20 MB.
Plain-language method
How JSON to ENV works
Nirmion validates portable variable names, converts scalar values to text, writes null as an empty value, escapes double quotes, backslashes, newlines, tabs, carriage returns, and dollar signs, and rejects nested objects and arrays.
- 01Choose a valid source
Use keys such as API_URL or PORT. Every value must be a string, number, boolean, or null.
- 02Review the conversion choices
Auto leaves simple text unquoted; Double quotes every value. Alphabetical order creates stable deployment diffs.
- 03Inspect the separate result
The result ends in _nirmion_tools.env. It contains no export commands and performs no variable interpolation.
Useful when
Practical jobs this tool handles
- Prepare reviewed non-production dotenv fixtures.
- Move flat deployment settings from JSON.
- Generate deterministic environment templates.
Before converting
Check the source and destination rules
- Use valid portable variable names.
- Review null and secret values.
- Test parsing in the destination runtime.
Know the boundary
Know what the destination format cannot keep
Generated ENV files may contain secrets in plain text. Do not commit credentials, tokens, or private endpoints to source control.
Quick answers
Questions before you convert
The conversion contract is deliberately explicit.
Can nested JSON be flattened?
No. Silent flattening can produce colliding environment names.
What happens to null?
It becomes an empty assignment.
Are dollar signs expanded?
No. They are escaped inside generated double-quoted values.