Skip to content

Trusted Web Activity availability

Published Updated

A Trusted Web Activity (TWA) lets an Android app open web content, such as a PWA, in a full-screen browser tab without browser UI. It uses a protocol based on Custom Tabs and is restricted to sites whose ownership the app proves through Digital Asset Links. The content is rendered by the user’s browser exactly as in the browser, and because browsers update independently of Android and of the app, the APK stays small and runs on a current web runtime.

Chrome’s documentation records TWA support on Android from version 72. This is the only support row; neither BCD nor caniuse has a TWA dataset. The same documentation notes that other browsers may implement the protocol but does not document any that do.

  • Legend
  • Yes
  • Partial
  • Flag
  • No
  • Unknown
Browser / PlatformSupportVersionsConfidenceSourceNotes
Chrome (Android)#Yes72mediumsource123
  1. Per Chrome's documentation, Trusted Web Activity is available in Chrome on Android from version 72.
  2. No cross-browser compatibility dataset (BCD/caniuse) covers TWA; version verified from Chrome's own documentation.
  3. The same documentation notes other browsers may implement the same protocol, but does not itself document TWA support in any other browser.

Source data: /compatibility/twa.json · Global usage: 66 % (StatCounter 2026-09, CC BY-SA 4.0)

Source: spec · Last verified 2026-09-09 · Confidence: medium (computed from sources)

When the activity launches, the browser verifies the Digital Asset Links statement at https://<site>/.well-known/assetlinks.json, which must name the app’s package and the SHA256 fingerprint of its signing certificate; no other file name or location is valid. If verification fails, the browser displays the site as a Custom Tab instead. A common cause of failure is a mismatched signing key, including the key Google Play may create when it manages app signing.

The host app does not have direct access to web content or web state such as cookies and localStorage; the two sides coordinate through URLs. A TWA follows the user’s default browser when it supports the protocol, then any installed browser that does, and otherwise falls back to a Custom Tab; adb logcat -v brief | grep -e TWAProviderPicker shows which browser was chosen.