YAML to ENV Converter
Convert YAML 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 any YAML configuration file — a plain config, a Spring Boot application.yml, or a Kubernetes-shaped YAML document — and WebCodeIn converts it into standard .env-format environment variables. Nested maps are automatically flattened, arrays are handled with a configurable strategy, and value types (numbers, booleans, null) are preserved.
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 does YAML nesting become environment variables?
- Nested YAML keys are flattened and joined with underscores: database: host: localhost becomes DATABASE_HOST=localhost. Deeper nesting works the same way, e.g. database.credentials.username becomes DATABASE_CREDENTIALS_USERNAME.
- Can it convert YAML lists/arrays?
- Yes. By default, a list becomes indexed variables (SERVERS_0, SERVERS_1, ...). In Options you can switch to a comma-joined value or a single JSON-array value instead.
- Does it support Spring Boot's application.yml?
- Yes — application.yml files convert the same way as any nested YAML, including Spring Boot's relaxed-binding-style keys.
- Is this safe for YAML with secrets in it?
- The YAML is parsed and converted entirely in your browser — it's never uploaded. WebCodeIn also flags likely secret keys (passwords, API keys, tokens) and can mask their values before you copy or download the result.
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.