Browser fingerprint test

How to read the four checks

The test compares only facts it can verify: whether values the browser reports contradict each other, and whether the browser matches its network connection. "Check this" means a website can see the mismatch; fix it as the table suggests, reopen the profile and test again. "Not comparable" means there is nothing to compare, for example when the IP location is unknown.

The fingerprint ID is calculated from canvas, WebGL, audio, fonts, User-Agent, platform, languages, time zone, screen and hardware values, without the window size or the IP. Reopening the same profile should keep it unchanged; two profiles with the same ID do not differ in any of these values.

Record the profile and test conditions

Before testing, note the profile name, OS template, browser engine version, proxy and time of the check. Open the test inside that profile's window. A result from your everyday browser describes that browser, so it cannot verify the profile you configured in WGBrowser.

BrowserScan, Pixelscan, CreepJS and BrowserLeaks provide places to inspect browser characteristics. Use another test when you need a field the first one does not display. Keep the field names and values, not just a screenshot of the summary. A fingerprint identifier calculated by one site is not directly comparable with an identifier from another.

1. Check the proxy in the proxy library and record the detected exit IP and region before opening the profile.
2. Save the relevant settings and test output. If a page loads incompletely, check the connection before interpreting missing fields as a fingerprint problem.

UA, operating system and hardware fields

Read the user agent and Client Hints together to check the browser version and operating system information. Then compare the screen, CPU and memory fields with the selected OS template. A value that differs from your host computer is not automatically an error: first establish what the profile is configured to report.

WGBrowser has Windows 10, Windows 11 and Apple silicon Mac templates. A template sets related UA, Client Hints, platform, font and GPU information together. Cross-system templates can differ from the host in fonts and media behavior, and the interface warns about this limitation. For the meaning of each category, see browser fingerprint parameters.

Graphics, audio and stable noise

WebGL results describe graphics capabilities and GPU information. Canvas, audio and ClientRects tests inspect drawing, audio processing and element geometry. Sites may use different inputs and calculations, so compare a profile's repeated results on the same test rather than expecting matching summaries from unrelated tests.

WGBrowser offers stable noise for Canvas, AudioContext and ClientRects. The saved profile reuses its configuration. Reload the same test page, then close and reopen the profile for another check. Record whether you changed a noise option or regenerated the fingerprint between checks; otherwise you may mistake an intentional configuration change for an unexplained difference.

Keep the investigation focused on the field that differs from your settings. Making every value different across multiple accounts is not the purpose of a configuration test, and repeatedly changing an established profile makes your records harder to compare.

Proxy exit IP and regional settings

Distinguish the proxy connection address, the exit IP detected by the client and the request source reported by the test site. The connection address alone does not identify the final exit. With a dynamic proxy, record extraction or session changes so you know whether two tests used the same connection arrangement.

WGBrowser can check the exit before opening a profile and set Time zone, Language and Location to Follow IP. Compare these fields with the actual exit. If you use custom values, compare the output with those settings instead. Location also depends on permission: choosing Deny explains a missing result differently from choosing Follow IP.

If the client and test disagree on region, compare their IP addresses first, then note differences in country, city and time zone. A city label alone is insufficient reason to replace the fingerprint. See proxy setup for connection checks and residential proxy types for fixed and rotating exit considerations.

WebRTC results and website functions

WebRTC supports real-time communication and can expose network information in a test. Record it separately from the exit shown for normal page requests. If the test shows no candidate addresses, review the WebRTC policy and confirm that the test page finished running before deciding whether something failed.

WGBrowser offers Proxy only and Disabled policies. A test reporting that a disabled capability is unavailable may be showing the expected result. If you need a website's calling or other communication features, check their actual behavior with the selected policy. The fingerprint feature guide explains how these settings fit into a profile.

Interpret warnings and scores

Start with the exact field behind a warning. Test sites differ in what they collect, how they evaluate it and how they display a result. A denied location request, disabled WebRTC or a changed device template must be interpreted against the corresponding settings. A warning on a test page is not an account status message from your business platform.

Browser engine updates can also affect comparisons. When WGBrowser starts a profile after an update, it adjusts the UA version to the current Chromium version while preserving the fingerprint seed. Keep the engine version in your records. Stable profile settings do not mean that every browser field stays identical across software updates.

Repeat the test after a configuration change

Match the correction to the issue you observed. Resolve proxy connection or authentication errors first. Check Follow IP when a time zone differs, and review the device template when system information is unexpected. Fingerprint changes take effect after saving and restarting the profile; refreshing a page in the old process does not test the new configuration.

1. Write down the field, expected value and actual value, together with the template and exit IP used for that test.
2. Save the relevant change, close the profile normally and reopen it. Visit the same test and compare the new output with your record.
3. Open the business website and check login and the functions you need. Use the multi-account isolation guide to keep each account assigned to its intended profile.

FAQ