Browser Fingerprint

User Agent High Impact

A text string containing your browser name, version, operating system, and device information. This is sent with every web request and is the single most identifying component of your fingerprint.

How to make it more common: Use a popular browser like Chrome or Firefox with default settings. Avoid niche browsers or very old versions. Firefox's privacy.resistFingerprinting setting reports a generic user agent. Tor Browser uses a standardized user agent for all users.

GPU Renderer High Impact

Your graphics card model as reported by WebGL. Since GPU models vary widely, this is a strong identifier. Combined with the vendor, it can narrow you down significantly.

Note: Laptops often have hybrid graphics — both an integrated GPU (Intel/AMD) and a dedicated GPU (NVIDIA/AMD). Browsers typically use the integrated GPU by default for power efficiency. If you have a dedicated GPU but see an Intel/AMD integrated one here, this is normal behavior, not an error. You can force your browser to use the dedicated GPU in Windows Graphics Settings or your GPU control panel.

How to make it more common: Use Firefox with privacy.resistFingerprinting = true (reports a generic renderer). Browser extensions like Canvas Blocker can also mask WebGL data. Disabling WebGL entirely is possible but may break some websites.

Detected Fonts High Impact

The number of installed fonts detected on your system out of 20 commonly tested fonts. Different operating systems and software installations result in different font collections, making this a powerful fingerprinting vector.

Note: Privacy-focused browsers like Brave intentionally report fewer detected fonts as part of their anti-fingerprinting protection. For example, you might see 18/20 in Chrome but only 15/20 in Brave on the same computer. This is expected behavior — the lower value means Brave's protection is working, not that fonts are missing from your system.

Why values differ between browsers:

• Chrome / Edge: Show the real number of installed system fonts (no protection)
• Brave: Masks some fonts to reduce fingerprint uniqueness (protection enabled)
• Brave Tor: Even more aggressive masking for maximum privacy
• Firefox (with resistFingerprinting): Restricts font enumeration to a standard set

Value stability: In Chrome and Edge, the value remains constant unless you install or remove fonts. In Brave, the value is also stable (does not change on page refresh), but may differ from Chrome due to the masking. Some privacy browsers may use "farbling" — adding slight randomization to prevent consistent tracking.

How to make it more common: Avoid installing unusual or custom fonts. Use a standard OS installation without additional font packs. Firefox with privacy.resistFingerprinting restricts font enumeration to a standard set. Tor Browser blocks font detection entirely.

Screen Resolution High Impact

Your screen's pixel dimensions (width x height). The most common resolutions are 1920x1080 (Full HD) and 1366x768. Unusual or very high resolutions make you stand out.

How to make it more common: Use a standard resolution like 1920x1080. If you have a 4K or ultrawide monitor, you can resize the browser window to a common size (though some fingerprinting scripts read the screen resolution, not the window size). Firefox's privacy.resistFingerprinting reports a rounded window size.

WebGL Parameters Medium Impact

Technical details about your GPU's capabilities: maximum texture size, maximum renderbuffer size, and the number of supported WebGL extensions. These values are tied to your specific graphics hardware and drivers.

How to make it more common: These values are hardware-dependent and difficult to change without masking. Use Firefox with privacy.resistFingerprinting or a WebGL-blocking extension. Updating your graphics drivers may change some values but won't necessarily make them more common.

Media Codecs Medium Impact

The number of video and audio codecs your browser supports. We test 19 common codecs:

Video codecs (8):

Audio codecs (11):

Different browsers and operating systems support different codec sets, contributing to your fingerprint.

How to make it more common: Use a mainstream browser (Chrome, Firefox) on a mainstream OS (Windows 10/11). Avoid browsers with unusual codec support. There is no easy way to change which codecs your browser supports without switching browsers.

CPU Cores Medium Impact

The number of logical processor cores reported by your browser. Common values are 4, 8, or 16. Very high core counts (24, 32, 64) or unusual numbers make you more identifiable.

How to make it more common: This value reflects your physical hardware and cannot be changed without masking. Some privacy-focused browsers intentionally mask or randomize this value (Brave, Tor Browser, Firefox with privacy.resistFingerprinting, LibreWolf, Mullvad Browser).

Device Memory Medium Impact

The approximate amount of RAM on your device in gigabytes. This API is only available in Chromium-based browsers (Chrome, Edge, Opera). Firefox and Safari report "Not available", which is actually better for privacy. The maximum reported value is 8 GB for privacy reasons - even if you have 16, 32, or 64 GB of RAM, the browser will report 8 GB.

