Select the APK
Drop the file onto the box or click to pick it. Larger apps may take a moment while the package is read into memory.
Open an Android application package to read its package name, version, signing certificate and declared components, and re-sign it with your own key — all in the browser. The file is never uploaded.
Choose an APK file
Drag a .apk here, or click to browse. Everything is parsed locally and nothing leaves your device.
| Path | Size | Compressed | Method | Modified |
|---|
Upload an RSA private key and its X.509 certificate (the standard Android .pk8 + .x509.pem pair), then re-sign the APK with the JAR (v1) scheme. Nothing is uploaded. The output is a v1-only package (the v2/v3 block is stripped) that installs through sideload.
Drop the package in and read the details without installing anything.
Drop the file onto the box or click to pick it. Larger apps may take a moment while the package is read into memory.
The package name, version, icon and signing scheme appear instantly, along with certificate fingerprints.
Expand permissions, components and the full file listing, and search for any entry inside the package.
No install, no upload, just the facts about an Android package.
The APK is parsed as a ZIP directly in the browser. It never reaches the 73hi server.
Read the v1/v2/v3 signing scheme and the certificate MD5, SHA-1 and SHA-256 fingerprints.
The viewer resolves the app label and launcher icon from the compiled resource table.
Browse every entry, its size and method, and filter the list by path instantly.
No. The file is read locally in your browser, parsed as a ZIP and inspected on the spot. It is never uploaded to the 73hi server.
Package name, version name and code, minimum and target SDK, the signing scheme (v1 JAR, v2, v3, v3.1), the certificate subject and issuer, MD5 / SHA-1 / SHA-256 fingerprints, declared permissions, activities, services, receivers, providers and a full file listing.
Yes. The viewer resolves the manifest label and launcher icon, including references into the compiled resource table, and renders the icon directly from the APK.
The whole file is loaded into memory, so very large APKs may be slow or run out of memory on low end devices. Typical apps parse in a fraction of a second.
Yes. Open the APK, then upload an RSA private key (PKCS#8, the standard Android .pk8) and its X.509 certificate. The tool re-signs the package with the JAR (v1) scheme entirely in your browser and downloads the signed file. Nothing is uploaded.