.env to JSON Converter
Convert dotenv variables and JSON in both directions with type inference and nested-key flattening
About this tool
.env to JSON Converter parses common dotenv assignments with optional export prefixes, blank lines, comments, single or double quotes, escaped newlines, and duplicate-key warnings. Type inference can recognize booleans, safe numbers, null, arrays, and JSON objects; disable it when every value must remain a string. The reverse mode accepts a JSON object, optionally flattens nested keys with underscores, preserves arrays and remaining objects as compact JSON, and quotes values when dotenv syntax requires it. Duplicate keys use the final value and are reported. Because dotenv interpolation and shell execution differ across libraries, the tool does not expand variables, execute commands, read local environment variables, or guarantee compatibility with every framework-specific extension. Processing stays in the browser.
Scenario Recipes
Review environment changes without exposing a secret file
Goal: Turn a dotenv sample into structured data for a local configuration review
- Remove production secrets or replace them with obvious placeholders before sharing the screen.
- Convert the dotenv text with type inference enabled and review duplicate-key warnings.
- Check inferred arrays, booleans, and numbers, then copy only the reviewed JSON fields needed by the next workflow.
Result: A structured local configuration snapshot with ambiguous types and duplicate assignments made visible.
Frequently Asked Questions
Are comments and export prefixes supported?
Yes. Blank lines and full-line comments are ignored, export prefixes are accepted, and unquoted trailing comments are removed.
How are quoted multiline values handled?
Double-quoted values decode common newline, tab, quote, and backslash escapes; a quoted value may also continue across input lines.
Will numbers and booleans remain strings?
Type inference is optional. Turn it off when values such as ports, flags, or numeric-looking identifiers must stay strings.
How are nested JSON objects converted to .env?
With flattening enabled, nested keys become uppercase underscore paths. Arrays and other object values are serialized as compact JSON.
Does it expand $VARIABLE references?
No. Expansion rules vary by dotenv implementation, so references are preserved as text and no shell expressions are executed.
Are secrets uploaded?
No. Parsing, conversion, warnings, copying, and downloads run locally in the browser.
Keep browsing