Registering Android package names

The registration process varies based on whether the package name is new or existing (has installs).

Note that during early access, you can only register package names for apps that you distribute outside of Play. In March 2026, prior to the official launch of Android developer verification, we will try to automatically register all of your Play apps for you. You do not need to register package names for these apps at this time.

For more information about the automatic registration process for Play apps, see page 16 in our walkthrough guide.

Step 1. Provide package name details (common to both new and existing package names)

Navigate to the Android developer verification page.
Select Register package name on the Package names tab.
Enter the package name you want to register.
Provide a friendly name for easy identification within Play Console.
Select Next to proceed.

Step 2: Key registration

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.

Select Add key.
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.
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.

Go to Select key.
Unlike new registration, a list of eligible public certificate fingerprints will be listed. These keys can be used for direct registration.
Scan the list or search directly for your certificate fingerprint.
Select your key (if listed) and select Add key.
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:

Expand the list of other keys on the page.
Confirm that you understand the implications of requesting to use a package name in this way
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.

Step 3: Verifying private key ownership (existing packages only)

To complete verification for an existing package name, you must sign and upload an APK using the private key corresponding to the public key you provided.

Select Upload APK to open the ownership verification user journey.
The next screen will show the package name, the selected SHA-256 public certificate, and signing guidance.
Copy your snippet—a unique identifier tied to your developer account.
Prepare the APK: In your IDE (using an empty project with the same package name or your actual app), navigate to your app's source tree.
Inside the assets folder, create a file named exactly adi-registration.properties.
Open the file and paste the snippet.
- Review the sample project on GitHub to confirm the correct structure and snippet placement for proof of ownership.
Build and Sign: Build a release APK and sign it with the private key that corresponds to the public certificate fingerprint. The signature (via jarsigner or Gradle's signingConfigs) serves as proof of legitimate ownership.
Note: Package name registration for apps with delegated signing keys

If the package name you are registering belongs to an app where the private signing key has been delegated to a third-party distribution platform, like the Samsung Galaxy Store, you must follow these steps instead when proving ownership of the private key.
- Build and upload your release APK or AAB to the distribution platform.
- Download the final signed release APK directly from that distribution platform.
- Upload the signed APK you downloaded to Play Console in 8.
Upload: Return to Play Console, select Upload, locate your signed release APK, and upload it. Android will check the signature and register your ownership.

Step 4: Tracking your package name registration

Android will formally attempt to register your package name, linking it to your verified Play developer identity.

You will receive an email notification upon successful completion.
You can monitor the registration and key status on the Packages page.

Adding additional keys

Once you have registered a package name, you can add additional keys.

Select Upload APK to open the ownership verification user journey.
The next screen will show the package name, the selected SHA-256 public certificate, and signing guidance.
Copy your snippet—a unique identifier tied to your developer account.
Prepare the APK: In your IDE (using an empty project with the same package name or your actual app), navigate to your app's source tree.
Inside the assets folder, create a file named exactly adi-registration.properties.
Open the file and paste the snippet.
- Review the sample project on GitHub to confirm the correct structure and snippet placement for proof of ownership.
Build and Sign: Build a release APK and sign it with the private key that corresponds to the public certificate fingerprint. The signature (via jarsigner or Gradle's signingConfigs) serves as proof of legitimate ownership.
Upload: Return to Play Console, select Upload, locate your signed release APK, and upload it. Android will check the signature and register your ownership.

Was this helpful?

How can we improve it?