What CPU Architecture Am I Using
CPU architecture
Detecting…
Architecture from Client Hints when available; otherwise inferred from user agent. Not a full CPU model name.
How to use
- Open the page — your CPU architecture appears at the top when your browser exposes it.
- Read architecture, bitness, and logical core count in the Details card.
- Click Copy to save the architecture label for a download or support ticket.
FAQ
What CPU architecture am I using?
The headline shows values like x86_64 (64-bit) or arm64 (64-bit) when User-Agent Client Hints or user agent inference can determine them. This is the instruction set family, not the retail CPU name (for example Intel Core i7).
What is the difference between x86_64 and arm64?
x86_64 is the 64-bit Intel/AMD PC architecture. arm64 (AArch64) is the 64-bit ARM architecture used on Apple Silicon Macs, most phones, and many newer Windows ARM laptops. Software builds are often separate for each.
Why does it say inferred from user agent?
Firefox and some privacy modes do not expose high-entropy Client Hints. The page falls back to parsing tokens like Win64, x64, or arm64 from the user agent string — less precise but still useful.
Is this my exact CPU model?
No. This page reports architecture and bitness, not whether you have an M2, Ryzen 7, or Snapdragon chip. Check your system About screen or specs for the marketing model.
What are logical CPU cores?
navigator.hardwareConcurrency reports how many threads the browser will use for parallel work. It is a hint, not a full spec sheet — physical cores and hyper-threading can differ by OS reporting.
Is any data sent to a server?
No. Values are read from browser APIs locally.
Introduction
What CPU Architecture Am I Using shows the instruction-set family your browser reports — x86_64, arm64, 32-bit vs 64-bit, and how many logical CPU cores are visible — so you pick the right native build or understand emulator and Rosetta scenarios.
Download pages often offer "x64", "ARM64", or "Apple Silicon" builds. This page answers which bucket your browser session falls into, using the same Client Hints and user agent signals developers rely on.
Common architecture labels
| Label | Typical hardware |
|---|---|
| x86_64 | Intel/AMD PCs and laptops (64-bit) |
| arm64 | Apple Silicon Macs, iPhones, most Android phones, Windows ARM |
| x86 | Older 32-bit Windows systems |
| unknown | Hints blocked or ambiguous user agent |
Common use cases
- Choosing an installer — ARM64 vs x64 vs Universal on Mac or Windows.
- WebAssembly and native modules — confirm architecture before loading a binary tied to CPU family.
- Remote desktop / VM — see what the guest browser reports inside the session.
- Education — explain why an old x86 app does not run natively on arm64 without emulation.
Best practices
- Prefer Client Hints rows when present — they are more accurate than inference on Chromium browsers.
- Do not confuse architecture with OS — an arm64 Mac still reports macOS; see what operating system am I using.
- For full hardware context, open device info.
- Apple Silicon Macs running x86 apps via Rosetta may still report arm64 to the browser — the app binary can differ from the OS architecture.