What Operating System Am I Using?
Find out exactly which OS, version, and architecture your browser reports. Useful for debugging cross-platform issues, figuring out why a layout looks different on someone else's machine, or just settling a debate about which OS someone is actually running. Works in your browser — no installs, no setup.
Current Operating System Information
This tool shows what OS your browser reports about your device. No installation needed — it reads the same information any web page can access through standard browser APIs.
Operating System
Unknown OS
Which OS your browser is running on.Version
Unknown
The specific OS version or buildPlatform
The underlying platform identifier (Win32, MacIntel, Linux x86_64, etc.)Architecture
Unknown
Your CPU architecture — whether you're on 32-bit or 64-bit.OS Detector
This one's fairly simple in what it sets out to do: it tells you your operating system family — Windows, macOS, Linux, Android, iOS — along with whatever version and architecture details your browser is willing to expose about the underlying platform. You open the page, and the information is right there. No configuration, no setup, no waiting for anything to load.
The reason this exists as its own tool instead of just being folded into the browser detector is that OS-specific bugs are more common than most people assume, and they're a genuinely different category from browser bugs even though the two get lumped together casually in conversation. When someone reports a bug and says "Chrome," you still don't know whether they're on Windows, macOS, Linux, Android, or iOS. Each of those platforms handles fonts, input events, scroll behavior, system shortcuts, and rendering differently at the OS level, before the browser even gets involved.
Why OS matters even when you think it doesn't
A font renders a hair differently on Windows versus macOS because of how each system handles font smoothing. Windows uses ClearType, which optimizes for LCD subpixel rendering and produces sharper text at certain sizes. macOS uses a different smoothing algorithm that produces slightly heavier, more rounded letterforms. The difference is subtle enough that most people won't notice it on a single element, but it becomes visible in side-by-side comparisons, in screenshot-based design reviews, and in any layout where text rendering affects spacing or line breaking. If a customer sends you a screenshot and says "the text looks weird," knowing whether they're on Windows or macOS immediately narrows down whether it's a font smoothing issue or something else entirely.
A touch gesture behaves slightly differently on Android versus iOS because of how each platform interprets multi-touch events at the system level, before it ever reaches the browser. The rubber-banding effect when you scroll past the end of a page is different. The momentum and deceleration curves for fling gestures are different. The way the browser decides between a tap and a drag has different thresholds on different platforms. These aren't bugs in the browser — they're fundamental differences in how the two operating systems define "touch," and they affect how users perceive whether a gesture "worked" or felt responsive.
A keyboard shortcut that works fine on Windows might collide with a system-level shortcut on macOS. Cmd+Shift+T reopens a closed tab in Chrome on macOS, but on Windows the same action is Ctrl+Shift+T. More problematically, some browser shortcuts overlap with OS shortcuts in ways that only manifest on one platform — a developer testing on macOS might never discover that a shortcut they implemented conflicts with a Windows system shortcut until a Windows user reports that pressing it triggers something unexpected at the OS level before the browser ever sees the keypress.
Pairing it with the browser detector
On its own, the OS Detector tells you the platform. Paired with the Browser Detector, you get the full "browser + OS" combination that most cross-platform bug reports actually need to be genuinely useful, rather than half the picture. "Chrome on Windows 11" is a fundamentally different environment than "Chrome on macOS Sonoma," even though both report the same browser name and version. The font rendering is different. The window management is different. The system-level integrations are different. The way the OS handles window resizing, multi-monitor setups, and display scaling are all different. A bug that appears in one combination might be completely absent in the other, and knowing both values tells you whether you're looking at a browser issue, an OS issue, or an interaction between the two.
This is particularly useful for QA teams testing across environments. If a tester reports a layout shift that only happens on Windows with Firefox, you know to check the Gecko rendering engine's behavior on Windows-specific font rendering. If it happens on Android with Chrome, you know to check how Blink handles touch events and viewport scaling on Android. The combination of browser and OS narrows down the search space for the root cause faster than either value alone.
What you'll actually see
The tool reports the operating system family — Windows, macOS, Linux, Android, or iOS — along with version and architecture details where the browser exposes them. On desktop, this usually includes the specific OS version (Windows 11, macOS 14.3, Ubuntu 22.04) and sometimes the architecture (x86, x64, ARM). On mobile, you typically get the OS family and a general version range rather than an exact point release.
The output is formatted for quick reading, designed to be the kind of information you'd paste into a bug report or a GitHub issue. No hunting through settings menus, no asking the user "what OS are you on," no guessing based on screenshots that might be too blurry to read the taskbar or menu bar details.
A limit that's worth knowing up front
Browsers don't hand over a full, precise OS version string the way a native application installed directly on the system could — that's an intentional privacy boundary built into the browser itself, not a shortcoming of this particular tool. When the browser only exposes a general platform family rather than an exact build number (like a specific Windows or Android point release), that's exactly what gets shown here — no guessing, no filling in blanks with something that sounds specific but isn't actually verified.
This is a privacy decision made at the browser level, and it's been tightening over the past few years. Chrome, Firefox, and Safari have all progressively reduced the amount of OS detail they expose in user-agent strings and platform detection APIs. The reasoning is straightforward: the more precise the OS information a browser reveals, the easier it is for advertisers and trackers to fingerprint individual users based on their specific combination of browser, OS, version, and hardware. By limiting what's exposed, browsers make fingerprinting harder at the cost of making debugging slightly less convenient.
This matters especially on mobile, where a lot of Android and iOS versions get grouped together at the browser level for privacy reasons, even though the actual devices in question might be running quite different OS builds under the hood. An Android phone running Android 13 and one running Android 14 might both report the same general platform family at the browser level, even though the underlying system APIs, permission models, and rendering behaviors differ between those versions. The OS Detector shows you what the browser is willing to reveal, which is the most accurate information available from a web page's perspective.
For situations where you need the exact OS version — which is occasionally necessary for native debugging or system-level diagnostics — the operating system's own settings menu or system information panel will always be more precise than anything a browser can report. The OS Detector is designed for the common case: quick identification of the platform and general version, enough to triage most browser-level issues without asking the user to dig through settings menus.
Last updated: May 2026 | DevNestTools