About WinPkg
Last updated
WinPkg helps you discover Windows apps, compare alternatives, and find install commands for winget, the Windows Package Manager. Start with a topic when you are exploring a use case, a comparison when you are choosing between tools, or an app page when you already know what you need.
Where the data comes from
Every package on WinPkg comes from microsoft/winget-pkgs, the community repository that the winget client reads. WinPkg re-reads the repository and rebuilds the site every 12 hours, so the catalog currently covers 15,000+ packages. Versions, publishers, licenses, installer types, and architectures shown on app pages are taken from each package's manifests as written by its contributors.
The searchable catalog includes every package. A smaller set of 100 app pages, plus the topic and comparison pages, carry additional editorial context and are the pages WinPkg submits to search engines.
What WinPkg does not do
- WinPkg does not host or modify installers. The commands it shows are plain winget commands; winget downloads installers from the URLs in the package manifests.
- WinPkg is not affiliated with or endorsed by Microsoft, and it does not review the software listed in the catalog. Check an app's publisher and license before installing it.
- WinPkg does not provide support for third-party apps. Contact the app's publisher for help with the app itself.
Reporting incorrect data
If a WinPkg page shows something wrong, email [email protected] with the page URL and what you expected to see. If the error is in the package manifest itself, it has to be fixed upstream in winget-pkgs; WinPkg picks up the change on the next sync. See the contact page for details.
Updates about the site are posted on X at @winpkgcom.
Catalog data
The winget catalog report summarizes the whole repository: package counts, installer formats, ARM64 coverage, and the most active publishers, recalculated on every sync.