On a Mac, open What Browser Am I Using in the browser you want to identify to see the brand and major version that browser reports.
The page reads the current browser’s reported fields locally after it loads. If the browser does not expose a meaningful brand, the result is “Browser name not exposed” instead of a guess based on the user-agent string.
Check the browser open on your Mac
Mac can have several browser applications installed, and a link opened from another app may be handled by the default browser. To check a particular browser, run the test inside that browser’s own window.
- Open the browser you want to identify. Use its normal window rather than relying on the name of a website tab or the icon of another Mac app.
- Navigate directly to What Browser Am I Using. Type or paste its address into that browser’s address bar instead of opening it through a link that macOS could pass to your default browser.
- Read the reported brands first. When meaningful Client Hint brands are available, the page shows their names and major versions after removing the intentionally meaningless “Not A Brand” placeholder. The remaining brand and version pairs stay in the order supplied by the browser.
- Compare the supporting fields. Review the platform, mobile hint, language, cookies setting, and complete raw user-agent string. These provide context, but they do not turn the report into authenticated identity.
- Copy the report if needed. Select “Copy browser report” when you need the exact visible values for a support request, issue report, or troubleshooting note.
If the brand section says “Browser name not exposed,” the browser supplied no meaningful brand list. That outcome is more reliable than declaring a browser from the order of words in a legacy user-agent string.
Read the Mac browser report field by field
Each field answers a different question. Reading them together gives a useful snapshot of the browser-reported environment without pretending that every field proves the same thing.
| Field | What the report shows | Important limit on Mac |
|---|---|---|
| Reported brands | Browser-supplied brand names and major versions from navigator.userAgentData.brands, when that interface is implemented. | The list can contain several brands. It describes what the browser advertises, not every browser installed on the Mac. |
| Platform | The Client Hint platform when available; otherwise, navigator.platform. | Either value can be reduced, legacy-formatted, frozen, or selected for compatibility, so it is not authenticated device information. |
| Mobile hint | A boolean only when the Client Hint interface supplies one. | It is not a screen-size estimate, touch-capability test, device model, or proof that the browser runs on a phone. |
| Language | The browser-reported value from navigator.language. | It may differ from content preferences, physical location, keyboard layout, or account settings. |
| Cookies enabled | The general setting reported by navigator.cookieEnabled. | A specific cookie can still be blocked by private mode, consent choices, partitioning, domain rules, extensions, or enterprise controls. |
| Raw user-agent | The complete navigator.userAgent compatibility string. | It is an opaque value that can be changed by extensions, automation, privacy tools, proxies, developer overrides, and other browser settings. |
Why the user-agent string mentions several browsers
A traditional user-agent string often contains historical compatibility tokens. A Chrome-family string can mention Mozilla, AppleWebKit, Chrome, Safari, and other names even though those tokens do not mean that several separate products are running.
The tool deliberately avoids maintaining a large user-agent pattern table. Mapping an old string to one confident product and exact version requires a maintained parser, and even that approach can be defeated by browser reduction, spoofing, embedding, or privacy settings. Client Hint brands provide a more direct reported list, but they remain browser-supplied information rather than proof of an installed application.
The page also preserves the browser’s original brand order after removing only the known meaningless placeholder. That GREASE-style placeholder is designed to prevent code from assuming that brands will always appear in a fixed order. If no meaningful brands remain, the honest fallback is “Browser name not exposed.” The broader distinction between advertised identity and authenticated identity is covered in What Browser Am I Using Explained: Honest Detection Limits.
Know what the Mac report proves
Use the report as a set of browser-supplied facts, not as a forensic inventory of the Mac.
| Question | What the report supports | What it does not establish |
|---|---|---|
| Which browser brand is exposed? | The brand names and major versions the current browser reports. | The exact installed executable, full build number, update channel, or security patch level. |
| Which browser opened the page? | The browser environment that supplied the report for the current tab. | The Mac’s default browser or the presence of other browser applications. |
| Is the browser running on a phone? | A browser-supplied mobile boolean when one is available. | The physical device, screen dimensions, touch support, or the user’s location. |
| Will a website cookie work? | The browser’s general reported cookies-enabled setting. | That every cookie can be written, read, retained, or used for tracking. |
| Is the reported browser secure or compatible? | A brand and major version advertised by the browser. | Support for a particular web feature, a security state, or the identity of the device owner. |
Confirm the result when the label is not enough
For the everyday question “What browser am I using on Mac?”, the exposed brand list is the most useful part of the report. If an exact supported-browser decision matters, do not rely on that label alone.
- Check the required web capability directly. Use feature detection for the specific Web API the site needs instead of assuming every browser with the same brand supports it.
- Check the browser’s own version screen. Consult the application’s About or update interface when you need the exact installed version.
- Run the page in the relevant browser. The report describes the browser supplying the page’s fields, not every browser installed on the computer.
- Keep the fallback intact. When the browser name is not exposed, retain that wording and use the raw compatibility string for diagnosis rather than inventing a product name.
Create a useful browser report for troubleshooting
A copied report is most valuable when it accompanies a reproducible website issue rather than standing on its own.
- Reproduce the problem first. Note the failing URL, the time, the exact steps, and whether the issue occurs in a normal or private window.
- Select “Copy browser report.” The control exports the same visible values as plain text, including the reported brands, platform, mobile hint, language, cookies setting, and raw user-agent string.
- Attach the report to the issue. Add the failing URL, time, reproduction steps, screenshots, relevant extension state, and whether private mode changes the behavior.
- Label it as diagnostic information. Describe it as a browser-reported snapshot, not as authenticated identity or proof of what application is installed.
All fields are read locally after the page loads. The widget does not upload them, fingerprint them into a server record, or persist them. Clipboard access occurs only after you select the copy control; once copied, the report remains in your clipboard until replaced or cleared, so paste it only where you intend.
Avoid common Mac browser-report misreads
- Safari in the user-agent does not automatically mean Safari is active. Compatibility strings can preserve old tokens across several browser families.
- “Browser name not exposed” does not mean there is no browser. It means the browser did not provide a meaningful Client Hint brand list for the page to display.
- An omitted mobile hint is not a desktop verdict. The field appears only when the Client Hint interface supplies the boolean.
- “Cookies enabled” is not a promise about every cookie. Storage access, partitioning, consent, private mode, expiration, and policy controls still apply.
- A Mac platform label is not a complete device check. Browser-reported platform values can reflect compatibility choices rather than authenticated hardware information.
The practical answer is the browser brand and major version exposed for the Mac browser tab running the check, with an honest fallback when no meaningful brand is available. Treat the raw user-agent as compatibility evidence, not as authenticated proof.