Properties to ENV Converter
Convert Java .properties files (including Spring Boot application.properties) into .env environment variables.
Your configuration is processed locally in your browser and is not uploaded.
About this converter
Paste a Java .properties file — including a Spring Boot application.properties — and WebCodeIn converts its dotted keys into standard uppercase, underscore-separated environment variable names, ready to drop into a .env file, container, or CI/CD pipeline.
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 application.properties to .env conversion work?
- Dotted property keys are converted to uppercase, underscore-separated names: spring.datasource.url becomes SPRING_DATASOURCE_URL. Hyphens within a segment are split too, so my-app.database-url becomes MY_APP_DATABASE_URL.
- Does it handle Java unicode escapes and line continuations?
- Yes — \uXXXX unicode escapes, backslash line continuations, and : / = / whitespace key-value separators are all parsed per the standard .properties format.
- What about duplicate keys?
- If a key is defined more than once, the last value wins (matching standard .properties loading behavior), and WebCodeIn flags the duplicate so you can double check it's intentional.
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.