# Android assetlinks.json Generator > Generate a valid assetlinks.json file for Android App Links from your package name and SHA-256 certificate fingerprints. Copy-paste ready — free, no signup. - Canonical: https://redirectly.app/tools/assetlinks-generator - Site: [Redirectly](https://redirectly.app) — deferred deep linking for Flutter & React Native Build a correct Digital Asset Links file from your package name and SHA-256 certificate fingerprints. Copy it, host it at `/.well-known/`, and validate it — all free, no signup. ## Generate Your assetlinks.json This is an interactive tool: enter your package name and SHA-256 fingerprints at [https://redirectly.app/tools/assetlinks-generator](https://redirectly.app/tools/assetlinks-generator) and copy the generated JSON. Fingerprints pasted without colons are reformatted automatically. The generated file looks like this: ```json [ { "relation": ["delegate_permission/common.handle_all_urls"], "target": { "namespace": "android_app", "package_name": "com.example.myapp", "sha256_cert_fingerprints": [ "AA:BB:CC:DD:EE:FF:00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF:00:11:22:33:44:55:66:77:88:99" ] } } ] ``` - **package_name** — your app's application ID. - **sha256_cert_fingerprints** — every signing certificate that should be trusted (debug + release; with Play App Signing, the app signing key from Play Console). ## Hosting Checklist 1. **Use the right fingerprint** — with Play App Signing, use the "App signing key certificate" SHA-256 from Play Console, not your upload key. 2. **Place it at the well-known path** — `https://yourdomain.com/.well-known/assetlinks.json`, reachable without redirects. 3. **Serve the right header** — `Content-Type: application/json` over valid HTTPS. 4. **Enable autoVerify in your manifest** — add `android:autoVerify="true"` to the intent filter that handles your domain. 5. **Validate it** — run the [assetlinks.json Validator](https://redirectly.app/assetlinks-validator.md) against your domain; it checks DNS, HTTPS, headers, JSON, and your app statement. ## Frequently Asked Questions ### How do I get my SHA-256 certificate fingerprint? Run `keytool -list -v -keystore your.keystore` and copy the SHA256 line, or find it in Google Play Console under App integrity if you use Play App Signing. Include both debug and release fingerprints while developing. ### Which fingerprint does Google Play use? With Play App Signing enabled, Google re-signs your app with its own key — use the "App signing key certificate" SHA-256 from Play Console, not your upload key, or verification will fail in production. ### Can assetlinks.json contain multiple apps? Yes — the file is a JSON array. Add one statement object per app (package name) and list every signing certificate fingerprint that should be trusted in each statement. ## Related Tools - [assetlinks.json Validator](https://redirectly.app/assetlinks-validator.md) — Check your live Digital Asset Links file, with fixes for anything that fails. - [AASA Generator](https://redirectly.app/tools/aasa-generator.md) — The iOS counterpart for apple-app-site-association files. --- Full site index for AI agents: https://redirectly.app/llms.txt