CPU architecture via float behavior
Telling ARM from x86 by how Float32 values behave in JavaScript.
FingerprintJS writes a Float32Array and reads bytes to detect endianness-like behavior. Chromium reduced UA hides CPU, but such probes can infer the architecture class anyway.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- Store numbers in memory and check how they behave
- Guess your chip family, such as ARM or x86
- Work even when Chrome hides the chip in its browser label
It cannot
- See your files or what you typed
- Ask permission first
- Name your exact device model
- Know who you are by itself
Browser support
How a site asks for it
| API | new Float32Array / Uint8Array reinterpretation |
| 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 |
|---|---|---|---|---|
architecture code | integer | None | small enumerated set (e.g. 127, 255) | Not listed |
Technical limits
- Coarse CPU class
The story
What it is
A script tells ARM chips from Intel style chips by how tiny decimal numbers behave in JavaScript.
For you
You never see it. Your chip does a math trick in a hidden way and the answer shows whether it is an Apple or phone style chip or a PC style chip.
For makers
It lets fraud tools check that the chip matches the claimed device, such as a phone that claims to be a Mac. Trackers add it to a device ID. Sites rarely need it for features.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A fraud tool sees a device claim to be an Intel laptop but behave like a phone chip, and flags an emulator. | None named |
| ads | A tracker uses the chip type as one more small piece of a device ID. | None named |
| analytics | A visitor tool splits users by chip family to learn how many use Apple silicon or ARM Windows. | None named |
| games | A game studio gathers chip types to decide which builds of a web game need testing. | None named |
| developer | A developer finds why a number result looks different on one chip and fixes the bug. | None named |
| banking | A bank compares chip type with the device model on file to spot a copied profile. | None named |
| shopping | A retailer checks that a device really is the phone it claims to be, to catch bots. | None named |
Risks
- Reveals your chip
- Adds to a device ID
Good uses and abuse
Legitimate uses
- None
Known abuse
- UA-reduction bypass
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 1 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
Related capabilities
Related
- Client Hints: architecture and bitness. Can tell if your chip is Intel, AMD, or ARM, and 32 or 64 bit
Sources
How well checked: Based on official documentation.