Skip to content
Lizely

What Browser Am I Using

See the browser brands, platform, mobile hint, language, cookie setting, and raw user-agent string that this browser chooses to expose.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Review the reported brand list and note when the page honestly says the browser name is not exposed.
  2. 2.Compare platform, mobile hint, language, cookie setting, and the raw compatibility user-agent string.
  3. 3.Select Copy browser report and attach it with reproduction steps when troubleshooting, without treating it as authenticated identity.

About What Browser Am I Using

What Browser Am I Using displays identity and environment fields supplied by the current browser. When User-Agent Client Hints exposes a brand list, the page shows the reported brands and major versions after removing the intentionally meaningless Not A Brand placeholder. It also shows the reported platform, mobile hint, language, whether the browser says cookies are enabled, and the complete navigator.userAgent compatibility string. Copy browser report exports those same visible values as plain text.

The page deliberately does not maintain a large user-agent pattern table. Traditional user-agent strings often include historical compatibility tokens and several browser names at once. A Chrome-family string can mention Mozilla, AppleWebKit, Chrome, Safari, and other tokens without meaning that five separate products are running. Mapping those strings to a confident product and exact version requires a maintained parser and can still be defeated by reduction, spoofing, embedding, or privacy settings.

Reported brands come from navigator.userAgentData.brands when the browser implements that interface. Browsers may include a GREASE placeholder designed to prevent code from assuming a fixed brand list or order. The widget filters only that placeholder-like name and preserves the remaining brand/version pairs in the order provided. When the interface is absent or no meaningful brands remain, it says Browser name not exposed rather than inventing a result from brittle token order.

Platform uses the client-hint platform when available and otherwise displays navigator.platform. Both values can be reduced, legacy-formatted, frozen, or chosen for compatibility. Mobile hint is shown only when the client-hint interface supplies a boolean. It is not a screen-size guess, device model, touch-capability test, or proof that the browser runs on a phone. Language comes from navigator.language and may differ from content preferences, physical location, keyboard layout, or account settings.

Cookies enabled reflects navigator.cookieEnabled. It indicates the browser's general reported setting, not that every cookie write will succeed. Third-party cookie restrictions, partitioning, storage access policy, private mode, expiration, domain and path rules, consent choices, extensions, and enterprise controls can still block a specific cookie. This page does not create a test cookie or infer tracking availability.

The raw user-agent value is preserved because support teams and bug reports often request it. Treat it as an opaque compatibility string, not authenticated identity. Automation, webviews, privacy tools, proxies, extensions, developer overrides, and remote browser services can change it. The report cannot prove the installed application, executable signature, update channel, security patch level, device owner, or whether the string has been modified.

Use the copied report when reproducing a website issue, then add the failing URL, time, steps, screenshots, extension state, and whether private mode changes the behavior. If an exact supported-browser decision matters, use feature detection for the required Web API and consult the product's own About or update screen. A reported brand alone does not demonstrate support for a particular feature or security state.

All fields are read locally after the page loads. Nothing is uploaded, fingerprinted into a server record, or persisted by this widget. Clipboard access happens only after selecting Copy browser report. The reliable contract is narrow: show browser-supplied fields transparently, remove only the known meaningless brand placeholder, preserve raw values, and use an honest fallback when a product name is not exposed.

Methodology & sources

Read navigator.userAgentData brands/platform/mobile when available, fall back to navigator.platform only for the platform label, and always preserve navigator.userAgent, language, and cookieEnabled. Remove empty brand names and the GREASE-style Not A Brand placeholder without parsing the legacy user-agent into a claimed product. Tests assert placeholder filtering, multiple reported brands, no-brand fallback, platform, cookie status, and raw user-agent copy text.

Frequently asked questions

Why can the user-agent string contain several browser names?
It is a compatibility string with historical tokens. Those tokens are not a reliable list of installed or running browsers.
Why does the page sometimes say Browser name not exposed?
Some browsers do not provide meaningful Client Hint brands. The tool avoids guessing a product from a brittle user-agent pattern table.
Does Cookies enabled prove a website can store every cookie?
No. Third-party restrictions, partitioning, private mode, consent, domain rules, extensions, and policy can still block a particular cookie.

Related tools

Device & Productivity guides

View all