MAC Address Generator
Generate MAC addresses that are correctly marked as locally administered.
JSON to ENV
Flatten a JSON config into .env lines with correct quoting and naming.
Quick Tool Overview
The JSON to ENV converter flattens a structured config into environment variables: nested keys joined with underscores and upper-cased, values quoted only where a shell needs it, and newlines escaped so each variable stays on one line.
- What it does
- Flattens JSON into .env lines
- You give it
- A JSON config object
- You get back
- One KEY=value per line, correctly quoted
- Best for
- Twelve-factor apps, Docker and CI secret stores
About the JSON to ENV
Environments are flat and strings-only, so moving a structured config into one means flattening it. Nested keys are joined with underscores and upper-cased, giving the DB_POOL_SIZE shape every twelve-factor application expects.
Quoting is applied only where it is needed — a value containing spaces, a hash, a quote, a dollar sign or a backtick — because unnecessary quotes are noise and some loaders treat them as part of the value. Arrays become comma-joined lists by default, or indexed keys if you prefer. Newlines inside a value are escaped so the file stays one variable per line, which is the only form most loaders parse correctly.
Key features of the JSON to ENV
Twelve-factor naming
Nested keys become DB_POOL_SIZE — upper-cased and underscore-joined, the shape every environment expects.
Quoting only where needed
A value with a space, hash, quote, dollar or backtick is quoted; the rest are left bare, since a few loaders include stray quotes in the value.
Two array styles
Comma-join a list into one variable, or write one indexed variable per item.
One line per variable
Embedded newlines are escaped rather than written raw, because that is the only form most loaders parse.
Optional prefix
Add an APP_ or SERVICE_ prefix to every key in one field, which is how most platforms namespace config.
How to use the JSON to ENV
-
1
Paste your JSON config
Nested objects and arrays are both handled.
-
2
Set the prefix and separator
Add a prefix such as APP, and choose the character that joins nested keys.
-
3
Choose how arrays are written
Comma-joined into one variable, or one indexed variable per item.
-
4
Copy the .env lines
Paste them into your .env file or a deployment secret store.
Frequently asked questions
Because quotes are only needed when a value contains whitespace or a character the shell would interpret. Quoting everything is noise, and a few loaders include the quotes in the value.
Keys are joined with an underscore and upper-cased, so { "db": { "pool": { "size": 10 } } } becomes DB_POOL_SIZE=10.
By default they become a comma-joined list in one variable, which is how most applications read a small set of values. Indexed mode writes TAGS_0, TAGS_1 instead.
Yes, with the ENV to JSON tool and its nesting option turned on. The pair round-trips for any config that does not rely on a key containing a literal underscore.
Reviews of the JSON to ENV
What people who use the JSON to ENV think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
- 5 0 reviews rated 5 stars
- 4 0 reviews rated 4 stars
- 3 0 reviews rated 3 stars
- 2 0 reviews rated 2 stars
- 1 0 reviews rated 1 star
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON to ENV. It takes half a minute and no account.
Write the first reviewMore developer tools
EditorConfig Generator
Make every editor agree on indentation, line endings and charset.
XPath Tester
Run XPath expressions against your own XML and see every node that matches.
HTML Formatter
Re-indent HTML without breaking whitespace-sensitive elements.
Query String to JSON
Turn a URL query string into structured JSON, including nested and repeated keys.
XML Validator
Check XML is well-formed and find the exact tag that breaks it.
Regex Cheatsheet
Every regex token, searchable, with an example of what it matches.
SQL Minifier
Collapse a SQL query to one line and strip its comments.