DEX / Smali Analyzer
Disassemble an APK's DEX into smali and decode its resources, with class/method counts and a downloadable smali tree.
Drop your file here
or click to choose from your device
About DEX / Smali Analyzer
Disassemble an APK's DEX into smali and decode its resources, with class/method counts and a downloadable smali tree.
DEX / Smali Analyzer is part of APKLint’s decompile & reverse engineering toolkit — Turn a built app back into readable code and resources. It’s free to use and needs no account.
Your privacy is the default: files you upload are processed on our servers over an encrypted connection and permanently deleted by a scheduled hourly cleanup after analysis finishes, and never shared.
What DEX / Smali Analyzer checks
- For an .apk: decodes to smali and resources with apktool
- For a raw .dex or .jar: analyzes with jadx (apktool is APK-only)
- Reports per-DEX class and method counts when DEX bytecode is present (APK, raw .dex, or a .jar that bundles .dex)
- Provides the decoded output as a download
Good to know: Accepts .apk, .dex, or .jar — not .aab. apktool smali output applies to .apk inputs; raw .dex/.jar are handled by jadx.
When to use DEX / Smali Analyzer
- Best for
- Working directly with bytecode containers: an .apk decoded to smali, or a raw .dex/.jar inspected on its own, with class and method counts.
- Not the right tool for
- Not for .aab inputs and not where you want fully readable Java (use the APK Decompiler for that).
- What you get back
- smali/disassembly plus class and method-count metrics, including for standalone .dex and .jar files.
- How it differs from related APKLint tools
- It is the only tool here that accepts raw .dex and .jar, not just APKs; apktool centers on resources, the Decompiler on Java source.
- Limitations
- It disassembles and counts; it does not reconstruct original Java or accept bundles.
How to use DEX / Smali Analyzer
- Choose your file — Drop a .APK, .DEX, .JAR file onto the page, or click to select it from your device.
- Send securely — The file is uploaded over an encrypted connection to our analysis servers.
- Read your report — APKLint unpacks and inspects the package and lays out the results on screen.
- Your file is removed — It's deleted by an hourly cleanup job after analysis finishes.
Why use APKLint
Every tool is free with no login and no paywall. Reasonable file and input limits keep the free service stable.
A clean, focused interface with no third-party ad banners cluttering your results.
Files you upload are deleted by a scheduled hourly cleanup after analysis finishes, and never shared.
Built on jadx and apktool for decompiling and disassembly.
Start immediately — no account, login, or email required.
Runs in any modern browser, on desktop or mobile.
Frequently asked questions
What does DEX / Smali Analyzer do?
Disassemble an APK's DEX into smali and decode its resources, with class/method counts and a downloadable smali tree.
What is smali?
Smali is the human-readable assembly form of Dalvik bytecode. It's lower-level than Java but shows exactly what the compiled code does.
Is it free to use?
Yes. Every tool on APKLint is completely free, with no sign-up and no account.
How is my data handled?
Your uploaded file and its result are processed on our servers over an encrypted connection, then removed by the next hourly cleanup after analysis finishes. We never share them.
What files can I send?
A full APK, or a raw .dex, .jar — .APK, .DEX, .JAR — up to 1 GB.