Browser fingerprint test: how to check results
A browser fingerprint test shows device and network information a website can read, so you can compare it with your browser profile's settings. Open the target profile in WGBrowser, visit a public test such as BrowserScan or Pixelscan, and record individual fields before making changes.
Different tests collect different information and apply their own checks. The same profile can receive different labels across sites. Use the results to identify a specific mismatch in your setup; no single score represents how every marketplace, advertising service or social platform assesses an account.
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.
- Check the proxy in the proxy library and record the detected exit IP and region before opening the profile.
- 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.
- Write down the field, expected value and actual value, together with the template and exit IP used for that test.
- Save the relevant change, close the profile normally and reopen it. Visit the same test and compare the new output with your record.
- 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
Which browser fingerprint test sites can I use?
BrowserScan, Pixelscan, CreepJS and BrowserLeaks can help you inspect browser and network characteristics. Run the test inside the profile you want to check, and record specific fields alongside its settings. Use another site for additional information, but avoid comparing overall scores or fingerprint identifiers as though every site calculates them the same way.
Why do browser fingerprint tests give different results?
Sites may collect different fields, use different test inputs and apply different evaluation rules. First compare the actual values behind the labels. Also check whether your engine version, proxy exit, template or noise settings changed between visits. Differences in a site's summary do not by themselves establish that the profile failed to apply its settings.
Does passing a fingerprint test prevent account restrictions?
A public test reports what it can observe about a browser and its network connection. It cannot establish how another platform evaluates an account or guarantee an outcome there. Use the results to verify your configuration, and separately check the account's login and required website functions. The test is one part of that review.
Do I need to restart a profile after changing its fingerprint?
Yes. Save the change, close the profile normally and reopen it so the browser starts with the new fingerprint configuration. Then repeat the same test under comparable conditions. A refresh in the previously running window still tests that process, so it is not sufficient evidence that the saved change has taken effect.