Developer tools
AAB Signer
Sign an Android App Bundle for Google Play in your browser. Free, open source, built for Closed Test Pro developers.
Studio
Prepare a signed release
Walk through bundle → key → confirm. Nothing is stored after the job ends.
Add your App Bundle
Use an unsigned `.aab` from your build. Max 100.0 MB.
No file selected
Limits: AAB 100 MB · keystore 10 MB · artifact kept ~24 hours
Transparency
Live signing pipeline
Every run is public. You can follow the same stages below in GitHub Actions and read the exact workflow that touches your files.
Secure upload
Start Actions job
Run jarsigner
Verify signature
Ready to download
Every signing job is public. Read the workflow source, then watch live Actions runs while your bundle is signed.
How it works
Four steps. No desktop JDK install required.
Upload
Add your unsigned AAB in the studio wizard.
Key
Attach keystore and alias credentials for Play upload signing.
Sign
A GitHub Actions job runs jarsigner on a clean VM.
Download
Get the signed bundle and upload it to Play Console.
Developer guide
Sign an Android App Bundle online for Google Play
Google Play requires a signed Android App Bundle (AAB) before you can ship to closed testing or production. If your build pipeline produces an unsigned `.aab`, you need jarsigner (or Android Studio) with your upload keystore.
Closed Test Pro AAB Signer runs that signing step in the browser: upload the unsigned AAB and keystore, enter alias and passwords, then download a signed bundle ready for Play Console. Files are processed on ephemeral GitHub Actions runners and deleted after the job.
Prefer a written walkthrough? Read our guide: How to sign an Android AAB online free.
Closed Test Pro
Finished signing? Complete closed testing next.
New Play developer accounts still need 12 opted-in testers for 14 days. Closed Test Pro helps you find real Android developers and track daily opens.
FAQ
Simple answers about signing AABs online
No. This tool is free. Signing uses free GitHub Actions time on our public repo, and Closed Test Pro does not charge for it.
Yes. Your keystore is sent over HTTPS, used only to sign this one job, then deleted. The job runs on a temporary GitHub machine that is thrown away after. You can check the public workflow code anytime.
Google Play will not accept an unsigned App Bundle. You must sign it with your app’s private key before you upload it to Play Console.
We use jarsigner from the official Java tools, with the SHA256withRSA method. That is a standard way to sign Android App Bundles.
Yes. The file you download is a normal signed AAB. You can upload it to production if you used the correct keystore for that app.
In Android Studio use Build → Generate Signed Bundle/APK, or use the keytool command. If the app is already on Play, keep using the same upload keystore you used before.
Android Studio is great when you build on your machine. This online AAB signer helps when you already have an unsigned .aab and need jarsigner without installing a local JDK. Both use the same signing standards Google expects.
Upload an unsigned .aab up to 100 MB, and a keystore as .jks, .keystore, .p12, or .pfx up to 10 MB. You also need the keystore password, key alias, and key password.
Need help? closedtestpro@gmail.com