Android developer verification
Stay organized with collections
Save and categorize content based on your preferences.
Android developer verification is a new requirement designed to link real-world
entities (individuals and organizations) with their Android applications.
Starting in 2026, Android will require all apps to be registered by verified
developers in order to be installed by users on certified
Android devices. This guide shows what you need to do.
Why these changes are happening
Android's developer verification adds a layer of security. This protects users
by deterring bad actors and making it harder for them to spread harm.
How this helps you
A safer, more trusted ecosystem benefits the entire developer community.
- Deters bad actors who prefer to operate anonymously.
- Makes it harder to spread harm by linking bad apps to their developers.
This helps us hold developers accountable, enforce safety policies, and
remove malicious networks.
- Boosts user confidence, helping you build relationships with new users
and establish trust.
What you need to do
Complete these two steps:
- Verify your identity: Provide information and documentation to confirm
your identity as an individual or an organization.
- Register your package names: Prove ownership of your apps and register
them with your verified identity.
This guide walks you through each requirement.
Timelines and milestones
The Android developer verification rollout happens in phases. This approach
allows us to incorporate your feedback and gives you time to prepare. Here's
what to focus on at each stage:
Date |
Milestone |
Developer focus |
August 2025 |
New Android developer verification requirements announced |
Learn about the new requirements and sign up for early access. |
October 2025 |
Early access begins |
If invited, start your identity verification and app registration. |
March 2026 |
Registration opens for all developers |
Begin your identity verification and app registration for all apps
you want to remain installable on certified Android devices. |
September 2026 |
Regional enforcement begins |
Verify compliance to avoid installation blocks on your apps in Brazil,
Indonesia, Singapore, and Thailand. |
2027 and beyond |
Global enforcement |
The rollout continues worldwide. |
Key concepts
Before you start, review these key terms:
- Identity verification: The process of providing information and official
documentation to verify your identity as an individual or organization.
- Package name registration: The process of creating a formal, verifiable
link between your app's unique package name and signing keys.
- App signing key: The certificate used to sign your APK.
- Certified Android devices: Google enforces Android developer verification
requirements on these devices. If your app runs on a certified device,
these requirements apply to you, regardless of your app's download source.
- Android Developer Console (ADC): A console for developers who
distribute apps only outside of Google Play.
- Google Play Console (PDC): The console for developers who distribute
apps on Google Play. If you have a Play Console account, use it to complete
the verification requirements.
Find your path
Use the following table to find the correct console and instructions for your
situation.
Sign up
for early access to the Android developer verification
experience. You might receive an invitation to our invite-only early
access. |
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-08-22 UTC.
[null,null,["Last updated 2025-08-22 UTC."],[],[],null,["# Android developer verification is a new requirement designed to link real-world\nentities (individuals and organizations) with their Android applications.\nStarting in 2026, Android will require all apps to be registered by verified\ndevelopers in order to be installed by users on certified\n[Android devices](https://www.android.com/certified/partners/). This guide shows what you need to do.\n\nWhy these changes are happening\n-------------------------------\n\nAndroid's developer verification adds a layer of security. This protects users\nby deterring bad actors and making it harder for them to spread harm.\n\nHow this helps you\n------------------\n\nA safer, more trusted ecosystem benefits the entire developer community.\n\n- **Deters bad actors** who prefer to operate anonymously.\n- **Makes it harder to spread harm** by linking bad apps to their developers. This helps us hold developers accountable, enforce safety policies, and remove malicious networks.\n- **Boosts user confidence**, helping you build relationships with new users and establish trust.\n\nWhat you need to do\n-------------------\n\nComplete these two steps:\n\n1. **Verify your identity**: Provide information and documentation to confirm your identity as an individual or an organization.\n2. **Register your package names**: Prove ownership of your apps and register them with your verified identity.\n\nThis guide walks you through each requirement.\n\nTimelines and milestones\n------------------------\n\nThe Android developer verification rollout happens in phases. This approach\nallows us to incorporate your feedback and gives you time to prepare. Here's\nwhat to focus on at each stage:\n\n|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|\n| Date | Milestone | Developer focus |\n| August 2025 | New Android developer verification requirements [announced](https://android-developers.googleblog.com/2025/08/elevating-android-security.html) | Learn about the new requirements and sign up for early access. |\n| October 2025 | Early access begins | If invited, start your identity verification and app registration. |\n| March 2026 | Registration opens for all developers | Begin your identity verification and app registration for all apps you want to remain installable on certified Android devices. |\n| September 2026 | Regional enforcement begins | Verify compliance to avoid installation blocks on your apps in Brazil, Indonesia, Singapore, and Thailand. |\n| 2027 and beyond | Global enforcement | The rollout continues worldwide. |\n\nKey concepts\n------------\n\nBefore you start, review these key terms:\n\n- **Identity verification**: The process of providing information and official documentation to verify your identity as an individual or organization.\n- **Package name registration**: The process of creating a formal, verifiable link between your app's unique package name and signing keys.\n- **App signing key** : The certificate used to [sign your APK](/studio/publish/app-signing).\n- **Certified Android devices** : Google enforces Android developer verification requirements on these devices. If your app runs on a [certified device](https://www.android.com/certified/), these requirements apply to you, regardless of your app's download source.\n- **Android Developer Console (ADC)**: A console for developers who distribute apps only outside of Google Play.\n- **Google Play Console (PDC)**: The console for developers who distribute apps on Google Play. If you have a Play Console account, use it to complete the verification requirements.\n\nFind your path\n--------------\n\nUse the following table to find the correct console and instructions for your\nsituation.\n\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [Sign up for early access](https://goo.gle/android-verification-early-access) to the Android developer verification experience. You might receive an invitation to our invite-only early access. |\n\n|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **If you distribute apps**... | **Next Steps** |\n| **Only on Google Play** | Use your existing [Play Console account](/developer-verification/guides/google-play-console). |\n| **Both on and off Google Play** | Use your existing [Play Console account](/developer-verification/guides/google-play-console). A new option lets you register your non-Play apps and keys. |\n| **Only outside of Google Play** | Create an account in the [Android Developer Console](/developer-verification/guides/android-developer-console). |"]]
