Android app signing: the upload key, the app signing key, and who should hold them
Distinguish Android upload keys from app signing keys and plan ownership, secure storage, resets and supported upgrades.
Every Android app is signed with a private key. Lose the right key and you may be unable to update your app. Let the wrong person hold it and your app can be impersonated. If a developer or agency builds your app, the question "who holds the keys?" belongs in the contract before launch, not after a falling-out. This article explains what Google's documentation says, as read on 15 November 2026. Details change; read the pages before you act.
Two keys, not one
Google's pages describe two keys when you use Play App Signing:
- The app signing key signs the versions delivered to users' phones. Signing identity continuity protects updates, but supported key-upgrade procedures exist. Do not read older wording that the key never changes as a ban on Google's documented upgrades. With Play App Signing, Google stores it in its key management infrastructure and, once configured, you cannot retrieve a copy of it (the Android page adds that Google may keep a backup copy for disaster recovery).
- The upload key is the one you use to sign the file you upload to Google Play. Google uses the upload certificate to check who is uploading, then signs for distribution with the app signing key.
Each key has a public certificate, which can be shared, for example with services that ask for an app's certificate fingerprint. The private keys must be kept secret. Google's advice is to keep the two keys different. Google also says that if you want the same signing key across several app stores, you must supply your own key when setting up Play App Signing rather than letting Google generate it.
Why separate keys help
The docs say that with a separate upload key, if the upload key is lost or compromised you can request an upload key reset in Play Console, and the reset does not affect the app signing key Google uses to sign for users. Because the signing key stays safe with Google, you can keep publishing updates to the same app even after changing upload keys. For apps that do not use Play App Signing, the Android page says that if you lose your signing key, you lose the ability to update the app, and the Play Help page adds that you would have to publish a new app with a new package name.
What the pages require
- Play App Signing is required for new apps on Google Play; it is optional for apps created before August 2021, per the Play Help page. Apps released as Android App Bundles need it configured before the first upload.
- To use Play App Signing you must be the account owner or a user with the release to production and Play App Signing permission, and you must accept its terms.
- For a new app, if you do nothing, Google generates the app signing key and the key used for your first release becomes the upload key. You can also reuse a key from another app in the same developer account, or supply your own key with Google's export tool.
- Keys made yourself should be valid for a long time: the Android page recommends 25 years or more, and says a key used on Google Play must be valid beyond 22 October 2033.
- Debug builds use an automatic debug certificate that is insecure by design and is not accepted by Google Play for publishing.
- Android Studio can keep signing details in plain text in build files; the page says teams should move this information out of the build files, since otherwise anyone with the code can read it.
Key sizes, upgrades and resets (as the Play Help page describes them)
- Size: a Google-generated app signing key is a 4096-bit RSA key. If you upload your own app signing key, or create an upload key, it must be RSA and at least 2048 bits.
- Lost or compromised upload key: you create a new one and the account owner starts a reset in Play Console. Google support registers the new key, and the account owner and global admins are then notified. Google says a reset does not affect the app signing key.
- Compromised or weak app signing key: for apps that use app bundles, you can request an app signing key upgrade, which Google says is allowed once a year per app for installs on Android 7.0 (API 24) and above. The page lists consequences: you must register the new and old certificates with any API providers, apps that share data or code through a shared key need updating, and users who install updates peer to peer can only install updates signed with the key they already have. This is a process to plan with your developer, not a routine step.
- Apps created before August 2021 that manage their own keys: the Android page says if you lose the key you cannot ship updates to the existing app, and that such apps cannot use app bundles, Play Feature Delivery or Play Asset Delivery.
- Play App Signing also uses APK Signature Scheme v4 for eligible apps on Android 11 and above; the page says no developer action is needed.
Who should hold what (Omnistu advice, not from the source)
- The Google Play developer account and the app signing setup should belong to the business that owns the app, not to the agency. If an agency publishes from its own account, ask how ownership will be transferred, and test that before you need it.
- Keep a record of who holds the upload keystore and its passwords, and keep a second secure copy in a place the business controls. A key stored only on one developer's laptop is a single point of failure.
- Do not send keystore files or passwords by email or chat. Use a password manager or a secrets store with access control.
- Ask the developer to confirm in writing which of the two models you are in (Google generated the signing key, or you supplied it), because that changes what is recoverable.
- If the app might later be published on other stores, decide about key ownership before the first release, because Google's page says to supply your own key if you want the same signing key across stores, and a key Google generated cannot be retrieved afterwards.
Questions to ask your developer or agency
- Is the app using Play App Signing, and who generated the app signing key?
- Who holds the upload key, where is it stored, and who can reset it in Play Console?
- Is the keystore backed up where the business controls it?
- Are any key passwords stored in the code repository?
- If we change agencies, how do we hand over publishing?
Limits
Both Google pages were read in full on 15 November 2026. We did not read the pages they link to, including the command line signing tool and signature scheme references, and we did not test any of the steps. The upgrade section is summarised, not a procedure; follow Google's page and your developer. Ownership and contract wording is advice; get legal advice for agreements. We say nothing about Apple's signing, which is different.
By Omnistu.