Can You Detect OS
Can websites detect your OS?
Checking…
Simulates what a normal website can learn from your browser — not a stealth audit.
How to use
- Open the page on the operating system you want to test.
- Read the Yes headline, platform fields, and Client Hints rows.
- Refresh after an OS upgrade to see whether version tokens changed.
FAQ
Can websites detect my operating system?
Yes, in most browsers. OS name and often version appear in the user agent; Chromium may also send `platform` and `platformVersion` Client Hints to sites that request them.
Why is my OS version rounded or wrong?
Browsers increasingly reduce precision in version tokens for privacy. The label here reflects exposed values, not necessarily your exact build from System Settings.
Can I browse without revealing my OS?
Only partially. Privacy tools may genericize the UA, but some OS class usually remains for compatibility. Complete OS hiding is not realistic on the open web.
Linux vs Windows detection?
User agent and platform strings distinguish major families. Linux desktop UAs often include X11 or Wayland tokens; Windows includes Windows NT version segments.
Same as What Operating System Am I Using?
Similar fields: [what operating system am I using](/tools/what-operating-system-am-i-using) is user-facing; this page stresses site-detectability.
Is data sent to your servers?
OS detection runs locally from navigator APIs. No OS profile is stored on our side from this check alone.
Introduction
Can You Detect OS demonstrates that websites can usually identify your operating system family — Windows, macOS, Linux, Android, iOS — and often a version token, from data the browser exposes by default. The headline is typically Yes.
OS detection drives download links, compatibility messages, and security policies (“Windows 10+ required”). It also feeds analytics and fraud models when combined with browser and IP signals.
What websites can read
| Signal | Notes |
|---|---|
| User-Agent OS tokens | e.g. Windows NT 10.0, Mac OS X, Android 14 |
| navigator.platform | Legacy but still logged by some scripts |
| Client Hints platform | Structured platform name on Chromium |
| Client Hints platformVersion | OS version when provided |
| Device class pairing | iOS/Android tokens imply mobile OS families |
Safari, Firefox, and Chromium differ in how aggressively they trim version precision — compare before and after browser updates.
Why sites care about OS
- Correct installers — offer
.exe,.dmg, or.apkautomatically. - Feature gating — WebCodecs, WebGPU, and OS-integrated APIs vary by platform.
- Risk scoring — outdated OS versions may trigger warnings (heuristic, not proof of compromise).
Common use cases
- Download pages — confirm your site’s OS sniffing matches what users actually send.
- Internal apps — verify corporate “Windows only” banners fire correctly.
- Privacy review — see what leaks before enabling UA reduction features.
- Cross-browser QA — same OS, different browsers, compare platformVersion hints.
Best practices
- Do not treat OS detection as security proof — user agents are spoofable in automation contexts.
- Pair with can you detect browser for the full client stack picture.
- For CPU architecture (arm64 vs x86), see what CPU architecture am I using.
- For complete environment snapshot, open device info.