Browser Info

Browser info answers the question what is my browser by reading the navigator interface exposed by every modern web browser and listing the values that pages and analytics scripts can see about you. That includes the user agent string, the preferred language, whether cookies are enabled, the platform name, the Do Not Track signal, the CPU concurrency hint, and the maximum number of simultaneous touch points the device reports.

This Browser Info tool calls those navigator properties once when the page renders and shows them in a single scrollable table with a copy button on every row. Web developers, QA engineers, and support staff use it to confirm which browser and capabilities a user is actually running before debugging a UI bug, an analytics discrepancy, or a feature-detection fallback that misfires for one segment of traffic.

Why use Browser Info?

• Resolve “works on my machine” disputes fast. Confirm in one glance whether you and a teammate are on the same engine, version, and OS family.
• Audit fingerprinting surface area. Every value the tool shows is visible to any script on any site. The list makes the privacy trade-offs concrete.
• Verify localization defaults. navigator.language drives most auto-detect locale routines. Confirm the value before filing a translation bug.
• Confirm hardware hints for performance work. hardwareConcurrency is the logical CPU count that web workers and frame budgets key off.

How to use Browser Info

1. Load the page. The tool reads the navigator interface automatically.
2. Scan the table for the field you care about: User Agent, Language, Languages, Cookies Enabled, Online, Platform, Do Not Track, CPU Cores, and Touch Points.
3. Click the copy icon next to any value to put it on your clipboard for a bug report, a Slack thread, or a support ticket.
4. Switch browsers, toggle a privacy extension, or change a system setting, then reload to see how the reported values change.

What gets detected

Every value comes from a well-defined property on the global navigator object. The table maps each row in the UI to its navigator source so you can verify the same number anywhere else.

// What the page reads on load
const info = {
  ua: navigator.userAgent,
  language: navigator.language,
  cookies: navigator.cookieEnabled,
  cores: navigator.hardwareConcurrency,
};

All detection runs locally in your browser. The values are read once on render, kept in component state, and never sent to any server. Closing the tab clears them.

Common use cases

• Support engineers triaging user reports. Ask the customer to send their Browser Info output instead of guessing browser and OS from a screenshot.
• QA engineers reproducing locale bugs. Confirm the active language matches the locale that triggered the bug in production.
• Frontend developers debugging feature gates. Verify that a Chromium build with the right hardwareConcurrency is actually loading the heavier code path.
• Privacy-conscious users auditing browser hardening. See exactly which values an extension or privacy mode has changed.

Frequently asked questions

What is my browser and how can I tell?

Your browser is the application you used to open this page. The Browser Info tool reads navigator.userAgent and decodes the browser name, version, OS, and engine from it. You can also check About in the browser menu, but the navigator value is what any website sees.

How accurate is browser detection?

Most fields are accurate because the browser controls them directly. The user agent string can be spoofed by extensions and is increasingly frozen on Chrome for privacy. For mission-critical detection, prefer feature detection or navigator.userAgentData over parsing the UA string.

Is my data sent to a server?

No. Every value on the page comes from navigator properties that already exist in your browser. The tool reads them in JavaScript, renders them in the table, and exits when you close the tab. Nothing is transmitted, logged, or stored remotely.

Why does Do Not Track show “unset”?

Most browsers removed the DNT signal because few sites honored it and it added to fingerprinting entropy. If the field shows unset, your browser is no longer sending the header.

What does CPU Cores represent?

navigator.hardwareConcurrency is the number of logical processors the browser exposes to JavaScript. Chrome and Firefox cap or round the value for fingerprinting resistance.

Why is my platform value MacIntel on Apple Silicon?

navigator.platform is a legacy property browsers froze for fingerprinting reasons. The modern replacement is navigator.userAgentData.getHighEntropyValues(["architecture", "bitness"]).

Can a website see all of this without my permission?

Yes. Every value in the table is readable by any first-party JavaScript without a prompt. This is why the combination is treated as a passive fingerprint.

Related tools

• HAR Viewer: Open and inspect HTTP Archive files captured from DevTools.
• User-Agent Parser: Decode any user agent string into browser, OS, and engine.
• Browser Size: Live readout of viewport and screen dimensions.
• Local IP: Detect your local network IP via WebRTC.