Turn a JSON or YAML config object into a valid .env file. Nested keys flattened automatically. 100% in your browser.
Share this tool
Found it useful? Help a fellow developer discover it.
Going the other way, reading a .env file as structured JSON or YAML?
Convert .env to JSON or YAML
Environment variables are flat strings. Configuration, as people actually write it, is nested. Every time you move config into a runtime that reads .env files, you hit that mismatch: a Docker Compose environment block, a Vercel or Netlify project, a Kubernetes secret, or a local dev setup that has to mirror what a JSON config service returns. Doing it by hand means inventing a naming scheme for nested keys and remembering which values need quoting. This converter flattens the structure using a double underscore between levels, which is the convention most config libraries already understand, and quotes only the values that would otherwise break parsing.
How keys and values are written
Before you commit the file
DB.HOST becomes DB__HOST. Confirm that matches what your config library expects..env holding real secrets belongs in .gitignore.Paste your JSON config object into the left panel. This page opens already set to output .env format, so dotenv lines appear on the right immediately with nested keys flattened. Copy them into your .env file or download the result.
Environment variables are flat, so nesting has to be encoded in the name. Each level is joined with a double underscore, so {"DB": {"HOST": "localhost"}} becomes DB__HOST=localhost. The double underscore is the separator .NET, Spring Boot and many Node config libraries already recognize and map back to nested config.
Yes. Use the format selector to switch the input between JSON and YAML. This is handy for pulling a values.yaml or a Compose fragment into a local .env without a second conversion step.
Only the ones that need it. A value containing spaces or characters that would otherwise break parsing is wrapped in double quotes. Plain numbers, booleans, and simple strings are written bare, which keeps the file readable and matches what people write by hand.
They are written without quotes, so 5432 stays 5432 and false stays false. Be aware that this is cosmetic: environment variables are strings at the operating system level, so your application will read the string "false", which is truthy in most languages. Parse these values explicitly rather than relying on the type surviving.
Yes. The conversion runs entirely in your browser using client-side JavaScript. Your config is never sent to a server, never logged, and never leaves your device. Config files are exactly the kind of data that should never be pasted into a tool that uploads it, which is why this one does not.
Open the .env to JSON and YAML converter, a separate page written around that direction, covering comments, export prefixes, quoting and how nested keys are rebuilt into structure.
Not if it contains real credentials. Add .env to .gitignore and commit a .env.example alongside it that lists the same keys with placeholder values, so anyone setting the project up knows which variables are required without gaining access to the secrets.
.env to JSON / YAML Converter
Read a .env file as JSON or YAML. Handles comments, quotes, export prefixes, and nested keys. Runs in your browser.
JSON to YAML Converter
Convert JSON to YAML instantly. Produces clean, indentation-based YAML for Kubernetes manifests, Docker Compose, and CI workflow files.
JSON Formatter & Validator
Format, beautify, validate, and minify JSON. Detects BigInt precision issues, duplicate keys, and JSONC comments.
JSON to TOML Converter
Convert JSON to TOML in your browser. Produces valid Cargo.toml, pyproject.toml, and Hugo config syntax with proper table nesting.