assetlinks.json generator for Android App Links

This tool builds the assetlinks.json file that lets Android open your website's links in your app. It validates the package name and every SHA-256 fingerprint, explains where to host the file, and gives the Google verification URL and adb commands to test it.

Updated

assetlinks.json

[
  {
    "relation": [
      "delegate_permission/common.handle_all_urls"
    ],
    "target": {
      "namespace": "android_app",
      "package_name": "com.example.myapp",
      "sha256_cert_fingerprints": [
        "14:6D:E9:83:C5:73:06:50:D8:EE:B9:95:2F:34:FC:64:16:A0:83:42:E6:1D:BE:A8:8A:04:96:B2:3F:CF:44:E5"
      ]
    }
  }
]
Host the file at
https://www.example.com/.well-known/assetlinks.json
Fingerprints in the file
1
Serve as
Content-Type: application/json, HTTP 200, no redirect
Google verification URL
https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://www.example.com&relation=delegate_permission/common.handle_all_urlsOpen it: you should see your package name and fingerprint in the statements list.
Check headers
curl -sI https://www.example.com/.well-known/assetlinks.jsonExpect 200 and content-type: application/json, and no Location header.
Check on a device (Android 12+)
adb shell pm verify-app-links --re-verify com.example.myappWait a few minutes, then: adb shell pm get-app-links com.example.myapp
  • One fingerprint covers one signing key. If you also install debug builds or distribute through Play App Signing, add those keys too, otherwise verification fails on those builds.
  • With Play App Signing, the key on users' phones is Google's app signing key, not your upload key. Take its SHA-256 from Play Console > Release > Setup > App signing. Google also shows a ready assetlinks snippet there.
  • Publish the file on every host your intent filters declare. Android 15 and later re-verify in the background; changes can take up to seven days to reach all devices.

What does assetlinks.json do?

Android App Links let a verified https link open your app directly instead of showing a chooser. To prove you control the website, Android fetches https://your-domain/.well-known/assetlinks.json when the app is installed and looks for a statement that names your package and signing certificate.

Each statement has a relation (what you grant), a target namespace android_app, the package name, and the SHA-256 fingerprints of the signing certificates that are allowed. The fingerprints and package must match the installed app exactly. Google's page asks for uppercase hex pairs separated by colons.

This tool checks the package name against Android's application ID rules and every fingerprint against the 32-pair format before it writes the file, so the common failure, a fingerprint pasted in the wrong form, is caught here rather than on a device.

[{ "relation": ["delegate_permission/common.handle_all_urls"],
   "target": { "namespace": "android_app",
              "package_name": "<applicationId>",
              "sha256_cert_fingerprints": ["AA:BB:...:FF"] } }]

What must the hosted file satisfy?

Hosting rules from Android Developers and Google's Digital Asset Links pages, checked 2026-11-11.
RuleRequirementIf it fails
Locationhttps://domain/.well-known/assetlinks.json on every host in your intent filtersOther paths or file names are ignored
ProtocolHTTPS with a certificate chain that validates, even if the intent filter is httpEmpty statement list
Content typeapplication/jsonVerification can fail
StatusHTTP 200, with no 301 or 302Redirects are not followed; empty list
FingerprintSHA-256, uppercase hex pairs with colonsNever matches your app
Signing keyThe key users receive: app signing key with Play App SigningWorks on debug builds, fails from Play

How to create and publish assetlinks.json

  1. 1
    Enter the package nameCopy applicationId from your module's build.gradle. It has at least two dot-separated segments.
  2. 2
    Add the fingerprintsPaste each SHA-256 fingerprint on its own line: the app signing key from Play Console for store builds, plus debug or upload keys if you test with them.
  3. 3
    Copy the fileCopy or download the JSON and save it as assetlinks.json in a .well-known folder at your web root on every host in your intent filters.
  4. 4
    Test itOpen the verification URL, check headers with curl, then run the adb commands on an Android 12 or newer device or emulator.

Frequently asked questions

Why does assetlinks.json verification fail only for the Play Store build?
With Play App Signing, Google re-signs your app with the app signing key, so users never get a build signed with your upload key. Add the app signing key's SHA-256 from Play Console > Release > Setup > App signing.
Does the assetlinks.json fingerprint have to be uppercase with colons?
Google's statement list page asks for the uppercase SHA-256 fingerprint, and its examples use colon-separated pairs. This generator rejects lowercase and plain hex so you fix it before publishing.
Can I list more than one app or fingerprint in assetlinks.json?
Yes. The file is a JSON array that can hold several statements, and one statement can list several fingerprints. Use one fingerprint per signing key, for example debug and release.
Why does my assetlinks.json return the wrong content type or a redirect?
Many hosts redirect from http to https or from the bare domain to www. Android does not follow 301 or 302 redirects for this file, so serve it with HTTP 200 and application/json directly on the exact host in the intent filter.
How long until a change to assetlinks.json reaches users?
Google says Android 15 and higher re-verify domains in the background, with changes taking up to seven days to reach all devices. Android 14 and lower pick up changes when the app is installed or updated.

Sources

Related tools

See all 135 free tools

Need a custom dev tool for your team?

We build internal tools, dashboards, APIs, and SaaS platforms. If you can describe it, we can ship it.

Built by CountryDevs · No signup · No ads · We count visits, never what you enter