A 2-in-1 JAVA decompiler based on JD-CORE v0 and v1 
Initially a duo of decompilers were supported (JD-Core v0 & v1), but now other decompilers are supported with the transformer-api project. JD-Core v0 and v1 are 2 different decompilers rather than 2 different versions of the same one. They use a different algorithm :
- JD-Core v0 uses byte code pattern matching like JAD, the 1st Java decompiler
- JD-Core v1 uses an analytical algorithm like Fernflower, the 1st analytical decompiler
This project is built on top of original JD-GUI written by Emmanuel Dupuy.
After opening a jar file, click 'Open Type' to decompile a class (tip: use $ to match the end of the class name)
Use the outline tree to select decompiled methods :
In the Help -> Preferences menu, use search source code on Maven Central if you want to show the original source code, if it's available :
Use the search button to do a search for methods, string constants,...
Use File -> Save All Sources to decompile all sources into a sources jar (choose a destination directory where you have rights)
- CTRL+F Find text
- CTRL+L Goto line
Right-click on a method of the outline tree and select 'Show Byte Code' in the context menu.
To get a visual of the control flow graph that is used by JD-Core v1 for each of the decompilation steps, select one of the menus 'Show Control Flow Graph ...'. The graph is built by plantuml.
Sometimes JD-Core v1 fails to decompile a method. In this case, method will be patched from JD-Core v0 if possible and the comment 'Patched from JD-Core v0' will appear :
A modified version of JarComp is used to compare the jars and netbeans diff module for class comparison (see https://github.com/nbauma109/netbeans-visual-diff-standalone).
Select the 1st file to compare and then another file chooser will appear to select the 2nd file to compare :
The differences in size and CRC checksums are shown :
Double-click on the row you want to compare :
Or alternatively, if the 2 jars are opened, you can open the type you want to compare :
If you select no, you will be asked select which file you want to open
The navigable links are shown as underlined portions of text. Single click navigates to definition (no CTRL click, no double click).
Choose another decompiler in the preferences window and the class will be decompiled with the newly selected decompiler as soon as you press OK.
Compiler reports errors and warnings. Choose whether you want to report them in the preferences page.
When this option is selected, the jars located in the same directory and the jmods (or rt.jar) of JAVA_HOME will be used by decompilers for better type resolution. Currently, the decompilers supporting this are CFR, JD-Core v1, Procyon. This option applies to the Eclipse AST parser too, to provide better hyperlinks. For optimal results, setup your JAVA_HOME to the same JDK that was used to build the jar you want to decompile (if any doubt, check the META-INF/MANIFEST.MF inside the jar). The running JRE of jd-gui-duo does not interfere. This option does not support jars in war.
This is a known option from the original JD-GUI that enables to align code for debugging if the debugging information is present in the class files. As of now, this is only supported by JD-Core v0 and v1. If the code is misaligned, the numbers will appear in red.
This option uses the same feature as Eclipse to cleanup unnecessary casts.
| Decompiler | Author | Link | License |
|---|---|---|---|
| CFR | Lee Benfield | https://github.com/leibnitz27/cfr | MIT |
| Procyon | Mike Strobel | https://github.com/mstrobel/procyon | Apache v2 |
| Fernflower | Jetbrains | https://github.com/JetBrains/intellij-community/tree/master/plugins/java-decompiler/engine | Apache v2 |
| Vineflower | Vineflower | https://github.com/Vineflower/vineflower | Apache v2 |
| JADX | Skylot | https://github.com/skylot/jadx | Apache v2 |
| JD-GUI | Emmanuel Dupuy | https://github.com/java-decompiler/jd-gui | GPL v3 |