Can You Detect Browser
Can websites detect your browser?
Checking…
Simulates what a normal website can learn from your browser — not a stealth audit.
How to use
- Open the page in the browser you want to test — detection runs automatically.
- Read the Yes headline, methods list, and signal bullets under What sites can see.
- Copy the user agent or click Refresh after switching browsers or profiles.
FAQ
Can websites detect my browser?
Yes, in normal browsing. Every HTTP request can carry a User-Agent string, and Chromium browsers may also send User-Agent Client Hints. This page shows the same fields a server-side parser would receive.
Can I hide my browser from websites?
Not completely without extensions, privacy browsers, or a modified client. Even reduced user agents still reveal a browser family. Treat complete invisibility as unrealistic for typical sites.
Why does the headline say Yes?
Because browser name and version are intentionally exposed for compatibility. The tool frames that as site-detectable — not as a vulnerability by itself.
Is this different from What Is My Browser?
Same underlying data, different purpose: [what is my browser](/tools/what-is-my-browser) shows your browser for support; this page explains that websites can detect those same values.
Do sites see my exact build number?
Often yes, but some browsers freeze or round version tokens for privacy. What you see here is what your browser exposes to JavaScript and typical requests.
Is data uploaded?
Browser detection runs locally in your tab. Only the user agent and Client Hints available to JavaScript on this page are shown — nothing is stored about you.
Introduction
Can You Detect Browser answers a question site owners and privacy-conscious users both ask: can a normal website learn which browser I use? The headline is almost always Yes — browsers advertise name, version, and engine through the User-Agent string and, on Chromium, User-Agent Client Hints.
Developers use that surface for analytics, compatibility gates, and fraud checks. Visitors use this page to see the same signals without reading raw HTTP headers — useful before filing a bug, testing a paywall, or comparing privacy settings.
What websites can read
| Signal | What it reveals |
|---|---|
| User-Agent | Browser family, version, OS tokens, and compatibility cruft |
| Client Hints | Structured Sec-CH-UA* values when the browser sends them |
| Engine tokens | Blink, WebKit, or Gecko identifiers embedded in the UA |
| JavaScript APIs | navigator.userAgent matches what many scripts log client-side |
Server-side parsers (like our user agent parser) consume the same strings. This demo runs entirely in your browser so you see the client-visible slice.
Yes vs No on this page
Yes means “sites can identify your browser with standard signals.” It does not mean every site actively logs or blocks you. No would only appear if those APIs were unavailable — rare in modern desktop and mobile browsers.
Privacy-focused browsers may send reduced or generic user agents; you still usually leak a coarse browser class.
Common use cases
- Product and QA — confirm your site’s browser gate sees Chrome 120+ the way you expect.
- Support — show a user what their browser reports before asking them to update.
- Privacy review — compare normal vs hardening profiles side by side.
- Education — explain why “private browsing” does not hide browser identity from websites.
Best practices
- Test in the same profile and window where you see a site bug — extensions rarely change UA but can affect Client Hints on some setups.
- Pair with what is my user agent for a parsed breakdown and can you detect OS for the OS slice sites combine with browser data.
- For automation detection (bots, headless Chrome), use can you detect bot — a different signal set than everyday browser identification.