Convert a .env file to JSON, YAML, or compose.
Paste a .env and get it as JSON, YAML, a docker-compose
environment block, or shell exports — and convert any of those back.
Duplicate keys and values that need quoting get flagged. Your secrets
never leave the browser.
FAQ
Are my secrets uploaded?+
No. Your .env is parsed and converted entirely in your browser — it is never sent to a server. We count anonymous, aggregate usage on our own server (a page view, that a conversion ran) — never your keys, your values, or your file.
What gets flagged as a warning?+
Duplicate keys (the last value wins), key names that aren't valid environment variable names, and unquoted values that contain spaces or a # (which a shell would treat as a comment). Warnings never block the conversion — they just point out the ambiguous lines.
Can it convert back to a .env?+
Yes. Pick JSON → .env and paste a flat JSON object of key/value pairs; you'll get a .env back, with values quoted where they need it. Nested objects or arrays are rejected — a .env file is flat key/value only.