.env to Shell Export Script Converter

A .env file is data, but shells execute code — and source .env blurs that line. It works until a value contains a space, a $, a quote or a newline, and then your script breaks, your secrets get mangled or your shell runs something it should not. The reliable pattern is to convert the file into a script of properly escaped export KEY=value lines that you source consciously.

The .env to Shell Export Converter produces exactly that. Every KEY is emitted as a valid shell assignment, every value is wrapped in single quotes with embedded quotes escaped the standard POSIX way, and options let you toggle the export keyword, add a shebang, include or strip comments, and choose verbose or silent output.

The result is deterministic and reviewable — you can eyeball the whole script before sourcing it — and because comments, blank lines and quoted .env values are all handled, the script behaves identically to the variables you defined.

• Safe quoting: single quotes wrap every value; embedded quotes are POSIX-escaped.
• export toggle: emit export KEY or bare KEY per preference.
• Shebang: optional #!/bin/sh header so the file runs directly.
• Verbose or silent: keep # comments or strip them for a minimal script.
• No expansion: dollar signs and backslashes stay literal — never evaluated.
• Special chars: spaces, ampersands, stars and newlines survive exactly.
• Duplicate detection: repeated keys are flagged with line numbers.
• Copy or download: clipboard or a .sh file ready to source.
• Private: all conversion happens in your browser.

1. Paste your .env content into the input box, or load the sample with tricky values.
2. Tune the options. Toggle export keyword, shebang, and comment handling.
3. Click Convert. The shell script appears on the right.
4. Review warnings such as duplicate keys above the output.
5. Copy or download the .sh file, then source it: source ./env.sh.

Example 1 — Local runner. A developer converts their .env into env.sh, sources it in their terminal, and every variable they set before is exported to their node or go processes.

Example 2 — Deployment job. An SRE generates an export script from the release .env and sources it before a service start command on a minimal image.

Example 3 — Cron wrapper. A cron job sources the generated script first so background tasks get the same environment as interactive shells.

Example 4 — Sensitive credentials. A security-minded engineer uses the silent output that strips comments, keeping secrets out of visible documentation while remaining fully functional.

Example 5 — Cross-machine bootstrap. A team ships the same generated env.sh to collaborators so all machines load identical environment values without relying on a dotfile runner.

• Safe to source: values are never evaluated as shell code.
• Exact values: spaces, dollars and quotes round-trip perfectly.
• Readable: deterministic, reviewable script output.
• Flexible: export toggle, shebang and verbosity controls.
• Reusable: works under bash, zsh and most POSIX shells.
• Private & free: browser-only conversion, no account.