DEVELOPER TOOL
ENV File
Converter
Output format
Result
{
"database_url": "postgres://user:pass@localhost:5432/app",
"db_password": "s3cret#1",
"api_key": "abc123",
"debug": true,
"port": 3000,
"greeting": "hello world",
"brand_colour": "#ff6600"
}How it works›
Paste your environment file and choose JSON or YAML. The conversion runs locally in this browser tab; your input is not sent to a server.
Environment files do not have one universal specification. Quoted values, inline comments, whitespace, and duplicate names can be handled differently by dotenv libraries and Docker Compose. Review flagged lines before moving the output into a different runtime.
Values are strings in an environment file. Optional type inference is a convenience for JSON and YAML and can change values such as version numbers, so leave it off when exact strings matter.
Frequently Asked Questions›
Are environment values always strings?
Yes. DEBUG=false is the five-character string “false”. Type inference is an optional conversion choice, not a rule from the .env format.
Why is a hash character flagged?
Some parsers treat an unquoted hash as the start of a comment and truncate the rest of the value. Quote values containing hashes, then verify the behavior in your target runtime.
What happens to duplicate names?
This converter uses the last value, matching common loader behavior, and reports the duplicate so it is visible.
Does this tool upload my file?
No. Parsing and conversion take place in your browser.
Related tools›
More developer tools will be added after this prototype is reviewed.