CPU logical core count
Number of logical processors the browser may use.
In one line
Can see how many processor threads your device has
Number of logical processors the browser may use.
Splits users into low, mid and high end hardware (2, 4, 8, 12, 16 or more threads). Sites use it to size worker pools; trackers use it as a stable hardware trait.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- Count your logical processor threads, such as 4, 8, or 16
- Size how much work the page runs at once
- Sort you into a low, mid, or high end device
- Use the number as a steady hardware clue
It cannot
- See your chip make or speed
- See how busy the processor is right now
- See your RAM size
- Be exact in every browser; some round it
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 37 | 2014-08-26 | None |
| Edge | Supported | 15 | 2017-04-05 | None |
| Firefox | Supported | 48 | 2016-08-02 | None |
| Safari | Supported | 15.4 | 2022-03-14 | None |
| Safari on iPhone | Supported | 15.4 | 2022-03-14 | None |
| Chrome on Android | Supported | 37 | 2014-09-03 | None |
| Samsung Internet | Supported | 3.0 | 2015-04-10 | None |
How a site asks for it
| API | navigator.hardwareConcurrency |
| Browser compat keys | api.Navigator.hardwareConcurrency |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
hardwareConcurrency | integer | threads | 1 to 256, typical 2, 4, 8, 12, 16 | exact on Chrome and Edge; clamped or bucketed elsewhere |
Technical limits
- Cannot name the CPU model
- Value is logical threads, not physical cores
- Safari and Firefox protections vary by mode and script
The story
What it is
Tells a page how many processor threads your device can use.
For you
You never see it. It quietly decides how many tasks a site runs side by side. A strong laptop gets more, a budget phone fewer, which can mean faster and smoother pages.
For makers
Apps need to know how many background workers to start without freezing the machine. The count also splits people into low, mid and high end groups. It is a stable number, so trackers like it.
Where you see it
| Type | Example | Apps |
|---|---|---|
| creative | A browser video editor starts as many export workers as you have processor threads. | Clipchamp |
| games | A browser game with many AI characters picks how many to simulate based on your thread count. | None named |
| productivity | A large spreadsheet app in the browser spreads calculations across workers. | Google Sheets |
| video | A video call app decides how many video streams to decode at once. | Google Meet |
| developer | A code editor in the browser sizes its background search pool to your hardware. | VS Code for the Web |
| security | A fraud tool notes that a supposed phone reports 64 threads and flags a server. | None named |
| ads | An ad network treats a device with 16 threads as a higher spending hardware tier. | None named |
Risks
- Stable hardware trait
- Hints at how wealthy a device is
What the platform says
- MDN: Navigator.hardwareConcurrency. Docs explain it as a hint for how many parallel workers a page can sensibly start.
Good uses and abuse
Legitimate uses
- Size WebAssembly or worker pools
- Heavy web app tuning
Known abuse
- Hardware fingerprint component
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2.5 | Rough identifying entropy, when known |
A real example: LinkedIn
Collector key(s): hardwareConcurrency. BleepingComputer confirms CPU cores are collected.
History
- 2016-03, Safari 10.1: Shipped; WebKit reports a clamped count (commonly capped at a small maximum)
- 2023-11, Firefox 120: Spoofed to 2 when resistFingerprinting is on
- 2025-09, Safari 26: Advanced Fingerprinting Protection stops known fingerprinting scripts reading it reliably
- 2025-11, Firefox 145: Fingerprinting protection reports 4 or 8 in Private Browsing and ETP Strict
Related capabilities
Related
- Approximate device RAM. Can see roughly how much RAM you have, rounded and capped at 8 GB
Sources
- Mozilla Security Blog 2026-11-10: harder to fingerprint
- WebKit features in Safari 26.0 (fingerprinting protection)
- MDN hardwareConcurrency
- fingerprintjs source: hardware_concurrency
- AmIUnique: Beauty and the Beast, Laperdrix et al. 2016 (attribute entropy)
- BleepingComputer: LinkedIn scans for 6,000+ Chrome extensions
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
How well checked: Based on official documentation.