What you enter stays on your device while you use this tool. Opening a shared link sends the settings in its address to HowToolbox to prepare the page.
This page downloads public data; editing the fields does not send your input.
Reported browser
Identity details
- Reported engine
- Not reported
- Reported operating system
- Not reported
- Device type
- Unknown device
Loading…
These device facts stay on this page. No permissions are requested. Reload to take a new snapshot.
More browser and device details
Vendor release data
Vendor release data
This compares reported versions with vendor releases, not security fixes or vehicle update eligibility. ESR and staged rollouts may differ.
Reported values can be rounded, hidden or spoofed. API presence does not promise permission or successful use.
Find the reported browser, engine and operating system.
How to use
- Open this page in the browser you want to identify.
- Read the browser name and version at the top, then the engine and operating system under it.
- If it says Chromium, look at the details: many Chromium browsers only show their own name when they share client hints.
How sample user-agent strings are read
| Sample from | Read as | Version | Engine |
|---|---|---|---|
| Chrome, Windows (user agent only) | Chromium | 100.0.0.0 | Blink |
| Chrome, Windows (with client hints) | Google Chrome | 100.0.1000.10 | Blink |
| Edge, Windows | Microsoft Edge | 100.0.1000.10 | Blink |
| Firefox, Windows | Firefox | 100.0 | Gecko |
| Safari, macOS | Safari | 16.0 | WebKit |
| Chrome, iPhone | Google Chrome | 100.0.1000.10 | WebKit |
Illustrative strings with invented version numbers, read with the page's own rules. A reduced version ends in .0.0.0.
How it works
A web page cannot ask a browser what it is. It reads what the browser chooses to report: a user-agent string and, in Chromium browsers, a set of client hints. This page reads both and picks the most specific name it can support. The table shows how the same rules read six typical identities.
Two things surprise people. Chrome's string contains the words Mozilla, Gecko and Safari, left over from older compatibility habits, so they say nothing about the brand. And a plain Chrome string looks the same as the string of many other Chromium browsers, so on its own it is read as Chromium; the brand appears in a name token such as Edg or in the client hints.
The engine is the part that draws the page: Blink in Chrome, Edge and other Chromium browsers, Gecko in Firefox and WebKit in Safari. Chrome and Firefox on an iPhone report WebKit too, because they are built on Apple's engine there.
Worked example
How is a plain Chrome user-agent string read?
- The string names Chromium 100.0.0.0 but no brand, so it is read as Chromium, with the Blink engine.
- If the browser also shares client hints, the brand is known: Google Chrome 100.0.1000.10.
Chromium without client hints, Google Chrome with them.
Frequently asked questions
Is Chrome the same as Chromium?
Chromium is the base used by Chrome and many other browsers. Product versions can differ from the engine version.
Can this identify Brave?
A positive Brave signal identifies the brand. Brave may still conceal its own product version.
Are browser names guaranteed?
No. Compatibility settings, privacy tools and overrides can change the reported name.
Do all iPhone browsers use WebKit?
Many report WebKit, but alternative engines are permitted in some regions. This page uses reported engine evidence, not a universal rule.





