Read and change a fingerprint

The fingerprint is the machine a site reads through the browser: screen, graphics card, cores, memory, fonts, time zone and language list. The path is right-click a profile → Fingerprint. Open it when you want to see what a site sees or to pin one value by hand.

Open the fingerprint card

The card lists the values this profile presents, in the order a site would collect them.

1
Right-click a profile card
The menu appears next to it.
2
Choose Fingerprint
The card opens over the list.
3
Read the rows
Template, platform, user agent, screen, languages, cores, memory, WebGL, time zone and the WebRTC policy.

Where the values come from

Nothing here is stored. Every value is derived from the profile's own number and its template, which is why the same profile shows the same machine on every launch.

Change the template and the machine changes with it.

The exit country moves three rows

When the profile has a proxy, the country it leaves through sets the time zone and the language list. The card is computed with the proxy counted, exactly the way a launch is.

Without that the card would say one thing and the browser another.

Change values by hand

Change values turns a few rows into lists. Only values a real machine of that platform reports are offered, and cores and memory are held to what a machine with the chosen graphics card actually has.

1
Press Change values
At the bottom of the fingerprint card.
2
Pick from the lists
Screen, cores, memory, pixel ratio, time zone, languages and WebGL.
3
Press Save
Back to generated returns every row to the generator.

Free text would give the profile away

A value no real machine reports stands out harder than any generated one. That is why these rows are lists and not empty fields.

Check it inside a real browser

Test fingerprint opens a throwaway copy in the engine and reads the values back the way a page script would. It reports how many checks passed and which engine and version it measured on.

If the protection for that copy could not be prepared the check does not run at all, rather than showing failures your real profile does not have.

Compare with your other profiles

Compare with other profiles counts how many of your own profiles describe the same machine. Two profiles with one machine are tied to each other more tightly than anything else here.

What this does not do

It does not hide that a browser is a browser. It makes the machine behind it an ordinary one.
It does not accept free text. Only values the generator itself could have produced are offered.
It does not follow the computer you are sitting at. The profile describes the machine its template and number describe.

Where this is decided

Each claim above is one place in the code and one stand.

A profile keeps the generator it was created with: apps/desktop/test/fingerprint-version.js
The parts of a fingerprint agree with each other: apps/desktop/test/fingerprint-consistency.js
The self-test reads the values back inside the engine: apps/desktop/test/fp-audit.js
The card counts the proxy exactly as a launch does: apps/desktop/test/fingerprint-card-matches.js

Questions

I edited it and nothing changed.: The profile was open. Proxy, use case and fingerprint changes apply the next time it starts, and the app says so when you save.
Does an update change the machine?: No. A profile keeps the generation it was made with, so an update does not present its accounts a computer they have never seen.
What does the self-test actually measure?: Values read back inside the engine: the automation flag, the canvas readback, the font set, the time zone, the language list and the nested frames.
Why are fonts limited to a set?: Font enumeration is one of the strongest signals a page can collect, so the profile shows the set its own fingerprint claims.

Next to this

See it on your own profile

The free plan gives two profiles, with no time limit and no card.

Download ARMANOS Knowledge base