Select key for existing package name

The next step depends on whether you are registering a new or existing package name.

A. Registering a new package name

For a new package name that has never been seen on Android, you just need to provide the public key certificate from your app’s signing key pair.

1. Select Add key.
2. Provide the public key certificate from your app's signing key pair. (This signing key is what Android uses to verify that app updates are from you.) Learn how to locate your public SHA-256 certificate.
3. Enter your key and select Add key.

B. Registering an existing package name

To register an existing package name, you must prove ownership of a known private signing key.

1. Select Add key.
2. Unlike new registration, a list of eligible public certificate fingerprints will be listed. These keys can be used for direct registration.
3. Scan the list or search directly for your certificate fingerprint.
4. Select your key (if listed) and select Add key.
5. You will return to the registration page, confirming the key has been added.

Key eligibility rules and requesting to use a package name

The list of eligible keys is determined by package name eligibility rules designed to minimize package name sharing (introduced as part of Android developer verification).

In scenarios where a package name is used by multiple developers or has multiple signing keys, eligibility is determined as follows:

Scenario	Rule for direct registration	Rule for other developers
Majority key holder	The key that accounts for over 50% of total known installs has priority.	All other developers must submit a request.
50+ installs	If no single key has >50% of installs, all keys with 50 or more installs are eligible.	Developers with keys having fewer than 50 installs must submit a request.
Under 50 installs	If no keys meet the 50-install threshold, all known keys can be used on a first-come, first-served basis.	Once one developer registers, others must submit a request.

If your SHA-256 fingerprint certificate is NOT listed as eligible, you can still register, but the process requires a request to Google, which may be rejected:

1. Expand the list of other keys on the page.
2. Confirm that you understand the implications of requesting to use a package name in this way
3. In addition to completing the proof of ownership (see Step 3), you will also be required to submit a rationale for using the package name (for example, migrating users would disrupt app distribution).

During early access, you will only be able to register package names for apps where you own an eligible key. The ability to register packages with other keys will roll out with the official launch in March 2026.

To learn more, make sure to read step 3 of the Registering Android package names article.