OOmnistu

Blog / Startup Guides

Startup Guides

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.

OOmnistu
Reviewed 2026-11-16 · 6 min read

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:

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

Key sizes, upgrades and resets (as the Play Help page describes them)

Who should hold what (Omnistu advice, not from the source)

Questions to ask your developer or agency

  1. Is the app using Play App Signing, and who generated the app signing key?
  2. Who holds the upload key, where is it stored, and who can reset it in Play Console?
  3. Is the keystore backed up where the business controls it?
  4. Are any key passwords stored in the code repository?
  5. 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.

Sources

Previous
Android App Bundle vs APK: what your app team is publishing