{"id":1264,"date":"2026-05-30T17:00:00","date_gmt":"2026-05-30T22:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=1264"},"modified":"2026-03-07T04:45:44","modified_gmt":"2026-03-07T09:45:44","slug":"chrome-intent-urls","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/chrome-intent-urls\/","title":{"rendered":"Chrome intent:\/\/ URLs for Android Deep Linking"},"content":{"rendered":"\n

Chrome on Android supports a special URL scheme, intent:\/\/<\/code>, that lets web pages launch Android apps directly. Unlike custom URL schemes (which show an error if the app isn't installed) and unlike App Links (which require domain verification), intent URLs give you explicit control over what happens: which app to target, what data to pass, and where to send the user if the app isn't installed.<\/p>\n\n\n\n

Intent URLs are the most powerful deep linking mechanism available from web pages on Android, but they're also the most complex. This guide covers the syntax, common patterns, fallback behavior, and when to use intent URLs vs. the alternatives.<\/p>\n\n\n\n

For the App Links approach, see the Android App Links complete guide<\/a>. For how Custom Tabs interact with deep links, see the Chrome Custom Tabs guide<\/a>.<\/p>\n\n\n\n

The Intent URL Syntax<\/h2>\n\n\n\n
intent:\/\/\n    HOST\/PATH\n    #Intent;\n        scheme=SCHEME;\n        package=PACKAGE_NAME;\n        action=ACTION;\n        category=CATEGORY;\n        S.key=value;\n        S.anotherKey=anotherValue;\n        S.browser_fallback_url=ENCODED_URL;\n    end\n<\/code><\/pre>\n\n\n\n
A real example:<\/p>\n\n\n\n
intent:\/\/product\/abc123#Intent;scheme=https;package=com.example.app;S.browser_fallback_url=https%3A%2F%2Fexample.com%2Fproduct%2Fabc123;end\n<\/code><\/pre>\n\n\n\n
This tells Chrome:<\/p>\n\n\n\n
    \n
  1. Try to open https:\/\/product\/abc123<\/code> in the app com.example.app<\/code>.<\/li>\n
  2. If the app isn't installed, redirect to https:\/\/example.com\/product\/abc123<\/code>.<\/li>\n<\/ol>\n\n\n\n
    Syntax Breakdown<\/h3>\n\n\n\n
    \n\n\n\n\n\n\n\n\n\n
    Component<\/th>\nRequired<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
    intent:\/\/HOST\/PATH<\/code><\/td>\nYes<\/td>\nThe data URI (host and path)<\/td>\n<\/tr>\n
    scheme=<\/code><\/td>\nYes<\/td>\nThe URI scheme (usually https<\/code>)<\/td>\n<\/tr>\n
    package=<\/code><\/td>\nNo<\/td>\nTarget app's package name. Without this, any matching app can handle the intent.<\/td>\n<\/tr>\n
    action=<\/code><\/td>\nNo<\/td>\nThe intent action (default: android.intent.action.VIEW<\/code>)<\/td>\n<\/tr>\n
    category=<\/code><\/td>\nNo<\/td>\nAdditional category (default: android.intent.category.BROWSABLE<\/code>)<\/td>\n<\/tr>\n
    S.key=value<\/code><\/td>\nNo<\/td>\nString extras to pass to the app<\/td>\n<\/tr>\n
    S.browser_fallback_url=<\/code><\/td>\nNo<\/td>\nWhere to go if the app isn't installed<\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n
    String Extras<\/h3>\n\n\n\n
    Pass arbitrary data to the app using S.<\/code> prefixed key-value pairs:<\/p>\n\n\n\n
    intent:\/\/open#Intent;\n  scheme=myapp;\n  package=com.example.app;\n  S.referral_code=ABC123;\n  S.campaign=summer_sale;\n  S.source=email;\n  S.browser_fallback_url=https%3A%2F%2Fexample.com;\nend\n<\/code><\/pre>\n\n\n\n
    The app receives these as string extras in the launching intent:<\/p>\n\n\n\n
    override fun onCreate(savedInstanceState: Bundle?) {\n    super.onCreate(savedInstanceState)\n\n    val referralCode = intent.getStringExtra("referral_code") \/\/ "ABC123"\n    val campaign = intent.getStringExtra("campaign") \/\/ "summer_sale"\n    val source = intent.getStringExtra("source") \/\/ "email"\n}\n<\/code><\/pre>\n\n\n\n
    Fallback Behavior<\/h2>\n\n\n\n
    With S.browser_fallback_url<\/code><\/h3>\n\n\n\n
    If the target app isn't installed (or the package<\/code> doesn't match any installed app), Chrome navigates to the fallback URL. This is the most important parameter for a good user experience. For a detailed look at how different platforms handle missing-app scenarios, see Deep Link Fallback Behavior Across Platforms<\/a>.<\/p>\n\n\n\n
    intent:\/\/open#Intent;\n  scheme=myapp;\n  package=com.example.app;\n  S.browser_fallback_url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.example.app;\nend\n<\/code><\/pre>\n\n\n\n
    The fallback URL must be URL-encoded. Common fallback targets:<\/p>\n\n\n\n