Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
You have a .ps1 file — a PowerShell script. If .bat files are DOS-era duct tape, PowerShell is the precision engineering that replaced it. PowerShell works with structured objects instead of plain text, can manage Windows systems, Azure cloud resources, Active Directory, and Exchange — essentially anything in Microsoft's ecosystem.
Microsoft released PowerShell in 2006, and it has evolved from a Windows-only tool into a cross-platform shell (PowerShell 7 runs on Linux and macOS too). The key insight is that PowerShell commands (cmdlets) pass .NET objects between them, not text strings. When you pipe `Get-Process | Where-Object { $_.CPU -gt 100 }`, you're filtering actual process objects, not parsing grep output. This makes complex automation dramatically more reliable.
PowerShell (pre-installed on Windows) runs .ps1 files. VS Code with the PowerShell extension is the recommended editor. By default, Windows blocks script execution (the ExecutionPolicy is set to Restricted). Run `Set-ExecutionPolicy RemoteSigned` in an admin PowerShell to allow local scripts. As with any script format, only run .ps1 files from trusted sources.