The only online tool that decompiles two Dalvik executables to Java source and diffs the actual code. No installation required.
Drop old and new versions of your .dex file into the upload areas.
Both DEX files are decompiled to Java source code using JADX.
View a file-by-file diff of every changed class and method.
A DEX (Dalvik Executable) file is the compiled bytecode format used by the Android runtime. When you build an Android app, Java or Kotlin source code is compiled to Java bytecode and then converted to Dalvik bytecode stored in DEX files. Every APK contains at least one DEX file (classes.dex), and apps using multidex may contain several (classes2.dex, classes3.dex, etc.).
DEX files contain all of the application's compiled code: classes, methods, fields, and string constants. They can be decompiled back to readable Java source using tools like JADX.
DEX files contain the compiled Dalvik bytecode that runs on Android devices. Comparing DEX files at the source level reveals exactly what changed in the application logic between two versions.
This is particularly useful when you have raw DEX files extracted from an APK or obtained from a device, and want to compare them without dealing with the full APK structure. Use it for:
CLI tools like dex-diff and Jake Wharton's Diffuse can compare DEX files but require local installation and command-line expertise. No other online tool provides DEX-level source comparison. If you have complete APK files, consider using the APK diff tool which also handles resources and the AndroidManifest.
Upload the original DEX on the left and the modified DEX on the right. Both files are decompiled to Java source code using JADX, then a unified diff is generated showing every changed class and method.
A DEX (Dalvik Executable) file contains compiled bytecode for the Android runtime. It is the executable format inside APK files. Android apps may have one or more DEX files (classes.dex, classes2.dex, etc.) when using multidex.
DEX files are decompiled using JADX, which converts Dalvik bytecode back to Java source code.
Compare DEX files directly when you have raw DEX files extracted from an APK, dumped from a device, or produced by a build tool. If you have complete APK files, use the APK diff tool instead as it also handles resources and the manifest.
Yes. Upload individual DEX files (classes.dex, classes2.dex, etc.) separately to compare them. Each DEX file is decompiled independently.
Yes, completely free. No registration or installation required.
Yes. Uploaded files are stored temporarily for decompilation and comparison, then automatically deleted. Files are never shared with third parties.