"Deep link", "App Link" and "Universal Link" are often used as if they meant the same thing. They describe different mechanisms. This guide uses Google's and Apple's own definitions.

Short version

A deep link is any link that opens specific content in an app. An Android App Link and an iOS Universal Link are HTTPS deep links that the operating system has verified against a file on your website, so they open your app without asking the user to pick an app. A custom scheme such as myapp:// is also a deep link, but it is never verified.

Deep links

Google describes deep linking as "a standard Android platform capability that takes advantage of the intents system to route deep links to your app", covering "several types of deep links, from custom URIs to standard web schemes and domains." There are two kinds of address:

  • Custom URI schemes, such as myapp://product/42. Only your app handles them. If the app is not installed, nothing can open the link and there is no website to fall back to.
  • Web URLs, such as https://example.com/product/42. The same URL can open your app on a phone and your website elsewhere.

Google notes that unverified deep links "are subject to the system disambiguation dialog", the chooser Android shows when more than one app can open a link.

Android App Links

Google defines App Links as "an enhanced deep linking capability that verifies deep links to your own website". Once verified, links "immediately open corresponding content in your app, without requiring the user to select your app from a disambiguation dialog." App Links work on Android 6 and higher on devices with Google services. Google recommends them for deep links to your own website. They need three things:

  • An http or https URL. The intent filter declares android:scheme="https", and can declare http as well.
  • An intent filter that requests verification. It has android:autoVerify="true", the android.intent.action.VIEW action, and the DEFAULT and BROWSABLE categories.
  • A Digital Asset Links file. You host https://example.com/.well-known/assetlinks.json with your package name and signing certificate fingerprint. Android checks it when the app is installed, and on Android 15 and higher it also checks again periodically.

If any of these is wrong, the link opens in the browser. See why your App Link opens the browser.

iOS Universal Links

Universal Links are Apple's version: an HTTPS URL that opens your app, backed by a file on your website. They need two things:

  • The Associated Domains entitlement, with an entry for each domain in the form applinks:example.com.
  • The apple-app-site-association file, with no file extension, at https://example.com/.well-known/apple-app-site-association. Apple requires HTTPS with a valid certificate and no redirects. The applinks section lists your app IDs (team ID plus bundle ID) in appIDs, and the URL patterns in components.

Since iOS 14, devices do not fetch the file from your server. They get it from Apple's CDN. Apple says the CDN requests the file within 24 hours, and devices check for updates about once a week after the app is installed. During development, if your server is not reachable from the public internet, the entitlement's alternate mode lets the device bypass the CDN.

Side by side

  • Custom URI scheme (myapp://). Registered in the intent filter on Android and under URL Types in Xcode on iOS. No verification and no web fallback.
  • Android App Link (verified https). autoVerify intent filter plus assetlinks.json.
  • iOS Universal Link (verified https). Associated Domains entitlement plus apple-app-site-association.

Which one to use

For links to your own website, Google recommends App Links. Apple says that "while custom URL schemes are an acceptable form of deep linking, universal links are strongly recommended." Both need a domain you control and a file served exactly as specified. Custom schemes remain an option where an HTTPS URL does not fit.

Test on a device

Generate a link or QR code with the Deep Link Tester and open it on the device. On Android you can also send the intent from a terminal, as described in the adb testing guide.

Keep reading

Official docs


Last updated · November 2026