The documentation site is moved to
https://obfuscar.lextudio.com/. This site will no longer be updated.
What does Obfuscar do?
Basically, Obfuscar scrambles the metadata in a set of assemblies. It renames everything to the minimal set of names that can be used to identify them, given signatures and type information. Since these new names are shorter than the old ones, it also dramatically
shrinks executable size.
The following method is from the example included in the release:
public ExampleUI( )
ClassX cx = new ClassX( "Some Text" );
displayText.Text = cx.DisplayText;
The code can be decompiled (via ILSpy
this.displayText.Text = new ClassX("Some Text").get_DisplayText();
After obfuscation, the code can be decompiled (via ILSpy
this.a.Text = new A.A("Some Text").A();
It's a simple example, but it scales...For example, given a reasonably sized code base, one could easily run into a class named
(in the namespace
) with 7 methods, 4 properties, and 5 fields named
, with several more methods, properties, and fields named
To try it out, see
It makes debugging / reverse engineering very difficult, but wouldn't stop someone who really wants to reverse engineer it. It would at least slow them down, and would deter casual observers.
Deobfuscators such as de4dot
make it easy to reverse most protection a commercial obfuscator might set. But note that the names obfuscated by Obfuscar still remains useful, as what's lost cannot be restored.