Skip to Content
Platform.Ontology

Browser flavor globals

Checks for window objects only certain browsers define (chrome, safari, __gCrWeb, opr).

Gets silentlyDevice detailsBrowser identityWeb browsersWhen the page loadsWhile you use it

In one line

Can tell which browser you really use, even when the label is changed

Checks for window objects only certain browsers define (chrome, safari, __gCrWeb, opr).

Identifies Chrome vs Edge vs Opera vs Safari vs in-app webviews even when the UA lies. FingerprintJS tests about 30 flavor names; spoofing tools often miss one.

What it can and can't do

What the user does: Nothing. It happens when the page loads

It can

  • Check for tell tale items that only Chrome, Edge, Opera, or Safari add
  • Spot in-app browsers inside other apps
  • Catch a browser that claims to be another one
  • Use the pattern as one more clue to tell you apart

It cannot

  • See your browser settings or add ons
  • Learn your identity from these checks alone
  • See your browsing history
  • Be fooled less often by tools that change only the label

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported122015-07-29None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported182012-06-27None
Samsung InternetSupported1.02013-04-27None

How a site asks for it

APIwindow.chrome, window.safari, window.opr, window.__gCrWeb, window.ApplePaySession ...
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnone needed (no grant)
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: object
How often: static per session

FieldTypeUnitRangePrecision
flavorslistNonesubset of about 30 known global namesNot listed

Technical limits

  • Only reveals browser family, not user

The story

What it is

Checks for special browser objects that only Chrome, Safari, Opera or in-app browsers define.

For you

You never see it. If you open a link inside the Instagram app, a site may know it is that kind of browser and show a nudge to open in Safari or Chrome instead. Its main effect is that the site can tell what really runs underneath.

For makers

A browser name in the user agent is easy to fake, but the hidden objects are harder to match. Fraud and bot teams use the mismatch to catch scrapers that lie. Developers use it to work around quirks in each browser engine and in app webviews.

Where you see it

TypeExampleApps
securityA bot defence service sees a client saying it is Chrome but missing the chrome object, and puts up a challenge.Cloudflare, DataDome
socialA site spots that you came from the Instagram or Facebook in-app browser and shows an Open in browser prompt.Instagram, Facebook
adsAn ad verification tool checks what kind of browser shows an ad so it counts the view correctly.None named
gamesA browser game portal detects an app webview where fullscreen or sound is flaky, and shows tips.None named
paymentsA checkout page picks the right wallet button, such as Apple Pay in Safari, when it knows the real engine.Apple Pay
developerAn error tracker adds the true browser engine to a crash report so developers can reproduce it.Sentry
bankingA bank's login flow raises a risk score when browser objects disagree with the user agent.None named

Risks

  • Hard to hide or fake
  • Adds to a device fingerprint

Good uses and abuse

Legitimate uses

  • Detect in-app browsers

Known abuse

  • Spoof detection
  • Bot detection

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits1.5Rough identifying entropy, when known

Sources

How well checked: Checked against real behavior.

On this page