# Anti-Fingerprint Source: https://metadock.app/docs/anti-fingerprint # Anti-Fingerprint Beta Give every profile its own device-level characteristics. Two profiles open on the same Windows PC appear to fingerprinting services as two separate computers, so it is far harder to link an account in one profile to an account in another. Note **Advanced anti-fingerprint is a Pro / beta feature, enabled per profile behind a legal acknowledgment.** Lower editions (Explorer and MetaDock) include basic per-profile device emulation only: user-agent and client-hints override, geolocation, timezone, and locale. The full spoofing system described below ships in Pro and beta builds. It is profile separation, not a guarantee of undetectability, and you are responsible for using it within each platform's terms and applicable law. ## Why this exists A website can identify your machine without cookies. A few lines of code reading your installed fonts, your graphics card, the way your computer renders text, the quirks of your audio hardware, and the precise timing of your clock are enough to build a stable identifier that follows you across sessions and accounts. That is fingerprinting, and it is how fraud-detection and bot services recognize a returning visitor even after cookies are cleared. Incognito is not enough: it clears cookies but leaves the fingerprint identical. To keep account A from being linked to account B on the same hardware, each profile needs to look like a different device. That is exactly what this system does, and it works hand in hand with the [profile](https://metadock.app/docs/profiles) system that keeps cookies, sessions, and history separate. ## What gets spoofed With protection on, MetaDock changes the answers your browser gives to dozens of identifying questions. The major categories: Signal What MetaDock reports Graphics card A different GPU than you actually have, drawn from a library of 100+ real-world models matched to the operating system you are emulating Screen Resolution, color depth, pixel density, and taskbar size taken from real device profiles so the values stay internally consistent CPU & memory Core count and RAM amount from the same device profile (a budget laptop reports 4 cores / 8 GB; an enthusiast desktop reports 16 cores / 32 GB) Canvas & text rendering Each profile renders graphics with a small, consistent per-profile difference, so it looks like its own device Audio Each profile's audio fingerprint is shifted so it does not match your real hardware Fonts A platform-appropriate font set instead of your real installed-font list User-agent & client hints The browser/version/OS string and the modern Client Hints headers, set per profile Network Connection type and reported speed, controllable per profile Secondary signals Battery, plugins, permissions, and installed speech voices, normalized for cross-checking Clock High-resolution timing quantized so it does not leak machine-specific drift IP & location Your real IP and location, via the profile's proxy plus the geo system below ## Presets You do not have to tune signals one by one. Pick a preset and MetaDock handles the rest, keeping the values coherent for you: - •None — protection off; your real machine answers every question - •Balanced (recommended) — tuned to look like an ordinary, consistent device to the mainstream fingerprinting and bot-detection systems in wide use, without breaking common sites - •Maximum — everything on with the strongest perturbation; catches more aggressive fingerprinters but can break features that need real device data, such as live video calls - •Custom — toggle each protection independently, for when one specific site needs you to relax one specific signal Tip Start on **Balanced**. It is calibrated to look like a normal machine to the commercial fingerprinting systems many sites use, while leaving everyday sites working. ## Stable identity A profile that looks like a different machine on every visit is its own red flag. MetaDock seeds each profile so its spoofed values stay stable: the same profile produces the same fingerprint across restarts and weeks later. From a website's view, your profile is one consistent device. - •Override the seed — paste a custom string to lock in a specific identity - •Rerandomize on every page load — genuinely look like a different device on each navigation; useful for stateless scraping, not for staying logged in Warning Rerandomize is loud. Looking like a new device on every navigation is itself an anomaly, so reserve it for throwaway scraping and keep stable seeds for any profile that stays signed in. ## Geolocation, timezone & language If a profile's IP comes from London but it reports New York coordinates, a Berlin timezone, and Japanese as its language, fingerprinting services notice instantly. The geo system keeps these aligned: - •Auto mode — MetaDock reads the IP of the profile's proxy, looks it up in a built-in offline location database (no outside service is contacted), and sets coordinates, timezone, and language to match. Move the proxy and everything follows - •Manual mode — type in latitude, longitude, timezone, and locale yourself These overrides apply before a page's scripts can read them, so a script asking for the timezone gets the spoofed answer. When geo spoofing is on, MetaDock also auto-approves the location-permission prompt so sites receive the spoofed coordinates without you clicking through a dialog. See the [proxies](https://metadock.app/docs/proxies) guide for how to point a profile at a specific region. ## Keeping signals coherent The single biggest red flag is not any one value being unusual. It is values that contradict each other: a platform that says Windows paired with an Apple GPU, a user-agent claiming one OS while the platform setting says another, or a locale and timezone that point at different regions. The Balanced and Maximum presets keep the whole bundle consistent automatically, which is why they are the safe default. If you switch to Custom and hand-edit individual signals, it is on you to keep the combination plausible: match the OS to the GPU, the user-agent to the platform, and the locale to the timezone. ## What it can and can't do It works for what it is designed for. MetaDock is built to make each profile look like its own ordinary device to the mainstream commercial fingerprinting techniques in wide use today. Profiles run independently without being linked to each other or to your real machine. Note It is not designed to defeat every academic detector. Some research tools exist specifically to count how many values look modified, and no consumer anti-fingerprint tool can beat every one of them — MetaDock does not claim to. If your goal is a perfect score on those, this will disappoint you. If your goal is to keep separate profiles genuinely separate — each with its own device characteristics — on platforms that permit you to run more than one account, it is built for exactly that. You remain responsible for using it within each platform's terms of service and applicable law. ## Good to know - •It is per profile — every profile has its own configuration; create a new profile and you get a fresh identity - •WebRTC is the usual reason a call breaks — WebRTC needs your real IP to connect, so the strictest mode disables it, which kills Google Meet, Whereby, and web Discord; soften the WebRTC setting in profiles that need calls - •Maximum can trip a checkout — some payment processors read device signals, so the strongest perturbation can interfere with a legitimate purchase; use Balanced for any profile where you need checkout to work normally - •You don't have to micro-manage — pick a preset and MetaDock handles the rest; the granular controls are there for when you actually need them