How browser fingerprinting works

The measurement

What a site actually reads

The interesting signals are the ones with hardware underneath them. Asked to draw the same shape, two machines produce subtly different pixels, because the GPU, the driver and the font rasteriser all differ — so the page hashes the result and gets a number that is stable for your device and rare across everyone else's. The same trick works on the audio stack. Alongside those sit the declarative properties: platform, languages, timezone, screen geometry, device memory, CPU core count.

None of this is exotic or hidden. Every one of these is a documented web API doing the job it was designed for, which is exactly why blocking them is not an option — a browser that refuses to report a screen size is more conspicuous than one that reports an ordinary screen size. Argus covers these surfaces:

• ✓Canvas, WebGL (including reported vendor and renderer), and audio
• ✓Platform, languages, timezone, screen, device memory, and CPU core count

Fingerprints

One value that disagrees ruins the whole set

This is the part that costs people accounts. A fingerprint is judged as a set, and the check that matters is not "is this value unusual" but "do these values describe a machine that could exist". A user-agent claiming macOS beside UA-CH metadata that says Windows describes no real computer. Neither does a device reporting a 4K screen, two CPU cores and a timezone three hours from its exit IP.

Random values per profile actively make this worse: the more fields you scramble independently, the more likely two of them contradict. So Argus generates the identity as a unit — An auto-generated hardware identity per profile, coordinated so that nothing contradicts anything else.

• ✓Windows, macOS, and Linux presets, with the user-agent and UA-CH metadata generated to match
• ✓Platform, CPU cores, memory, screen, timezone, and languages generated together as one coherent set

The network half of the same problem is the address the session arrives from, which no amount of fingerprint work can fix from inside the browser. That is what a per-profile proxy is for.

The browser

Where the substitute is applied

Most anti-detect tooling automates a browser it did not build, so the only place it can intervene is JavaScript: an extension or an injected script replaces the real function with a wrapper that returns a different answer. That works until a page looks at the wrapper. A native function that has been reassigned no longer stringifies like a native function, prototypes and property descriptors shift, and the wrapper itself becomes the tell — the page now knows not just that you are hiding something, but that you are the kind of visitor who hides things.

Argus ships its own build of Chromium, so the substitution happens a layer below that. The identity is applied below the page, where a script cannot read around it.

• ✓A script sees the spoofed value because that is the only value present, not because a wrapper hid the real one

Fingerprints

Four modes, per surface

Spoofing everything is not automatically the safest setting, so each surface is configured on its own rather than by one master switch.

• ✓Each surface runs in one of four modes: real, noise, off, or manual

Realpasses the machine's own answer through, which is what you want on a surface where your hardware is unremarkable. Noise perturbs the result so the hash differs per profile while the output still looks like something a GPU produced. Off declines the surface. Manual pins the exact value you type, for when a profile has to keep reporting what it reported last month.

Fingerprints

Presets, pinning, and the re-roll

A new profile gets a coherent identity without you doing anything; the editor is there for the parts you want to decide yourself.

• ✓Per-profile editor for the parts you want to pin yourself
• ✓One-click re-roll produces a new identity while preserving your configuration

The re-roll matters more than it sounds. When a profile's identity has to change — a fresh start after a flag, a profile handed to a different client — you want a new hardware identity and the same proxy, cookies, tags and notes. One click does that, rather than deleting the profile and rebuilding its configuration from memory.

Honestly

What a fingerprint cannot fix

A coherent identity answers one of the three questions a site asks on arrival. It does nothing about the other two, and a setup that gets those wrong fails regardless of how good the fingerprint is.

The second is the address. A profile presenting a Warsaw device and arriving from a datacenter range in Frankfurt has contradicted itself before the page finished loading — how proxies work in Argus covers the network half, including how to buy proxies that survive the sites you care about.

The third is state. Two profiles with immaculate, entirely different fingerprints are still one account if they share a cookie jar, a cache or a service-worker registration — profile isolation is what keeps them apart on disk.