.env to PowerShell Environment Script Converter

A clean environment bootstrap is one of the quietest ways to standardize Windows development. The pattern is simple: a script that reads configuration and sets $env:KEY for every variable, then stops. But hand-writing that file from a .env invites the usual failure modes — a value containing an apostrophe breaks the quoting, a comment leaks into a command, or CRLF/UTF-8 mismatches make the file misbehave under git on Windows.

The .env to PowerShell Environment Script Converter produces the finished artifact. Every KEY=value becomes a correctly quoted $env:KEY = 'value' line, guarded by Set-StrictMode -Version Latest and a header comment. Options control comment retention, line endings (CRLF for Windows or LF), and a verbose footer that confirms each assignment. The result is a commit-ready bootstrap.ps1 that behaves identically on every machine.

Deterministic, reviewable, and entirely browser-side — your values never leave the page.

• Complete script: Set-StrictMode guard, header and summary footer built in.
• Safe quoting: single-quoted values with doubled embedded quotes.
• CRLF ready: choose CRLF for Windows or LF for cross-platform files.
• Comment control: keep or strip comments from the source .env.
• Verbose footer: optional per-variable confirmation output.
• Key validation: letters, digits, underscores; duplicates flagged.
• Copy or download: clipboard or a bootstrap.ps1 file in one click.
• Private: all conversion happens in your browser.

1. Paste your .env content into the input box, or load the sample.
2. Choose line endings — CRLF for Windows, LF for cross-platform.
3. Toggle comments and the verbose footer as you like.
4. Click Convert. The complete bootstrap script appears on the right.
5. Download bootstrap.ps1, then dot-source it: . .\bootstrap.ps1.

Example 1 — Team bootstrap. A Windows team commits the generated bootstrap.ps1; new developers dot-source it and get an identical environment in one command.

Example 2 — CI on Windows. A build pipeline runs the script at the start of a Windows runner job so node or dotnet steps see the full environment.

Example 3 — Cross-platform repo. A repo already ships an env.sh; the team generates the matching bootstrap.ps1 with LF endings so git diffs stay clean on Windows and Linux.

Example 4 — Service pre-start. An ops engineer dot-sources the script before launching a Windows service so it inherits the correct configuration.

Example 5 — Onboarding without docs. The verbose footer tells a new hire exactly which variables were set, replacing a manual wiki checklist.

• Commit-ready file: a full, guarded bootstrap, not a fragment.
• Identical everywhere: deterministic quoting across machines.
• Windows-native: CRLF endings and correct PS syntax.
• No interpolation: dollars and quotes stay literal.
• Reviewable: valid keys and duplicate detection.
• Private & free: browser-only, no account.