Note: Privacy-focused browsers like Brave may intentionally return a modified or randomized value as part of their anti-fingerprinting protection (Brave Shields). This means the displayed value may not reflect your actual RAM. This is expected behavior, not a bug.

How to make it more common: Use Firefox or Safari, which don't expose this API. Common values in Chrome are 4 or 8 GB. There's no way to change the reported value without switching browsers.

Pixel Ratio Medium Impact

The ratio between physical pixels and CSS pixels on your display. 1x is standard, 2x is common on Retina/HiDPI displays. Unusual values like 1.25x, 1.5x, or 3x make you more identifiable.

How to make it more common: Set your display scaling to 100% (1x) or 200% (2x) in your OS settings. Avoid fractional scaling (125%, 150%) as these produce uncommon pixel ratios. Firefox's privacy.resistFingerprinting reports 1x regardless of actual value.

Browser protection: Most browsers — including Firefox, Brave, Brave Tor mode, and Google Chrome — do not modify or mask the Pixel Ratio value by default. They report the real value directly from your operating system's display scaling settings. The reason is that altering the pixel ratio would break page rendering — images could appear blurry, layouts could shift, and responsive design would malfunction. Browser vendors prioritize usability over fingerprint protection for this parameter.

Note: The only mainstream browser that actively changes this value is Tor Browser, which always reports a pixel ratio of 1.0 regardless of your actual display scaling, so that all Tor users appear identical.

Platform Low Impact

The operating system platform string reported by navigator.platform. There are only a few possible values, so this has relatively low identifying power on its own:

How to make it more common: Using Windows or macOS gives you the most common values. This is difficult to change without switching your OS. Note: this API is deprecated and being replaced by navigator.userAgentData.platform in Chromium-based browsers.

Color Depth Low Impact

The number of bits used to represent the color of each pixel. Almost all modern displays use 24 bits (16.7 million colors). A value of 30 or 48 bits would indicate a professional HDR display and make you more unique.

How to make it more common: Use default display color settings (24-bit). Avoid switching to HDR or 10-bit color modes in your OS settings.

Note: Tor Browser always reports a color depth of 24 regardless of your actual display settings, so that all users appear identical.

Timezone Offset Low Impact

The difference in minutes between your local timezone and UTC. For example, Central European Time (CET) is -60 (60 minutes ahead of UTC). This is shared by millions of users in the same timezone. However, combined with other parameters like language, it can help reveal your real location — for example, if someone uses a VPN to appear as if they are in the US, but their timezone offset is -60 (CET), this inconsistency can be detected.

How to make it more common: Use a common timezone like UTC, US Eastern, or Central European. Setting your OS to a different timezone will change this value but may cause confusion with local times.

Language Low Impact

Your browser's preferred language setting (e.g., en-US, cs-CZ). Common languages like English are shared by hundreds of millions of users. Less common languages add to your uniqueness.

Note: Unusual combinations of language and other parameters can reveal VPN usage — for example, a browser set to cs-CZ with a US timezone offset suggests the user is likely in Central Europe, not the US. Tor Browser sets the language to en-US for all users to prevent this kind of detection.

How to make it more common: Set your browser language to en-US (the most common value worldwide). This can be changed in your browser's language settings without affecting the rest of your system.

Cookies Enabled Low Impact

Whether your browser accepts cookies. Over 99% of users have cookies enabled, so this value rarely distinguishes you. However, having cookies disabled is very uncommon and ironically makes you more unique.

How to make it more common: Keep cookies enabled (the default). Blocking only third-party cookies is a good privacy measure that doesn't affect this value.

Storage APIs Low Impact

Checks whether your browser supports four client-side storage methods:

• sessionStorage — temporary data that is cleared when the tab is closed
• localStorage — persistent data that survives browser restarts
• indexedDB — a client-side database for larger amounts of structured data
• openDatabase — older Web SQL API (deprecated, only supported in Chrome/Safari)

These are available in virtually all modern browsers, so they add minimal uniqueness. The only case where they differ is if you've explicitly disabled them.

Note: In Tor Browser and private browsing mode, these APIs are available but localStorage and indexedDB data is automatically deleted when the browser is closed. Firefox-based browsers (including Tor Browser) do not support openDatabase (Web SQL), which may produce a slightly different result compared to Chromium-based browsers.

How to make it more common: Keep the default browser settings. All major browsers support these APIs out of the box.