Short answer
The official WinDirStat source code is at github.com/windirstat/windirstat, maintained by the WinDirStat team under the GPL-2.0 license. The repository holds the C++ program, the MSI installer definition, 25 translation files and the changelog, and its Releases page is where every official installer is published. It has about 4.2k stars on GitHub.
How do I use the WinDirStat GitHub repository?
- Open the repository. Go to github.com/windirstat/windirstat; the owner must be the windirstat organization.
- Read the README. It lists features, the official install routes, supported Windows versions and the malware warning.
- Get a release. Click Releases on the right and download from the release marked Latest.
- Report a problem. Use Issues, or Help > Report Bug/Feedback inside WinDirStat, which opens the new-issue page.
- Follow changes. Watch the repository for releases, or read CHANGELOG.md, which has one section per version.
Who maintains WinDirStat on GitHub?
The WinDirStat team maintains the repository and publishes the releases. The program's About box credits Bernhard Seifert, Oliver Schneider and Bryan Berns as its programmers and thanks Stefan Hundhammer, whose Linux tool KDirStat was the model. Contributors send fixes and translations through pull requests, and CONTRIBUTORS.md lists earlier contributors, testers and translators. At the last update the repository had 4.2k stars, 261 forks and 31 open issues; its latest push was on October 6, 2026.
Is WinDirStat really open source?
Yes. The application is distributed under the GNU General Public License version 2, and the README adds one condition worth knowing: you may not move it to a later GPL version. Parts of the code are also available under more lenient terms, and the logo and its derivatives use Creative Commons BY 3.0. In practice that means you can read every line, build it yourself, use it at home or at work without paying, and share modified versions under the same license. The license text is in LICENSE.md.
How are WinDirStat releases tagged on GitHub?
Stable releases use tags of the form release/v plus the version, and the newest is marked Latest; the current one is release/v2.9.0. Betas are published as pre-releases with a beta/v tag that includes the build date. Every release page lists its files with SHA-256 digests. The releases guide explains each file, and the safe download steps show how to check one.
Where do I report a WinDirStat bug?
Open an issue on the GitHub issue tracker; inside the program, Help > Report Bug/Feedback opens the same new-issue form. Include the version from Help > About, your Windows version and the steps that cause the problem. The project wiki, reachable from Help > Help, holds the online manual. Questions about this guide's wording go to our contact page, not to the WinDirStat team.
| Path | What it holds |
|---|---|
windirstat/ | The program's C++ source, views, dialogs and resources |
windirstat/res/langs/ | 25 translation files, one per language, such as lang_en.txt |
setup/msi/ | The WiX definition of the MSI installer and its options |
setup/chocolatey/, setup/store/ | Packaging for Chocolatey and the Microsoft Store |
tests/ | PowerShell test scripts for the built program |
CHANGELOG.md | Changes per version, each with its own anchor |
LICENSE.md | The GNU GPL version 2 |
windirstat.sln | Visual Studio solution; the README says Visual Studio 2022 or later builds it |
From the repository at the release/v2.9.0 tag.
Frequently asked questions
Is github.com/windirstat/windirstat the real WinDirStat repository?
Yes. It is the repository the WinDirStat README, windirstat.net and the program's own Help menu point to, and its Releases page is the source of the winget package's installers. Forks under other accounts are copies that the WinDirStat team does not publish from.
Can I build WinDirStat from source myself?
Yes. The README says it builds with Visual Studio 2022 or later from windirstat.sln. The license lets you build, change and share it under the same GPL-2.0 terms, but most people should use the official release files instead of their own build.