What is a fingerprint
When your browser visits a website, it leaks dozens of details about itself — operating system, screen size, graphics card, installed fonts, time zone, and more. Taken together these details form a browser fingerprint: a combination that is often unique enough to re-identify a visitor across sessions, even without cookies.
Anti-detect browsers counter this by replacing the real fingerprint with a controlled, believable substitute so each profile looks like a different, ordinary device.
Why fingerprints matter for multi-accounting
Platforms that need to enforce one-account-per-person use fingerprinting to link accounts that share a device. If two profiles produce the same (or inconsistent) fingerprint, the platform can flag or ban them even if they use different cookies and different proxies.
A realistic fingerprint must satisfy two requirements:
- Each profile is distinct — no two profiles share the same combination of attributes.
- Each fingerprint is internally consistent — the values must hang together the way a real device would produce them (a macOS browser should not report a Windows operating system; a 4K screen should not pair with a display scale of 1, and so on).
What gets fingerprinted
Browsers expose a wide surface. The main categories are:
Browser and operating system identity
The browser name, version, and operating system are the most visible attributes. Related fields — the platform identifier and OS/CPU string — must match to avoid obvious contradictions. Network request headers must also be consistent with the in-page values.
Screen and window
Screen width, height, color depth, display scale, and window dimensions. Tracking systems correlate these values: a display scale of 2 implies a high-resolution display, which constrains which resolutions are plausible.
Graphics card (WebGL)
The graphics vendor and renderer strings, supported feature lists, and a range of capability values. This is one of the most identifying signals because GPU capabilities vary significantly across hardware.
Canvas and audio
Canvas fingerprinting renders an off-screen image and reads back the pixel data; subtle differences in font rendering and anti-aliasing produce a per-device result. Audio fingerprinting measures tiny differences in the audio processing pipeline. Both are difficult to spoof convincingly without the right noise offsets.
Fonts
Which fonts are installed on the device. The set of installed fonts is strongly correlated with operating system version and language pack.
Timezone and locale
The timezone and language preferences reported by the browser. These should match the profile's proxy location for a coherent identity.
Geolocation
If a site requests the user's location, returning coordinates inconsistent with the IP address is a red flag.
WebRTC
WebRTC can leak the real local IP address even when a proxy is in use. A controlled fingerprint replaces both the public IP and the local network IP reported by WebRTC.
Media devices
How many cameras, microphones, and speakers are reported as available. Real devices have at least one of each; profiles reporting zero of everything look unusual.
Battery
Charging state, level, and estimated times. These attributes can be used as a supplementary signal.
Codecs and voices
Supported audio and video formats, and available text-to-speech voices, vary by platform and browser version and can be sampled as part of a fingerprint.
Fingerprint vs. proxy
A fingerprint is about what your browser looks like; a proxy is about where it appears to be. Both must be consistent. If the profile's timezone and language say Tokyo but the IP geolocates to Germany, the mismatch is suspicious regardless of how good the fingerprint is.
Maskifi lets you configure timezone and geolocation to follow the proxy IP automatically so you do not have to coordinate these manually.