Generate PWA
Free Tool

Digital Asset Links Generator

Generate your assetlinks.json file to verify domain ownership for Google Play Store WebAPKs and Trusted Web Activities (TWA).

Do you actually need this file?
Standard PWA (Browser Installation)

You do not need this file. If users install your web app directly via Chrome or Safari on desktop or mobile (e.g. with Progressier) a standard Web App Manifest and Service Worker are all that are required. AI tools often incorrectly state this is needed for pure PWAs.

Google Play Store (TWA / APK)

You do need this file. If you wrap your PWA using Bubblewrap, PWABuilder, or Android Studio to distribute on Google Play, Android uses this file to verify you own the domain and remove the browser URL address bar.

/.well-known/assetlinks.json

Where do I upload this file?

  1. Upload this generated file to your root web server directory: https://yourdomain.com/.well-known/assetlinks.json.
  2. Ensure your server responds with HTTP status 200 OK. Redirects (301/302) are strictly forbidden by Android's Digital Asset Links verification system.
  3. Verify your server sends the header: Content-Type: application/json.

Digital Asset Links FAQ

What is a Digital Asset Links (assetlinks.json) file?

Digital Asset Links is a Google protocol that establishes cryptographically verified trust between an Android app and a website. When an Android app wrapped as a Trusted Web Activity (TWA) launches a website, the Android operating system downloads /.well-known/assetlinks.json from that website. If the package name and cryptographic SHA-256 fingerprint match the installed app, Android removes the Chrome browser address bar to give the user a full-screen native experience.

Why do AI assistants claim I need assetlinks.json for my PWA?

Large language models frequently conflate standard browser-installed Progressive Web Apps (PWAs) with Google Play Store packaging methods (Trusted Web Activities/WebAPKs). A standard PWA installed directly from Safari or Chrome only requires an app manifest file and a registered service worker. You only need assetlinks.json if you are submitting your app to the Google Play Store as an APK or AAB package.

Where do I find my app's SHA-256 fingerprint?

If your app is published on the Google Play Store using Play App Signing, log in to the Google Play Console, navigate to Setup > App Integrity, and scroll to the App Signing tab. You will see your official SHA-256 certificate fingerprint, as well as an auto-generated Digital Asset Links snippet. If you are signing your APK locally, you can extract it using keytool: keytool -list -v -keystore your-release-key.keystore.

Why do I need multiple SHA-256 fingerprints?

If you use Google Play App Signing, Google re-signs your app with their own private key before delivering it to users. This means your local build (used for testing or developer builds) and the production build downloaded from the Play Store have two completely different SHA-256 certificates. You can add both fingerprints to your assetlinks.json array so verification succeeds in both development and production.

Why is the browser address bar still showing in my TWA?

If the Chrome URL bar appears when launching your Google Play PWA, Digital Asset Links verification has failed. Common causes include: returning a 301/302 redirect on the /.well-known/assetlinks.json endpoint, failing to return an explicit application/json Content-Type header, or listing an upload keystore fingerprint instead of Google's official Play Signing key.

Your app here

Looking for a simpler solution?

With Progressier, no need for a digital asset link file.

Generate PWA See plans