/ 01TOOLFREE TOOLS · FOR DEVELOPERS
assetlinks.json generator
Enter your package name and SHA-256 fingerprints and get a valid Digital Asset Links file for Android App Links, ready to upload. It fixes fingerprint format as you type and runs entirely in your browser.
assetlinks.json
[]
Upload it to https://your-domain/.well-known/assetlinks.json, then test it with the assetlinks.json checker.
What goes in the file
assetlinks.json is a list of statements. Each statement grants one Android app a relation with your website. For App Links the relation is delegate_permission/common.handle_all_urls, and the target names the app by its package name and the SHA-256 fingerprints of the certificates allowed to sign it:
[
{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "com.example.shop",
"sha256_cert_fingerprints": ["14:6D:E9:…:44:E5"]
}
}
]Several apps (a main app and a lite app, for example) can share one domain: add one statement per package. Android picks the app whose package and signature match what is installed.
Get the fingerprint right
Most App Links failures are fingerprint mistakes. With Play App Signing, Google re-signs your app, so the key on users' phones is Google's app signing key, not the upload key in your keystore. Copy that one from the App signing page in Play Console. For local builds, read it from the keystore:
keytool -list -v -keystore release.keystore -alias release | grep SHA256
# debug builds:
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android | grep SHA256Then add android:autoVerify="true" to the intent filter for your link host. If your links run on a Strait link domain, you paste the same fingerprints into your app settings and Strait serves this file for you; see App Links & Universal Links.
Questions
Where do I find my SHA-256 fingerprint?
For apps installed from Google Play with Play App Signing, copy the SHA-256 certificate fingerprint of the app signing key from the App signing page in Play Console. For a build you sign yourself, run keytool -list -v on the keystore and copy the SHA256 line. Debug builds use the debug keystore in ~/.android/debug.keystore.
Should I list more than one fingerprint?
List every key that signs a build you want links to open: the Play app signing key for store installs, and your upload or debug key if testers install builds signed with those. One statement can hold several fingerprints.
What does "share sign-in credentials" add?
It adds the get_login_creds relation, which lets Android share saved passwords between your website and your app. It is optional and does not affect whether links open the app.
Is anything I type sent to a server?
No. The file is built in your browser as you type. The page works offline once loaded.
Skip hosting the file yourself
On a Strait link domain the association files are generated from your app settings and kept in step with every change.
More free tools
AASA generator
Team ID, bundle ID and the paths your app handles in, an apple-app-site-association file out, with exclusions.
UTM builder for app links
Tag a link for WhatsApp, Instagram, SMS, email or a poster, and build a Google Play referrer URL for the same campaign.
App QR code generator
A QR code for a link that opens your app, as SVG or PNG, with a quiet zone and error correction set for print.