Brave browser user agent
Brave is a privacy-focused Chromium browser that, by design, does not advertise itself in the user-agent string. It mirrors Chrome's user agent so sites cannot single Brave users out and to avoid breaking UA-sniffing sites. This page explains why Brave is hard to detect from the UA and why that is intentional.
Why Brave looks like Chrome
Brave is built on Chromium and deliberately presents a user agent that matches Chrome's. It does this for two reasons: compatibility, so UA-sniffing sites treat it as a known browser, and privacy, so a distinct Brave token cannot be used to single Brave users out for fingerprinting.
The practical result is that you usually cannot tell Brave from Chrome by the user agent alone, and that is by design rather than an accident.
- Chromium-based, presents a Chrome-like user agent
- Avoids a distinct token to reduce fingerprinting
- UA-based Brave detection is unreliable by design
Detection and the privacy boundary
Because Brave intentionally blends in, attempts to detect it from the user agent are unreliable, and chasing harder fingerprinting signals to unmask it works against the privacy goal Brave exists to serve.
The honest approach is to classify Brave as a Chromium browser and accept that the exact brand may be unknown. Do not invent a Brave attribution, and do not fingerprint visitors to force one. Confirm any UA specifics against Brave's documentation.
How it appears in analytics and logs
Brave traffic generally presents an ordinary Chrome user agent with no Brave token. Seeing no Brave marker is expected behaviour, not a spoof, because Brave intentionally blends in.
Diagnostic use case
Understand why Brave traffic typically looks like Chrome in logs, so you do not try to detect Brave from the user agent or treat its absence as anomalous.
What WebmasterID can help detect
WebmasterID classifies Brave as a Chromium browser from its Chrome-like pattern and does not invent a Brave attribution it cannot observe, keeping unidentifiable specifics honest.
Common mistakes
- Expecting a Brave token in the user agent and treating its absence as a spoof.
- Fingerprinting visitors to unmask Brave, defeating its privacy purpose.
- Reporting precise Brave share from the UA when it deliberately mimics Chrome.
Privacy and accuracy notes
Brave masks its identity in the user agent specifically to reduce fingerprinting. WebmasterID stores coarse browser categories and does not attempt to fingerprint or single out privacy browsers.
Related pages
- Chrome user agent and its quirks
Chrome's user-agent string is full of historical artefacts: it claims AppleWebKit and Safari for compatibility even though Chrome uses the Blink engine. Google has also reduced the detail Chrome exposes in the UA, moving fine-grained information into User-Agent Client Hints. This page explains the pattern and the quirks.
- User-Agent Client Hints
User-Agent Client Hints are HTTP headers (the Sec-CH-UA family) that let a site request specific browser, platform, and version detail rather than reading it all from one passive string. They underpin UA reduction: the raw user agent is shrinking, and finer detail moves to opt-in hints. This page explains the model.
- Privacy-first analytics
Analytics that rely on coarse categories, not fingerprintable detail.
Sources and verification notes
- Brave — Help Center and browser documentationBrave's privacy posture, including minimising fingerprintable signals.
- MDN — User-Agent header
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.