Your files never leave your device. All processing happens locally in your browser.
What browser, version and operating system am I using, and how can I check it?
Open AnyTool What Is My Browser and it reads your browser instantly — no clicks needed. A prominent “You are using…” headline names your browser and version (for example Chrome 126), your rendering engine (Blink, Gecko or WebKit), your operating system (Windows 11, macOS, Android, iOS, Linux) and whether you are on a desktop, mobile or tablet. It derives these from a careful user-agent parser and, on Chromium browsers, upgrades them with navigator.userAgentData client hints, which are harder to spoof. Below the headline it shows your language(s), timezone and locale (from Intl), CPU cores, device memory, touch points, cookies, Do-Not-Track, live online status, screen and viewport size, the raw user-agent string (with copy), and a checklist of which web features your browser supports — WebGL/2, WebRTC, WebAssembly, Service Workers, WebGPU, Clipboard and more. Everything is detected in your browser with no network request, and a Copy report button gives you a clean read-out for tech support. Importantly, it does NOT show your IP address, because an IP can only be obtained by contacting a server.
“You are using…” headline: browser + version, rendering engine, OS and device type
Prefers navigator.userAgentData (Chromium client hints) over the spoofable user-agent string
Language(s), timezone/locale, CPU cores, memory, touch, cookies, Do-Not-Track, online status
Raw user-agent (copyable) plus a web-feature support checklist (WebGL, WebRTC, WASM, WebGPU…)
100% client-side — nothing uploaded; your IP is NOT shown because that would require a server
What is
What Is My Browser
A “what is my browser” tool reports the software and device you are browsing with. A client-side detector reads navigator (userAgent, languages, cookieEnabled, doNotTrack, hardwareConcurrency, deviceMemory, maxTouchPoints, onLine), navigator.userAgentData (Chromium client hints — brands, platform, mobile, and high-entropy values like platform version and architecture), window.screen, Intl (timezone and locale) and feature detection to derive your browser name and version, rendering engine, operating system, device type and supported web features. The user-agent string can be spoofed or “frozen” by UA reduction, so client hints are preferred when available. Because it makes no network request, it cannot and does not show your IP address or IP-based location, which only exist on the network and require a server.
Generators
Related terms
User agentnavigator.userAgentDataClient hintsRendering engine (Blink/Gecko/WebKit)Operating systemDevice typeUA reductionFeature detectionDo Not TrackTimezone
Frequently Asked Questions
No to both. It makes no network request, so it cannot see your IP address or location, and it never uploads anything — every value is read locally from your browser.
The tool is 100% client-side. It reads standard browser APIs — navigator (user agent, languages, hardware, cookies, Do-Not-Track, online status), navigator.userAgentData on Chromium browsers, window.screen, Intl for timezone and locale, and feature detection — entirely in your browser. It makes zero network requests, so nothing is uploaded, logged or stored, there is no server and no account, and we never see your details. Because of that it also cannot show your IP address or IP-based location: those exist only on the network and require contacting a server to look up, which this tool deliberately never does. Any website you visit can read these same browser signals, so the tool simply shows you what your browser already reveals — minus the IP.
It is best-effort. The user-agent string can be spoofed by extensions or settings and is deliberately frozen/reduced by modern browsers, so version and OS may be approximate. Client hints, when available, are more reliable.
Detection parses the navigator.userAgent string, which is only an advisory label: extensions, developer tools and privacy settings can change (spoof) it, and modern browsers intentionally freeze or simplify it — a policy called user-agent reduction — to limit fingerprinting, so the reported version or operating system can be approximate or generic. To improve accuracy the tool prefers navigator.userAgentData (User-Agent Client Hints) when the browser exposes it, because those structured values are harder to spoof and can include the precise platform version and CPU architecture. Client hints are Chromium-only, however — Firefox and Safari do not implement them — so on those browsers detection falls back to user-agent parsing. The tool tells you which source it used.
It is a structured, privacy-preserving alternative to the user-agent string available in Chromium browsers. It exposes brand/version, platform and mobile flag by default, plus high-entropy details like platform version and architecture on request.
navigator.userAgentData is the User-Agent Client Hints API. Instead of one long, easily-spoofed string, it provides discrete, structured fields: a list of browser brands and versions, the platform name, and whether the device is mobile, all available with low entropy by default. Higher-entropy details — the full platform version (useful for telling Windows 10 from Windows 11), CPU architecture and bitness, and the device model — are requested explicitly with getHighEntropyValues(), and the browser may withhold them for privacy. Because the values are structured and the browser controls what is shared, they are more reliable and harder to fake than parsing the raw user-agent. The catch is support: it is implemented only in Chromium-based browsers (Chrome, Edge, Opera, Samsung Internet, Brave), not Firefox or Safari, so it is used as an upgrade when present and the tool falls back to user-agent parsing otherwise.
It checks support for WebGL/2, WebRTC, WebAssembly, Service Workers, Web Workers, IndexedDB, localStorage, WebGPU, Clipboard, Notifications, Web Share and more, and a Copy report button puts a full plain-text read-out on your clipboard.
The tool feature-detects a checklist of web platform capabilities using simple typeof / “in” checks and a throwaway WebGL canvas: JavaScript, cookies, localStorage and sessionStorage, IndexedDB, Service Workers, Web Workers, WebAssembly, WebGL and WebGL 2 (plus the GPU renderer string when exposed), WebRTC, WebSockets, the Geolocation API, Notifications, the Clipboard API, Web Share, Touch Events, Speech Synthesis, WebGPU and Intl — each shown as supported or not. Copy report assembles everything — browser, engine, OS, device, languages, timezone, CPU cores, memory, touch, cookies, Do-Not-Track, online status, screen and viewport, the full user-agent and the feature list — into a clean plain-text block on your clipboard, ideal for pasting into a bug report or a message to a support team. The Copy buttons only write to your own clipboard.
Detailed Explanation
⚙️Methodology
How What Is My Browser Detects Your Browser, OS and Device
AnyTool What Is My Browser runs entirely on standard browser APIs — navigator, navigator.userAgentData, window.screen, Intl and feature detection — with no library, CDN, upload or server. A small, careful regex parser reads navigator.userAgent to derive the browser and version (handling Chrome, Edge, Firefox, Safari, Opera, Samsung Internet, Brave, Vivaldi and iOS variants in the right priority order, because Edge and Opera masquerade as Chrome), the rendering engine (Blink for Chromium, Gecko for Firefox, WebKit for Safari), the operating system (Windows version mapping, macOS, iOS, iPadOS, Android, ChromeOS, Linux) and the device type (desktop, mobile or tablet). On Chromium browsers it upgrades this with navigator.userAgentData: it reads the brand/version list and calls getHighEntropyValues() for platform version, architecture, bitness, model and full version, which are harder to spoof and can tell Windows 10 from Windows 11. The page shows a prominent “You are using…” headline, three primary readouts (browser, OS, engine) and a detail grid, and labels which source — client hints or the user-agent string — was used.
Reads navigator, navigator.userAgentData, window.screen, Intl — no upload, no server
Careful UA parser orders Edge/Opera/Samsung/Brave before Chrome to avoid mis-detection
Prefers Chromium client hints (getHighEntropyValues) over the spoofable user-agent
Derives browser + version, engine (Blink/Gecko/WebKit), OS and device type
Labels which source was used and updates online status and viewport live
📖How It Works
Every Signal It Surfaces
Beyond identity, the tool reports the signals your browser exposes: language and full language list (navigator.languages), timezone and locale from Intl.DateTimeFormat().resolvedOptions(), CPU cores (navigator.hardwareConcurrency), approximate device memory (navigator.deviceMemory, which is rounded and capped), touch points (navigator.maxTouchPoints), cookies enabled, Do-Not-Track, live online status (navigator.onLine, updated on the online/offline events), platform, and screen and viewport size with colour depth and device pixel ratio. It also shows the raw user-agent string with a copy button, the structured navigator.userAgentData brands and high-entropy hints as chips, and a web-feature support checklist built with typeof / “in” checks and a throwaway WebGL canvas: JavaScript, cookies, localStorage, sessionStorage, IndexedDB, Service Workers, Web Workers, WebAssembly, WebGL, WebGL 2, WebRTC, WebSockets, Geolocation, Notifications, Clipboard, Web Share, Touch Events, Speech Synthesis, WebGPU and Intl — plus the GPU renderer string when the browser exposes it. A Copy report button assembles all of this into a paste-ready plain-text block for tech support.
Languages, timezone/locale (Intl), CPU cores, device memory, touch points
Cookies, Do-Not-Track, live online status, platform, screen and viewport
Raw user-agent (copyable) plus userAgentData brands and high-entropy hint chips
Feature checklist: WebGL/2, WebRTC, WASM, Service Workers, WebGPU, Clipboard and more
Copy report builds a paste-ready plain-text read-out for bug reports
⚠️Limitations
Privacy, No IP, and Honest Limits
Because every value is read in your browser from navigator, navigator.userAgentData, window.screen, Intl and feature detection, your information is never transmitted, logged or stored — there is no server and no account, and Copy buttons only write to your own clipboard. Crucially, the tool makes zero network requests, so it cannot and does not show your IP address or IP-based location: those exist only on the network and require contacting a server to look up, which this tool deliberately never does — any site claiming to show “your IP” had to send your request to a backend. Be aware that any website you visit can read these same browser signals, so the tool simply reveals what your browser already discloses. Honestly, detection is best-effort: the user-agent string can be spoofed by extensions or settings and is deliberately frozen or reduced by modern browsers (user-agent reduction) for privacy, so the version or OS may be approximate or generic; navigator.userAgentData is Chromium-only, so Firefox and Safari fall back to user-agent parsing; and high-entropy hints and device memory can be withheld or rounded, so some fields may read “Hidden” on privacy-hardened browsers.
What Is My Browser: in-browser (AnyTool) vs typical online checkers
Capability
AnyTool
Typical online checkers
Detection source
Client hints preferred, UA fallback
Usually UA string only
Shows your IP
No — by design (needs a server)
Often yes (sent to a backend)
Rendering engine
Blink / Gecko / WebKit shown
Sometimes omitted
Web-feature checklist
WebGL/2, WebRTC, WASM, WebGPU…
Rarely shown
Client hints (userAgentData)
High-entropy values surfaced
Usually not used
Copy report
Paste-ready plain-text read-out
Varies
Privacy
Read in-browser, never uploaded
Often server-side
AnyTool reads navigator, navigator.userAgentData, window.screen and Intl entirely in your browser with no network request; detection is best-effort because the user-agent can be spoofed or frozen, and your IP is never shown because that would require a server.