ConfuserEx is still the best-known free .NET protector, and "is it still maintained?" is the question everyone asks before leaning on it. The honest answer has two halves: the original project is effectively dead, but "ConfuserEx" lives on through community forks — some of which do target modern .NET. Here is the real status, so you can decide with your eyes open.
The short answer
The original ConfuserEx has not had active development for years, and its best-known successor fork has itself gone quiet. What keeps the name alive is a scattering of community forks of varying activity — a few of which are still receiving commits and targeting recent .NET versions. So "ConfuserEx" in 2026 is not one maintained product; it is a family of forks, and which one you pick matters more than the name on it.
What actually happened to the project
ConfuserEx began as an open-source successor to Confuser, and for a while it was the default answer to "free .NET obfuscation with real protection." The original repository was archived long ago. A widely-used successor fork carried it forward and added broader .NET support, but its own activity has slowed to a near-stop in recent years. Development, where it continues, has moved into further forks maintained by different people — which is why searching turns up several similarly-named repositories rather than one obvious home.
Can it still protect modern .NET?
This is where the popular narrative overshoots. You will see competing vendors flatly state that ConfuserEx "doesn't support .NET 5/6/7/8" — and for the original and the best-known fork, the modern-.NET story really is shaky. But it is not the whole truth: there are actively-committed forks that target .NET 8 and later, update their underlying libraries, and build against current runtimes. Treat "ConfuserEx can't do modern .NET" as marketing shorthand, not a fact — the accurate version is "the mainstream ConfuserEx is stalled, but a maintained fork can still do it."
The real catch: you are choosing and trusting a fork
A maintained fork existing is not the same as a maintained product. When you adopt a community fork you are taking on some real, ongoing responsibilities that a commercial tool would carry for you:
- Fork selection and longevity. You have to evaluate which fork is live, read its recent commit history yourself, and accept that today's active maintainer may move on. There is no vendor on the hook for the next .NET release.
- Trust and provenance. You are running a community build over your own assemblies. Satisfy yourself about who maintains it and what it does before you wire it into a release pipeline.
- Licensing. Forks can carry different or added terms; confirm the licence of the specific one you use.
- No support. When an aggressive preset breaks your app, you are debugging it from GitHub issues, not a support contract.
If you use it, use it well
None of this means avoid ConfuserEx — it means use it deliberately. If it is the right tool for you:
- Pick a fork with recent, ongoing commits that explicitly targets your .NET version, and re-check it still builds on each runtime upgrade.
- Prefer moderate presets. The aggressive ones — heavy packing and anti-tamper — are the ones most likely to break your app at runtime and to trip antivirus false positives.
- Know that some stock ConfuserEx protections are well-understood by automated deobfuscators; see can obfuscated .NET code be reverse-engineered? for what that does and does not change.
- Test the obfuscated build hard before shipping — reflection and serialization are where it bites. The workflow in how to test your obfuscated build applies directly.
Where we fit, honestly
We are a smaller, different tool, and we will not pretend otherwise: a maintained ConfuserEx fork protects more deeply than our free tier, and it runs entirely on your machine, which we do not. What we offer instead is the thing forks cannot — a single, actively-maintained hosted service with zero setup, no fork to vet, and an HTTP API, with the deeper layers available on Pro. The full ConfuserEx comparison lays the two out side by side, including where ConfuserEx wins.
A reasonable path, if you are weighing them: start here for free to confirm your application survives renaming — that flushes out reflection and serialization problems in minutes — then move to a maintained ConfuserEx fork if you decide you need its depth and are happy to own the fork decision. The layer decision guide will tell you whether you actually need that depth in the first place.
ConfuserEx is not the only tool in this position. Several other once-popular protectors are now offline or dormant — see discontinued .NET obfuscators and what to use instead.