JSON to ENV Converter
Convert JSON configuration into .env environment variables, instantly and in your browser.
Your configuration is processed locally in your browser and is not uploaded.
About this converter
Paste a JSON configuration object — from a Node.js config file, an API response, or anywhere else — and WebCodeIn converts every key into a properly-cased environment variable, flattening nested objects and arrays automatically.
How it works
- Paste your configuration, or drag & drop a file, into the input panel.
- Choose the input and output formats — WebCodeIn detects most formats automatically from the content.
- Your converted output appears instantly, computed entirely in your browser.
- Copy it to your clipboard or download it as a file. Nothing is uploaded at any point.
Supported formats
Input
- .env
- .properties (Spring Boot)
- YAML (incl. Spring Boot, Kubernetes, Docker Compose)
- JSON
- TOML
- INI
Output
- .env
- JSON
- YAML
- Docker Compose
- Kubernetes ConfigMap
- Kubernetes Secret
- Shell export
- TypeScript
- Spring Boot properties
Frequently asked questions
- How are nested JSON objects converted?
- Nested objects are flattened with underscores: {"database": {"host": "localhost"}} becomes DATABASE_HOST=localhost.
- What happens to JSON arrays?
- By default each array element becomes its own indexed variable (SERVERS_0, SERVERS_1, ...). You can switch to a comma-joined or JSON-array value in Options.
- Are numbers and booleans preserved?
- Yes — the ENV output represents every value as its string form (as real environment variables always are), while JSON/YAML output preserve the original type unless you enable Quote all values.
- Is my JSON uploaded anywhere?
- No. Conversion happens entirely client-side in your browser. Nothing you paste is sent to a server.
Privacy
Conversion runs entirely in your browser using JavaScript — your configuration is never transmitted to our servers just to be converted. We don’t log your input, store it in our database, send it to analytics, or include it in error reports. The only server-side calls this page makes are for anonymous, aggregate usage counters (which format pair was used) and never include your actual configuration or generated output.