PowerShell to Bash Converter

No — it is a best-effort heuristic mapper, not a transpiler. It converts line by line using a defined rule table (Write-Host to echo, Get-ChildItem to ls, Select-String to grep, $env: to export, if conditions to [ ] tests, foreach to for loops, and so on). Every line is flagged MAPPED or UNMAPPED, and unmapped lines are emitted as comments so the script cannot run them blindly. Always review and test the output in a safe environment before running it.

Several PowerShell constructs have no bash equivalent and are flagged UNMAPPED: Get-WmiObject and Get-CimInstance (Windows-only), registry provider paths like HKLM:, .NET interop calls such as [System.IO.File]::ReadAllText(), try/catch/finally blocks, Where-Object and ForEach-Object script blocks, PowerShell classes and enums, param() blocks, here-strings, and Invoke-RestMethod (which parses JSON — use curl plus jq instead).

Simple variables keep their dollar sign: $name becomes $name. Inside double-quoted strings, "$name" becomes "${name}" so the name boundary is always safe. Environment variables map both ways: $env:PATH reads as $PATH, and $env:API_KEY = "x" becomes export API_KEY="x". Special values convert too: $null becomes "", $true/$false become true/false, $args becomes $@, and array literals @(1, 2) become bash arrays (1 2).

Test-Path becomes the matching test: -PathType Leaf to [ -f ], Container to [ -d ], plain to [ -e ]. Comparison operators map as -eq to =, -ne to !=, while -gt, -lt, -ge and -le stay the same for numeric tests. Comparisons against $null become [ -z "$var" ], -match becomes [[ "$s" =~ pattern ]], -like becomes [[ "$s" == glob ]], and -and/-or become && and || between bracket tests.

foreach ($f in *.log) becomes for f in *.log; do, foreach over an array becomes for x in "${arr[@]}"; do, and numeric ranges like 1..5 become brace expansion {1..5}. C-style for ($i = 0; $i -lt 5; $i++) becomes for (( i=0; i -lt 5; i++ )); do, while (...) becomes while [ ... ]; do, and switch ($x) becomes a case "$x" in ... esac block.

Each pipeline segment is converted independently and re-joined with the bash pipe: Select-String -Pattern becomes grep, Select-Object -First/-Last becomes head/tail -n, Sort-Object becomes sort, Measure-Object -Line becomes wc -l, and Get-Content becomes cat. A recursive Get-ChildItem piped into Select-String is merged into a single grep -r, and a trailing Out-File becomes a > or >> redirect.

Safety. A line like Get-WmiObject Win32_Process has no Linux equivalent, so emitting it as # [UNMAPPED] keeps the original text visible for your manual port while guaranteeing the generated script cannot execute something the converter did not understand. A skipped line would silently change what the script does.

No. The conversion runs entirely in JavaScript inside your browser — no line of your script is transmitted anywhere. You can disconnect from the network after the page loads and the converter keeps working.

No. This tool is strictly one-way: PowerShell in, bash out. The reverse direction is a separate tool with its own mapping rules written specifically for bash syntax constructs.