Dota 2 Mod Manager: facts and numbers

One page of everything you can check. The counts are read from the catalog and from GitHub when this page is built, so they do not drift between releases.

In one paragraph

Dota 2 Mod Manager is a free app for Windows and Linux that installs cosmetic mods for Dota 2 in one click. The mods come from the open D2PFX catalog: 1,181 of them across 41 categories, added to by the community. The source is GPL-3.0 and public, releases are built by GitHub Actions, no account is needed and nothing is collected. Version 2.6.9, 44 releases, 72,472 installer downloads.

Numbers

Version 2.6.9
Platform Windows 10 and 11, Linux
Price Free, with nothing paid inside it
License GPL-3.0
Mods in the catalog 1,181
Catalog categories 41
Releases 44
Installer downloads 72,472
Interface languages English and Russian
Account Not required
Telemetry None
Updates The app updates itself

What it does

Installs and removes in one click

It downloads the mod, finds a free pak slot, writes it into the game folder and cleans up when you delete it. You never rename a pakNN_dir.vpk by hand.

Switches a mod off without deleting it

The file is renamed, the library entry stays. One more switch turns every mod off at once, which is what you want before a ranked game or right after a patch.

Shows you which mod is winning

Two mods carrying the same file cannot both apply. The app says which one the game is loading, and you drag them into a different order to change the answer.

Unlocks cosmetics your account already owns

Weather, couriers, wards, loading screens, announcers, mega-kills. Read out of the game's own item table, so anything Valve adds appears without an app update.

Takes your own files, and packs a mod from a folder

Drag a .vpk in, or point it at a folder. Archives inside come in all at once; a folder of loose game files is packed into a VPK for you, so an author needs no separate packer. It also unpacks an installed mod back into a folder, which is where editing one starts.

Recognises mods you installed by hand

It fingerprints what is already in your game folder, tells you which catalog mod each file is, and takes it under management instead of ignoring it or overwriting it.

Combines mods into one pak, and splits them back

Useful when you are running out of slots, or when you want several mods to move together.

Saves setups and sends them as a link

Save what you have on as a preset, send one link, and the other side ends up with the same look. Presets also export to a file.

Survives Dota patches

A game update overwrites the files mods depend on. The app puts them back, warns you when something needs attention, and writes to the game folder as one transaction: if a step fails, everything goes back.

Installs the modding tools

The catalog's Tools section - the VPK tools, the compiler, the patcher - is downloaded and installed from inside the app.

Backs up fonts and cursors

Those two replace files rather than layering over them, so the originals are copied first and restored when you remove the mod.

Launches the game

From the same window, into the language folder the mods are actually in.

Where the mods come from

From D2PFX, the open catalog h6rd has been running with the community for over a year: 1,181 mods in 41 categories, with previews, tags, per-hero grouping and a wiki that teaches you to make your own. The app reads that catalog directly, so a mod added today shows up today, without an app update and without anyone shipping a new version. The manager is listed in the catalog's own Tools section. The full story of the catalog.

How it differs from the others

Open source, and buildable. GPL-3.0, every line readable, and the installer you download is built by a public GitHub Actions workflow you can open and read. The other managers in this space are closed binaries.
It tells you about conflicts. Nothing else here explains which of two mods the game is loading, or lets you change it.
Off is not delete. A mod you switch off stays in your library.
It reads a live catalog. New mods appear without an app update, because the catalog is not baked into the build.
It adopts what is already there. Mods installed by hand or by another tool are recognised rather than trampled.
No account, no telemetry, no ads. Signing in with Discord is optional and only puts your name on a setup you share.
It does not ask for your Steam login. Nothing that installs a file into a folder needs your account. Anything that asks for it is doing something else.
It runs next to Minify. Not an alternative to it: Minify compiles mods where this installs them from a catalog, and the app is built to share a game with it - it stays out of the pak slots Minify writes, never touches its files, and says which of the two the game is reading. The detail.

What it does not do

It does not change the game rules and gives you no advantage. The mods are what you see on your own screen; nobody else in the match sees them.
It does not touch your Steam account, and never asks for a password or a Steam Guard code.
It collects nothing. There is no telemetry and no analytics in the app.
It does not promise you will not be banned. These are client-side mods and you run them at your own risk, the same as any other Dota mod.
It is not affiliated with Valve. Valve has not endorsed it and takes no part in it.

What it writes into the game folder

A mod is a VPK archive placed in the language folder the game mounts, in a free pak slot. That is a mechanism the engine already has, and it edits none of the game's own files.

The free-cosmetics feature is the one exception, and it is optional and off until you turn it on. Unlocking cosmetics means overriding the item table, which the engine only reads through one path, so the app registers an extra content folder in gameinfo_branchspecific.gi and records the patched file in dota.signatures. Both are backed up before the first write and put back when you turn the feature off. Why that patch is needed.

Will you get banned

Nobody honest promises anything here. What can be said precisely: Valve has never published a rule that names cosmetic mods; VAC looks for code injected into the running game rather than files sitting in a folder; people have been installing these for over eight years. That is every argument there is, and none of them is a guarantee. The app never touches your account, and the risk is yours. The long answer.

How to check any of this

Nothing on this page needs taking on trust. Each line below is a link to the thing itself rather than a description of it.

The installer is built in public. Every release is produced by release.yml on a GitHub-hosted runner, from the commit the version tag points at. Nothing is uploaded from a desktop. Every run, with its log.
The tag and the code match. A release page names its tag; the tag names a commit; the run log for that tag shows the checkout. Three clicks, no account.
Checks run on every push. test.yml: a linter aimed at code that cannot run, then the full suite on Linux and on Windows, with a coverage floor that fails the run rather than warning about it.
The code is scanned. CodeQL on every push and weekly, with the security-and-quality rules; findings are public under the Security tab of the repository.
Dependencies are watched. Dependabot covers the app, this site, and the actions the workflows themselves call.
What it fetches while running is public files you can open in a browser: the catalog's own lists and the signatures over them, the fingerprint map this repository publishes, the mod you asked for, and the update check. Nothing about you goes the other way.