To find out what browser you are using on an Android phone, open the browser you are currently using and check its reported brand; if it says “Browser name not exposed,” the browser has not provided a meaningful name to that page.

An Android phone can have several browser apps installed, and a page can also run inside an in-app web view. The What Browser Am I Using tool addresses the browser currently rendering the page: it displays identity and environment fields supplied by that browser, reading them locally after the page loads.

what browser am i using on my android phone
What Browser Am I Using on My Android Phone?

Installed, default, and current browsers are different

The question “what browser am I using on my Android phone” can refer to three separate things. Knowing the installed apps does not establish which one handled a particular page, and the default browser is not necessarily used for every link.

  • Installed browser: A browser app is present on the phone. Android’s app drawer or installed-app list can show its application name.
  • Default browser: Android has selected one browser to handle ordinary web links unless another app is chosen.
  • Current browser: This is the browser or web-view context that actually loaded the page you are viewing.

A link opened inside a messaging, social, shopping, or email app may use that app’s embedded web view instead of the standalone browser. That is why an installed-app list alone cannot answer every version of the question.

Check the browser open on your Android phone

  1. Open the browser you want to identify. Load the site you want to examine in that browser. If the content originally appeared inside another app, use that app’s external-browser option when available, then repeat the check there.
  2. Load What Browser Am I Using in the same browser. After the page loads, it reads the available identity and environment fields locally. The widget does not upload them, fingerprint them into a server record, or persist them.
  3. Read the reported brand list first. When the browser provides User-Agent Client Hints brands, the tool shows the reported brand and version pairs. It removes the intentionally meaningless “Not A Brand” placeholder while preserving the remaining pairs in the order supplied.
  4. Compare the supporting fields. Review the reported platform, mobile hint, language, general cookie setting, and complete raw user-agent compatibility string. Each answers a different question, so avoid treating one field as proof of all the others.
  5. Copy the browser report when needed. Select “Copy browser report” to export the same visible values as plain text. Clipboard access occurs only after you select that control.

Keep the browser under investigation unchanged between the check and the troubleshooting session. A report opened in Chrome, for example, should not be used to explain a page that was actually rendered inside a separate Android app.

Read each field in the Android report

The report is most useful when its fields are interpreted separately. The table below shows what each visible value represents and the conclusions it cannot support.

Report field What the tool displays What it cannot establish
Reported brands Brand and version pairs exposed through the browser’s Client Hints interface, with the meaningless placeholder removed. The exact installed application, executable signature, update channel, security patch level, or support for a particular feature.
Platform The Client Hints platform when available, otherwise the browser’s reported navigator.platform value. The exact phone model, the physical device, or proof that the page is running on Android.
Mobile hint A mobile boolean only when the Client Hints interface supplies one. Screen size, touch capability, device model, or proof that a browser is running on a phone.
Language The browser’s reported navigator.language value. Physical location, content preferences, keyboard layout, or account language.
Cookie setting The browser’s general reported state through navigator.cookieEnabled. That every cookie write will succeed or that third-party tracking is available.
Raw user agent The complete navigator.userAgent compatibility string. Authenticated identity, an unmodified installed app, or an exact product decision.

The platform fallback and Client Hints values can be reduced, frozen, legacy-formatted, or selected for compatibility. Likewise, a general cookies-enabled result can still be affected by third-party restrictions, partitioning, storage-access rules, private mode, expiration, domain and path rules, consent choices, extensions, and enterprise controls. The page does not create a test cookie or infer tracking availability.

Why the browser name may not be exposed

“Browser name not exposed” is a deliberate result, not a failed check. It appears when the browser does not provide meaningful Client Hints brands, either because the interface is absent or because no useful brand remains after the placeholder-like entry is removed. Browsers may also include a GREASE placeholder designed to prevent code from assuming a fixed brand list or order.

The raw user-agent string is preserved separately and should remain an opaque compatibility value. Traditional strings often contain historical tokens and several browser names at once. A Chrome-family string, for example, can mention Mozilla, AppleWebKit, Chrome, Safari, and other names without meaning that five separate products are running.

For that reason, the tool does not maintain a large user-agent pattern table or claim an exact product from token order. Mapping such strings confidently requires a maintained parser and can still be defeated by reduction, spoofing, embedding, or privacy settings. Automation, web views, privacy tools, proxies, extensions, developer overrides, and remote browser services can also change the reported values. Do not select a browser name merely because one familiar token appears in the string.

Verify installed and default apps in Android Settings

Use Android’s own interface when you need the application name rather than the browser-reported identity.

  1. Check the foreground app. Open Android’s recent-apps view and inspect the current card. A browser application name identifies the standalone app handling the page. If the card belongs to another app, the content may be inside its embedded web view.
  2. Review installed applications. Open Settings, choose Apps, and select “See all apps,” or inspect the app drawer. Menu labels vary by phone maker. This reveals browser apps installed on the phone but does not prove that one of them loaded the current page.
  3. Check the default browser. In Settings, look for Apps, Default apps, and then the browser category. The exact labels vary by Android version and manufacturer. This setting identifies the system’s default handler, not necessarily the app used by a particular in-app link.
  4. Repeat the browser-reported check in the relevant context. If the problem appears only inside an embedded web view, compare its behavior with the same page opened in a standalone browser and record that distinction in your reproduction notes.

These checks complement rather than replace one another: Android can identify installed application names, while the browser report shows what the current page’s browser context chooses to expose.

Capture a useful Android troubleshooting report

  1. Reproduce the problem in the browser context that matters. Note the failing URL, the time, and the exact actions that trigger the issue.
  2. Select “Copy browser report.” The copied plain text contains the same visible brand, platform, mobile, language, cookie, and raw user-agent values shown on the page.
  3. Attach the surrounding evidence. Include the failing URL, time, reproduction steps, screenshots, extension state, and whether private mode changes the behavior.
  4. Record the app context. State whether the page was opened in a standalone browser or an in-app web view, and include the relevant app name if that distinction affects the issue.
  5. Present the report as diagnostic data. Support staff can compare the visible browser-supplied fields, but the report is not authenticated identity and does not prove which executable is installed.

The report is read locally after the page loads, and the widget does not create a server-side fingerprint record. Selecting the copy control is the point at which the report is placed on your clipboard, so review that text before pasting it into a support ticket or chat.

Know what the result does not prove

A reported brand or complete compatibility string cannot prove the installed application, executable signature, update channel, security patch level, device owner, or whether the value has been modified. It also does not establish that a browser supports a particular website feature or security state.

If an exact supported-browser decision matters, test for the required Web API with feature detection and consult the browser product’s own About or update screen. Use the copied report to explain the environment around a reproducible issue, not as proof of a browser’s full identity or security posture.

If you're weighing options, Screen Light on Android: Make a Browser Fill Light covers this in detail.

If you're weighing options, What Browser Am I Using on My iPad? Read the Report covers this in detail.