jquery.app
English
EnglishDeutschFrancaisEspanol日本語Nederlands

GitHub Pages Tools

Free Assetlinks & AASA Generator

One tool that generates both Android's /.well-known/assetlinks.json and iOS's /.well-known/apple-app-site-association for deep linking and universal links. Enter your Android package name and SHA-256 fingerprint, plus your iOS Team ID and Bundle ID, with custom path rules.

Loading tool...

What is Assetlinks & AASA Generator?

assetlinks.json and apple-app-site-association (AASA) are JSON files placed at the /.well-known/ path of a domain to enable deep linking. Android uses assetlinks.json to verify that an app can open links for a domain. iOS uses the AASA file to enable Universal Links that open content in your app instead of the browser. Both files must be served over HTTPS without redirects.

quickAnswer

assetlinks.json (Android) and apple-app-site-association (iOS) enable deep linking from your website to your mobile app. Generate both files, place them at /.well-known/ on your domain, and serve over HTTPS without redirects.

limitations

  • iOS AASA file changes require the user to reinstall the app for the new rules to take effect. This makes iOS deep link configuration changes slow to propagate.
  • Both files require direct HTTPS access to /.well-known/ without redirects. Some CDN configurations and static hosts redirect unknown paths, which silently breaks deep linking.
  • Android App Links verification requires a matching Digital Asset Links API response. The assetlinks.json file alone is sufficient for verification, but Google may also check the app listing in the Play Store.

How to use this tool

  1. For Android: enter your app's package name and the SHA-256 fingerprint of your signing certificate.
  2. For iOS: enter your Apple Developer Team ID, the app's Bundle ID, and path rules for which URLs should open in the app.
  3. Select the output target — Android, iOS, or both.
  4. Deploy the generated JSON file(s) to the /.well-known/ directory on your domain.

What you can use it for

  • Set up deep linking so links to your website open directly in your mobile app instead of the browser.
  • Generate both Android and iOS deep link verification files at once for a cross-platform Flutter or React Native app.
  • Configure path-specific rules so only certain URL patterns (like /posts/*) open in the app.

Use cases

Practical examples

example

Cross-platform app deep linking

A Flutter app wants links to example.com/posts/ to open in the app on both Android and iOS. Generate the Android assetlinks.json with the app's signing key SHA-256 and the iOS AASA with path rules for /posts/*. Deploy both to /.well-known/.

example

Android-only deep link verification

An Android app needs to handle all URLs from its domain. Generate assetlinks.json with the package name and SHA-256, set the path to /*, and deploy to /.well-known/assetlinks.json.

Common mistakes

  • Forgetting to serve the files over HTTPS without redirects — both Android and iOS require direct HTTPS access to the /.well-known/ path.
  • Using a different signing key for the app than the one in assetlinks.json — the SHA-256 must match the exact certificate used to sign the published APK or AAB.
  • iOS AASA file requires an app reinstall to pick up changes — the file is fetched only once during app installation.

verification

  1. Verify Android: https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://yoursite.com&relation=delegate_permission/common.handle_all_urls
  2. Verify iOS: Use the App Search API Validation Tool in your Apple Developer account or test on a physical device after reinstalling the app.

FAQ

Questions about Assetlinks & AASA Generator

How long does it take for changes to assetlinks.json to take effect?

Android checks assetlinks.json periodically, typically within 24 hours. Google Play's App Links verification can trigger a re-check sooner. For testing, use the Android App Links Verification API or the App Links Assistant in Android Studio to force an immediate re-verification.

Does the iOS AASA file need a .json extension?

Apple recommends serving the file at /.well-known/apple-app-site-association with no file extension. However, some CDNs and static hosts add extensions automatically. Also serve it at /.well-known/apple-app-site-association.json as a fallback. iOS checks both locations.

Can I have different path rules for Android and iOS?

Yes. The Android assetlinks.json and iOS AASA file are completely independent. You can configure Android to handle all paths while iOS handles only specific paths. Run the tool twice — once for each target — to generate separate files with different rules.

Related tools

More github pages tools

Github Pages

COOP/COEP/CORP Header Builder

Build Cross-Origin isolation headers for SharedArrayBuffer, WebAssembly threads, and cross-origin security. Choose from presets with debugging checklists.

Open tool

Github Pages

CORS Header Generator

Generate CORS HTTP headers for any origin, method, and credential configuration. Output in raw HTTP, Nginx, Apache, Express, or Cloudflare Workers format.

Open tool

Also try

Also try

Seo

AI Crawler robots.txt Builder

Build a robots.txt policy for AI crawlers. Choose from open, selective, or strict presets and block specific AI training bots while allowing search engines.

Open tool