We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Extract readable code and app resources from APK, DEX, AAB, AAR, and common split-package formats.
Choose filesDrop a file here, or click to choose
.apk · .xapk · .aab · .aar · .apks · .apkm · .dex
Max 5 MB
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Android packages contain bytecode, manifests, resources, configuration files, and sometimes native libraries. Processing produces a ZIP with readable Java-like code and recognized package files, not a complete Android Studio project.
APK is an installable package, AAB generates device-specific APKs, AAR contains library assets, and DEX stores executable code; XAPK, APKM, and APKS may bundle a base package with configuration splits. Unity Mono assemblies may yield separate C# output, but IL2CPP native code cannot be reconstructed into C#.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Select an authorized .apk, .dex, .aab, .aar, .xapk, .apkm, or .apks file up to 5 MB.
Upload it to the server and wait for processing to finish.
Review the manifest, package folders, resources, and several code files.
Download the organized ZIP and compare relevant findings with the original project or runtime evidence.
Tip: For split packages, provide the complete archive with its base and required configuration packages.
Use cases
See how the tool fits into real work and everyday tasks.
Confirm that a release contains the intended permissions, resources, and packaged files.
Inspect manifests, DEX code, and configurations for clues behind device or version issues.
Document static findings from packages you are authorized to test and validate them at runtime.
Q&A
Find concise answers to common questions and confusing cases.
No. It reads code and resources but does not create device-specific splits, sign files, or generate an installation package.
Not necessarily. Kotlin bytecode usually appears as Java-like code, and coroutines, inline functions, and compiler-generated structures may look different.
Not always. Obfuscation can shorten names, while comments, resource names, and module structure may already have been removed during compilation.
Notes
Review scope, result limitations, and important precautions before use.
Analyze only software you own or are authorized to inspect; decompilation does not grant rights to copy, modify, redistribute, or bypass restrictions.
Files are sent to a server for processing, and temporary working directories are cleared after the task ends. Do not upload personal data, secrets, confidential code, or packages containing sensitive identifiers, endpoints, certificates, or test data.
Missing splits, corruption, optimization, obfuscation, compression, hardening, complexity, or timeouts may cause incomplete or distorted results. Static output cannot prove runtime behavior or replace dynamic testing and verification against the original project.
Related
Discover related tools, collections, and available API capabilities.