What makes a browser fingerprint consistent

One profile, one story

Think of a profile as a short biography: this person uses Windows, works in Berlin, reads German, and connects from a German residential line. Every value the browser reports is a sentence in that biography. The job is to keep the sentences from contradicting one another.

The pairs that contradict each other most often:

• Exit IP country vs. timezone
• Timezone vs. the clock’s actual offset right now (summer time moves)
• Language list vs. country
• Platform in the user agent vs. platform in the rendering stack
• Screen size vs. device type
• WebRTC candidates vs. the proxy’s address

Geography: the pair that catches everyone

If your proxy leaves from Germany, the profile’s timezone should be Europe/Berlin, its locale de-DE (with English as a second language if you like — that is ordinary), and its geolocation, if a page asks, somewhere in Germany.

In WarpX Browser these follow from the country you pick when you create the profile, so the common mistake — changing the proxy later and leaving the clock where it was — is worth a second look whenever you move a profile to a different exit.

WebRTC, the leak that survives a proxy

WebRTC asks your operating system for its network addresses so two browsers can talk directly. A page can read those candidates, and they are the real ones — the proxy never sees the request. A profile behind a Berlin proxy that offers a local address from your home network has answered the question twice, differently.

WarpX Browser blocks that leak per profile. It is worth testing anyway, because it is the check most people skip and it costs nothing.

Canvas, WebGL and audio: noise, not blanks

These three produce a hash of how your machine renders something. Blocking them is conspicuous; returning the same hash on every profile is worse, because it links them to each other.

The workable answer is small per-profile noise: each profile renders slightly differently from the others but the same way every time, so it is stable for itself and distinct from its neighbours. That is what the profile’s fingerprint settings do.

A ten-minute check

Open the profile you are about to use and walk through this list:

1. Exit IP. Check it in the proxy manager, then confirm on any “what is my IP” page inside the profile itself.
2. Clock. The page should show the local time of that country, not yours.
3. Language. The accepted-languages header should lead with that country’s language.
4. WebRTC. A leak test should show no address from your own network.
5. Rendering. A fingerprint test page such as Cover Your Tracks should give this profile a different canvas and WebGL hash from another of your profiles — and the same hash as itself on a second visit.
6. Storage. Signing into a site in one profile should leave every other profile signed out.

If all six hold, the profile tells one story. Then keep it that way: one identity per profile, the same proxy country for its life, and a backup so a reinstall does not cost you the history that made it look real.