How are nested JSON values handled?

A .env file is flat key-value pairs, so nested objects and arrays cannot map directly. When converting JSON to .env, nested values are serialized back to compact JSON as the value of the key, which round-trips and is what most config loaders expect. When converting .env to JSON, every value is a string unless it is valid JSON, in which case it is parsed - matching how .env is actually consumed.

Does it handle quotes and comments?

Yes. Parsing a .env file, it ignores blank lines and # comments, strips a leading export, and removes surrounding single or double quotes from values. Generating a .env file, it quotes any value that contains spaces or special characters so it parses back correctly.

Is my config safe to paste here?

It runs entirely in your browser - nothing you paste is uploaded or logged. That said, real .env files and config JSON often contain live secrets, so prefer pasting redacted or sample values, and never commit either format to your repo. Keep secrets in an environment or a secret store.

Free tool · Runs in your browser · Nothing uploaded

JSON ↔ .env, instantly.

Convert a JSON config object into a .env file, or a .env file into JSON — handling quotes, comments, export prefixes, and nested values. Everything runs in your browser.

.env input

JSON output

The format your config keeps changing into

Config lives in a dozen shapes — a .env file in dev, a JSON blob in a secret manager, an object in code, a key-value list in a dashboard — and you're forever translating between them by hand, which is exactly where a typo silently breaks a deploy. This does the boring, error-prone part for you, both directions, so the values come across intact.

It's a small reminder of a bigger truth: configuration and secrets are infrastructure, and where they live, who can read them, and whether they've drifted matters as much as the code. Managing that cleanly across the backend you own — one source of truth, access you can prove — is part of what a control plane is for.

Related free tools

Production-ready checkerScore your deploy Deploy error decoderDecode any deploy error CORS config generatorFix CORS the right way DATABASE_URL builderBuild or decode a conn string

All free tools →

Config is infrastructure. Treat it that way.

Infraveil runs your backend on servers you own, with configuration and secrets managed and access audited — so the values your app depends on are one controlled, inspectable source, not scattered across files, dashboards, and chat.

See how it works

Get the backend-config playbook

Config, secrets, and environments done safely for a backend you run yourself. No spam.