Upload and fingerprint
The server stores the submitted package, calculates SHA-256 and records file size and format.
automatic
Submit APK, XAPK, AAB or APKS packages directly. Each release receives a SHA-256 fingerprint, package metadata review and a public verification record before publication.
Create a publisher account first, then upload your package from the secure developer dashboard.
Create developer accountTrack your release from file selection to moderation. The published listing keeps the file fingerprint and release metadata visible to users.
The server stores the submitted package, calculates SHA-256 and records file size and format.
automaticAPK packages are inspected for package name, version, Android requirement, architecture, permissions and signature details when available.
automaticThe submission remains pending while an administrator checks the publisher, description, category, download data and verification record.
review queueApproved releases appear in the public catalog with their download variants, SHA-256 fingerprint and available scan metadata.
after approvalCreate a developer account and send evidence that connects your publisher identity with the existing app or game listing.
Submit a production release signed with the same certificate used by your published app. Administrators can compare the certificate fingerprint with the existing listing.
Submit signed packageAdd the verification value supplied during review to the publisher website or DNS zone connected with the app.
Approved publisher profiles can be connected to their public releases and verification records.
Manage publisher information, package submissions, file verification and release status from dedicated developer URLs.
Maintain your public developer name, company, website, support email, country, description and logo.
Open developer profile →Upload Android packages, fill public information and track pending or published submissions from your account.
Submit a release →Calculate a SHA-256 fingerprint and compare it with fingerprints stored for published releases.
Verify a file →Registration, login, password recovery, dashboard, submissions and verification each use a separate clean URL.