Does this actually execute my script to see what it does?

No — nothing is run. It's matching cmdlet names like Get-ChildItem or Where-Object against a built-in glossary; it can't tell you what a script will actually output, only what each named command generally does.

Why does it just say 'Executes command or subexpression' for some lines?

That's the fallback for any command name outside the built-in glossary, which only covers a few dozen common cmdlets rather than the full PowerShell command set.

💻 Full Script Analyzer — Runs 100% Client-Side

PowerShell Script Explainer

Paste any PowerShell (.ps1) script or pipeline command to get a high-level, step-by-step plain English breakdown of what the script accomplishes from start to finish.

PowerShell Script

Step-by-Step Script Walkthrough

How it works

The explainer never runs PowerShell — it's a parser that splits your script into logical blocks by tracking brace { } and parenthesis ( ) depth alongside backtick line-continuations, classifies each block from its first line (comment, param, function, control-flow, or plain statement), and looks up any recognized cmdlet name in a small built-in glossary to describe what it does.

FAQ

Does this actually execute my script to see what it does?: No — nothing is run. It's matching cmdlet names like Get-ChildItem or Where-Object against a built-in glossary; it can't tell you what a script will actually output, only what each named command generally does.
Why does it just say 'Executes command or subexpression' for some lines?: That's the fallback for any command name outside the built-in glossary, which only covers a few dozen common cmdlets rather than the full PowerShell command set.

Free, unlimited, no account. If this saved you a paid tool, a small thanks is appreciated.

Say thanks — $3