.env to PowerShell Script Converter

On Windows, environment variables live in several worlds at once: the current process, the registry-backed user and machine stores, and the PowerShell provider. Hand-converting a .env into something that loads under PowerShell usually means writing $env:KEY = value lines by hand — and guessing how to quote a value that contains an apostrophe or a trailing backslash.

The .env to PowerShell Converter removes the guesswork. It parses your .env and emits ready-to-run PowerShell: $env:KEY = 'value', with every value single-quoted and embedded quotes doubled exactly the way the PowerShell parser wants. A style toggle switches to Set-Item Env:KEY provider syntax, or to [Environment]::SetEnvironmentVariable for persistent User or Machine scopes.

The output is deterministic, reviewable and safe to paste into a terminal or a .ps1 bootstrapping your service. Comments, blank lines and quoted .env values are handled, and nothing leaves your browser.

• PS-correct quoting: single quotes with doubled embedded quotes.
• Three styles: $env:KEY, Set-Item Env:KEY, and SetEnvironmentVariable.
• Persistent scopes: process defaults, or User/Machine via the registry API.
• No interpolation: dollar signs and backticks stay literal inside single quotes.
• Special chars: apostrophes, spaces, ampersands and slashes survive exactly.
• Comment control: keep or strip comments from the source .env.
• Duplicate detection: repeated keys are flagged with line numbers.
• Copy or download: clipboard or a .ps1 file ready to run.
• Private: all conversion happens in your browser.

1. Paste your .env content into the input box, or load the sample with tricky values.
2. Pick an assignment style — $env:KEY, Set-Item, or persistent scope.
3. Optionally keep comments or strip them from the output.
4. Click Convert. The PowerShell script appears on the right.
5. Review warnings such as duplicate keys above the output.
6. Copy or download the .ps1 file and dot-source or run it.

Example 1 — Dev machine bootstrap. A Windows developer converts their .env into a .ps1 and runs it before lunch; every variable lands in their current PowerShell session for the local dev tooling.

Example 2 — CI on Windows runners. A build engineer sources the generated script in an Azure DevOps or GitHub Actions Windows job so node or dotnet processes see identical configuration.

Example 3 — Service user profile. An admin persists variables for the service account with the User scope, so a background service keeps a stable environment across sessions.

Example 4 — Registry-backed legacy app. A team migrating a legacy Windows service converts DATABASE_URL and API keys to Machine scope via SetEnvironmentVariable for the service launch.

Example 5 — Onboarding. New hires run the same generated bootstrap.ps1 and are configured in seconds without a wiki of manual steps.

• Guaranteed quoting: PowerShell-safe escaping every time.
• Exact values: apostrophes and dollars round-trip correctly.
• Right scope: process/session or persistent User/Machine.
• Readable: deterministic, easy to review before running.
• No registry surprises: session mode never touches the registry.
• Private & free: browser-only conversion, no account.