To reset your upload key on Google Play, create a new upload key, export its certificate as a PEM file, then go to Play app signing in Play Console and click Request upload key reset. This only works if your app uses Play App Signing. Your users aren’t affected, because Google keeps signing their installs with the same app signing key.
Can you reset your upload key on Google Play?
You can reset your upload key on Google Play only when the app is enrolled in Play App Signing. Play Console Help says that for the upload key, if it’s compromised or lost, Google can reset it for you.
The app signing key is another story. The same page says that key cannot be reset if you manage it yourself and lose it. So before you generate anything, work out which key you actually lost.
| Your situation | What you lost | Can Google reset it? |
|---|---|---|
| Enrolled in Play App Signing, keystore gone | Upload key | Yes, request an upload key reset |
| Enrolled, keystore leaked or shared | Upload key | Yes, same reset |
| Not enrolled, keystore gone | App signing key | No |
| Not enrolled, key leaked | App signing key | No reset; see key upgrade below |
To check, open Play app signing in Play Console. If you see an Upload key certificate section next to the app signing key certificate, you’re enrolled. If you’re unsure what each key does, the upload key vs app signing key post covers the split.
What you need before you start
A reset needs three things.
- Access to the right Play Console account. Play Console Help says configuring Play App Signing needs admin permission, so sign in with an admin user.
- Java’s keytool, which ships with a JDK and with Android Studio.
- A safe place for the new keystore before you create it. The keystore file guide covers where to keep it.
How to reset your upload key, step by step
The Google Play upload key reset is six steps on your side, taken from Play Console Help, then a wait for Google.
- Create a new upload key. Use Android Studio’s Generate Signed Bundle wizard, or keytool as shown in signing an APK from the command line. Android’s guide recommends a key valid for at least 25 years.
- Export its certificate to PEM. Google’s example command is:
keytool -export -rfc -keystore upload-keystore.jks -alias upload -file upload_certificate.pem - Open Play app signing. In Play Console, go to Protected with Play > Play Store protection > Manage Play app signing.
- Start the request. In the “Upload key certificate” section, click Request upload key reset.
- Give a reason. For example: “Laptop with the upload keystore was stolen.”
- Upload the PEM file (
upload_certificate.pem) and click Request.
Don’t upload the .jks file. Google only needs the certificate, which holds the public half of your new key.
Why the alias in Google’s keytool command may not match yours
The -alias value in the export command must be the alias you chose for your new key. Google’s two pages use different example names. Play Console Help uses -alias upload, while the Android signing guide uses -alias upload-alias and a file called output_upload_certificate.pem.
Neither is a required name. Use the alias you typed when you created the key. If keytool says it can’t find the alias, the keystore is fine; the name is just wrong.
What happens after you request the reset
After you request an upload key reset, you wait for Google before your next upload. Neither Google page says how long that takes. One developer who lost their signing key reported that the new key was available about two days after the request.
My take: treat it as a two-day pause. Don’t announce a release date, and don’t delete the old keystore if you still have it, until uploads with the new key go through.
The reset doesn’t touch your users. Android’s guide says resetting the upload key will not affect the app signing key Google uses to re-sign APKs. You keep uploading versions as updates to the original app, so reviews, installs and the package name stay put.
What if your app isn’t enrolled in Play App Signing?
If your app isn’t enrolled in Play App Signing, there’s no upload key to reset. Android’s guide says opting out was only possible for apps created before August 2021. For those apps, losing the signing key means you lose the ability to update your app, and Google cannot retrieve it.
What’s left is covered in what happens if you lose your app signing key. A new key means a new app listing.
A leaked key (not lost) has one more route. Play Console Help describes an annual key upgrade for installs on Android 17 (API level 37) or higher. That’s a different process from an upload key reset, and it only covers those newer installs.
How this works when you build in the browser
If you build your AAB in a browser-based tool, your upload key is whatever key that tool signs with. In Web2Apk, signing runs in your browser and the private key isn’t uploaded to a build server. The key is kept as a password-encrypted backup with a password of at least 10 characters, which can’t be recovered if forgotten.
The limitation: Web2Apk can’t import JKS or P12 keystores, only its own encrypted backups. If you signed earlier Play releases with a keystore from another tool, keep using that tool for updates. Changing to a different key for an enrolled app means going through an upload key reset. The APK signing and updates guide explains the backup steps. A new upload key isn’t store approval, either: the listing and review stay separate, as the Play App Signing explainer notes.
How to avoid the next reset
The best reset is the one you never request. These habits make it unlikely:
- Keep two copies of the new keystore, one offline.
- Store the password and alias in a password manager, apart from the file.
- Turn on 2-Step Verification for every Play Console user, as Play Console Help recommends.
- Label the keystore with the app’s package name.
FAQ
Does resetting the upload key affect my existing users?
No. Android’s signing guide says resetting the upload key doesn’t affect the app signing key Google Play uses to re-sign APKs, so installs keep updating normally.
How long does an upload key reset take?
Google’s help pages don’t give a time. One developer who went through it reported the new key was usable about two days after the request, so don’t plan a release for the same day.
Can I reset the key if my app isn’t in Play App Signing?
No. Without Play App Signing your key is the app signing key, and Play Console Help says it cannot be reset if you manage it yourself and lose it.
Can I reuse my old keystore password for the new upload key?
You can, but it’s a new key either way. What Google checks is the certificate you upload, not the password.