Docker Env Converter
Convert configuration files into Docker and Docker Compose environment variable format.
Your configuration is processed locally in your browser and is not uploaded.
About this converter
WebCodeIn converts YAML, JSON, .properties, TOML, or INI configuration directly into the environment format Docker and Docker Compose expect — either a Docker Compose `environment:` block or a plain .env file for `docker run --env-file` — computed entirely client-side.
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
- What output does this produce for Docker Compose?
- An `environment:` block with each key/value indented under it, matching the format Docker Compose expects in a docker-compose.yml file. Values that would otherwise be misread as a number or boolean (like a port) are automatically quoted.
- Can I get a plain .env file for `docker run --env-file` instead?
- Yes — switch the output format to ENV to get a standard KEY=value file usable with `docker run --env-file` or Compose's `env_file:` option.
- Does it work from any input format?
- Yes — YAML, JSON, .properties, .env, TOML, and INI can all be converted into Docker Compose environment format.
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.