What is the ZAP file format?
A .zap file is a Zero Administration Package descriptor used by Windows Group Policy Software Installation (GPSI) to deploy non-.msi applications across an Active Directory domain. The format was introduced with Windows 2000 Server and has remained unchanged since.
The file is an INI-style plain text file - typically under 2 KB - with two key sections. The mandatory [Application] section must contain at least FriendlyName= (the display name shown in Add/Remove Programs) and SetupCommand= (the path to the installer executable, such as setup.exe). An optional [Ext] section lists file-type associations that GPSI registers on behalf of the application.
A critical limitation is that GPSI can only *publish* - not *assign* - applications deployed via .zap files. Published apps appear in Add/Remove Programs for domain users to install voluntarily; unlike MSI-based deployment, ZAP-published applications cannot be automatically pushed to machines, offer no auto-repair capability, and have no advertised-feature behaviour.
.zap files must be stored on a network share accessible to domain-joined clients, and the SetupCommand= path must point to the actual installer. Any plain text editor such as Notepad or Notepad++ can create or modify them.
The format is now a legacy feature. Modern organizations use Microsoft Intune, Configuration Manager (SCCM), Chocolatey, or winget for software deployment instead.
Security & safety
RISK: LOWZAP files are plain text INI configuration files and cannot execute code by themselves. The risk lies in what SetupCommand= points to: if a ZAP file references a malicious setup.exe on a network share, deploying it via Group Policy would silently install malware across the domain. Treat ZAP files received from outside your organization with caution; always verify the SetupCommand path before deploying.
Format details
in a nutshell- Zero Administration for Windows (ZAW) initiative file - ZAP is part of Microsoft's broader Zero Administration for Windows initiative from the Windows 2000 era; the file format itself IS this ZAP file type.
- Zap (various apps) - Several unrelated applications (compression tools, game data files) have used a .zap extension; unrelated to Windows Group Policy.
Programs that open ZAP files
Windows3 apps
Microsoft Windows Server (Group Policy Management Console)
Paid In Group Policy Management, link a GPO to an OU; under Computer/User Config > Software Settings > Software Installation > right-click > New > Package, choose ZAP file to publish the app.
Any plain text editor (VS Code, Notepad++, etc.)
Free Create or edit the ZAP file in any text editor; the INI format requires no special tool. Technical details
deep spec| Format type | INI-style plain text software deployment descriptor |
| Encoding | ANSI / Windows-1252 or UTF-8 without BOM |
| Typical file size | Under 2 KB |
| Mandatory section | [Application] - must contain FriendlyName= and SetupCommand= keys |
| Optional section | [Ext] - lists file-type associations for GPSI to register on behalf of the application |
| Deployment mode | GPSI publish only; cannot be used to assign applications to computers |
| Auto-repair support | None - unlike MSI-based deployments, ZAP apps have no auto-repair or advertised features |
| Target environment | Windows domain-joined clients via Active Directory Group Policy |
| File storage requirement | Must reside on a network share accessible to domain clients; SetupCommand= path must reach the installer |
| Editor requirement | Any plain text editor (Notepad, Notepad++, VS Code) |
| Related formats | .ini (structural basis); .msi (the preferred GPSI native format) |
| Current status | Legacy - superseded by Intune, SCCM/ConfigMgr, Chocolatey, and winget for modern deployments |
| Released | 2000 (Windows 2000 Server / Active Directory Group Policy) |
| Latest version | Unchanged through Windows Server 2025 (legacy feature) |
| Specification | learn.microsoft.com |
ZAP conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about ZAP files.
