JSON to .env Converter

What is a .env File?

// Generate .env lines from a JSON object in Node.js
const config = {
  DATABASE_URL: 'postgres://user:pass@localhost:5432/mydb',
  PORT: 8080,
  DEBUG: true,
  NOTE: 'value with spaces',
};

const needsQuotes = (s) => /[\s#"'\n]/.test(s);

const env = Object.entries(config)
  .map(([key, value]) => {
    if (typeof value === 'string') {
      return needsQuotes(value)
        ? `${key}=${JSON.stringify(value)}`
        : `${key}=${value}`;
    }
    return `${key}=${value ?? ''}`; // null -> empty value
  })
  .join('\n');

console.log(env);
// DATABASE_URL=postgres://user:pass@localhost:5432/mydb
// PORT=8080
// DEBUG=true
// NOTE="value with spaces"

Key Features

Examples

{
  "DATABASE_URL": "postgres://user:pass@localhost:5432/mydb",
  "PORT": 8080,
  "DEBUG": true,
  "LOG_LEVEL": "info",
  "API_KEY": "sk_live_abc123"
}

DATABASE_URL=postgres://user:pass@localhost:5432/mydb
PORT=8080
DEBUG=true
LOG_LEVEL=info
API_KEY=sk_live_abc123

{
  "GREETING": "Hello, World",
  "MOTD": "line one\nline two",
  "COLOR": "#ff0000",
  "NOTE": "value with # hash",
  "EMPTY": null
}

GREETING="Hello, World"
MOTD="line one\nline two"
COLOR="#ff0000"
NOTE="value with # hash"
EMPTY=

{
  "databaseUrl": "postgres://localhost/mydb",
  "poolSize": 10,
  "enable-signup": true
}

DATABASE_URL=postgres://localhost/mydb
POOL_SIZE=10
ENABLE_SIGNUP=true

{
  "APP_NAME": "my-app",
  "FEATURES": { "signup": true, "beta": false },
  "REGIONS": ["us-east-1", "eu-west-1"]
}

APP_NAME=my-app
FEATURES="{\"signup\":true,\"beta\":false}"
REGIONS="[\"us-east-1\",\"eu-west-1\"]"

How to Use

1. 1

   Paste Your JSON Object

   Enter or paste a flat JSON object into the input field above. You can also click 'Load example' to try a config object, values that need quoting, or a nested object.

2. 2

   See Live .env Output

   The .env file appears instantly in the output panel. Toggle 'Normalize keys' for UPPER_SNAKE_CASE names, or 'Add export prefix' if the file will be sourced in a shell.

3. 3

   Copy or Download

   Click Copy to grab the .env to your clipboard, or Download to save it as a .env file — ready to drop into your project and load with dotenv.

Common JSON Pitfalls

["a", "b", "c"]

{"ITEMS": "a,b,c"}

{'PORT': 8080,}

{"PORT": 8080}

{"DB": {"host": "localhost", "port": 5432}}

{"DB_HOST": "localhost", "DB_PORT": 5432}

{"2fa-enabled": true}

{"TWO_FA_ENABLED": true}

{"MSG": Hello World}

{"MSG": "Hello World"}

Common Use Cases

Generate .env from a Config Export

Take a JSON configuration export from an API, a settings dashboard, or a secrets manager and turn it into a ready-to-use .env file for local development or a container.

Scaffold .env Templates

Build a JSON object describing the variables a new service needs, convert it to a .env, and commit a .env.example so teammates know exactly which keys to fill in.

Bridge JSON-Configured Tools to dotenv

Some tools emit configuration as JSON while your runtime expects a .env. Convert the JSON output into dotenv format so both halves of the pipeline agree on the same variables.

Produce Sourceable Shell env Files

Enable the export prefix to generate a file you can source directly in a shell or CI step, turning a JSON config blob into exported environment variables in one paste.

Round-Trip Configuration

Pair this with the .env to JSON Converter to edit configuration as structured JSON and write it back to .env — the round-trip-safe quoting guarantees values survive both directions.

Normalize Mixed-Case Keys

Convert a JSON object with camelCase or kebab-case keys into a .env with consistent UPPER_SNAKE_CASE variable names using the Normalize keys option, matching environment-variable conventions.

Technical Details

Object-Only Input with Typed Serialization

Input is parsed with the browser's native JSON.parse() and must be a top-level object; arrays and scalars are rejected with a clear error. Each top-level property is serialized by type: numbers and booleans are written bare, null becomes an empty value (KEY=), and strings are written directly unless they contain a space, newline, # or quote, in which case they are double-quoted and escaped for round-trip safety.

Nested Values and Key Normalization

Nested objects and arrays are serialized with a compact JSON.stringify, double-quoted and escaped, with a warning naming the flattened keys. The optional Normalize keys step converts keys to UPPER_SNAKE_CASE, resolving most invalid names; when keys are kept verbatim, any key that does not match [A-Za-z_][A-Za-z0-9_]* triggers an invalid-name warning. An optional export prefix can be added to every line.

Browser-Based — No Upload, No Server

All processing happens entirely in your browser's JavaScript engine; no JSON data is transmitted over the network at any point. The serializer is written in-house with no external dependencies, since the Node dotenv library is not browser-safe. Inputs larger than 200KB switch from live mode to manual mode (an explicit Convert click) to keep the browser responsive.

Best Practices

Keep Keys Verbatim Unless You Need env Conventions

Leave Normalize keys off when the consuming app already expects the exact key names in your JSON, so nothing is renamed unexpectedly. Turn it on only when you specifically want the UPPER_SNAKE_CASE convention environment variables conventionally use.

Flatten Nesting Intentionally, Not Accidentally

A nested value becomes an opaque JSON string in the .env, which most apps cannot parse back automatically. When you see the flattening warning, prefer reshaping the JSON into flat, prefixed keys (DB_HOST, DB_PORT) before converting, or choose a structured format like YAML instead.

Trust the Auto-Quoting for Round-Trips

Let the tool decide when to quote — it double-quotes and escapes only the values that need it. This keeps the .env readable while guaranteeing values with spaces, newlines or # survive a round trip back through the .env to JSON Converter unchanged.

Generate Secrets Only in a Browser-Only Tool

The JSON you convert here is effectively a set of credentials. Only generate a .env in a tool that runs entirely in the browser; verify zero network requests in DevTools. This converter qualifies, unlike server-side or API-backed generators.

Validate the JSON Input First

If the JSON is hand-written or assembled by a script, validate it with the JSON Formatter first to catch trailing commas or unquoted keys, so you get a clean .env instead of a confusing parse error.

Frequently Asked Questions