Complete APK signing toolkit with v1, v2, and v3 scheme support. Verify signatures, optimize with zipalign, and manage keystores securely — all inside your IDE.
Signing Tools provides a complete APK signing toolkit integrated directly into your JetBrains IDE. It supports all three Android signing schemes — v1 (JarSigner), v2 (APK Signature Scheme), and v3 (APK Signature Scheme v3) — and wraps Google's apksigner utility with a streamlined UI that handles scheme selection, zipalign optimization, and signature verification in one place.
APK signing is a mandatory step before any Android app can be installed on a device or submitted to the Play Store. The signing process involves selecting the correct scheme for your target Android versions, ensuring the APK is properly zipaligned, and applying the signature with a valid keystore. Signing Tools manages this entire pipeline, from raw unsigned APK to fully signed and verified output.
Credential security is a key part of the module. All keystore paths, aliases, and passwords are stored through IntelliJ's PasswordSafe API, which encrypts credentials using the IDE's built-in security layer. No passwords are ever written to plain-text files or exposed in command history.
Manual APK signing with command-line tools is fragile and easy to get wrong:
apksigner usage — The command-line interface requires precise argument ordering (--ks, --ks-key-alias, --ks-pass, --key-pass, --v1-signing-enabled, etc.). A single typo produces a corrupted or unsigned APK with little useful error feedback.apksigner verify --verbose --print-certs separately and parsing dense output manually.Sign APKs using any combination of signing schemes. The v1 JarSigner scheme provides backward compatibility for devices running Android versions prior to 7.0, while v2 and v3 APK Signature Schemes offer stronger whole-file integrity protection and faster verification on modern Android. ADB Pro uses Google's apksigner under the hood, ensuring full compatibility with the latest Android platform requirements. Select individual schemes or enable all three with a single checkbox.
Verify the signature of any APK with a single click. The verification report shows which signing schemes are present (v1, v2, v3), certificate chain details including issuer, subject, validity period, and serial number, and whether the signature covers the entire APK contents. This makes it easy to catch signature mismatches or missing schemes before uploading to the Play Store or distributing to testers.
Run zipalign on unsigned or signed APKs to ensure all uncompressed data starts at a 4-byte boundary. Proper alignment reduces RAM usage on the target device and is a mandatory requirement for Play Store submission. ADB Pro automatically detects misaligned APKs and offers one-click alignment, or you can configure automatic zipalign as a pre-signing step in settings.
Store keystore paths, key aliases, and passwords securely using IntelliJ's PasswordSafe API. Credentials are encrypted by the IDE and never written to plain-text config files. Switch between multiple keystores — debug, release, enterprise — from a dropdown without re-entering passwords each session. Keystore entries are validated on load to confirm the file still exists and the alias is accessible.
Save frequently used signing configurations as named favorites for instant access. Each favorite stores the keystore path, key alias, preferred signing schemes, and zipalign flag. This is especially useful for teams managing multiple app variants, white-label builds, or separate debug and release signing identities. Favorites sync with the IDE project settings for consistent access across team members.
Signing Tools settings are accessible from Settings > Tools > ADB Pro > Signing Tools. From there you can configure:
apksigner and zipalign binary paths (auto-detected from Android SDK by default)Quick-access actions are available under the Tools > ADB Pro menu: Sign APK, Verify APK Signature, Zipalign APK, and Manage Keystores.
After signing an APK, confirm that everything was applied correctly:
apksigner verify --verbose --print-certs app.apk and confirm that the output shows the correct signer certificate (CN, OU, O fields match your keystore).true).zipalign -c -v 4 app.apk to confirm the APK passes the alignment check. The exit code should be 0 with "Verification successful" in the output.adb install app.apk and confirm the app launches without signature-related errors.sign, verify, and rotate.