Browser fingerprint parameters explained
A browser fingerprint is a set of device and browser characteristics a website can read, including system identifiers, graphics, audio, fonts, screen settings and regional information. WGBrowser configures more than twenty parameters in the browser engine and saves them with each browser profile.
For multiple accounts, understanding these fields helps you check what each profile presents to a website. Start with its device template and proxy exit IP, then compare individual fields. A public fingerprint test can show whether settings match your intent; its score does not establish an account's status on another platform.
User agent, Client Hints and OS templates
The user agent, often shortened to UA, identifies the browser and operating system. Client Hints provide related browser and platform information. Read them together: changing a UA string alone does not configure the fonts, graphics or other device characteristics that a page may also inspect.
WGBrowser provides Windows 10, Windows 11 and Apple silicon Mac device templates. In the editor, choose an OS template to generate the corresponding UA, Client Hints, platform, fonts and GPU settings together. The default follows your computer's operating system. A template for another OS may differ from the host in font and media behavior, and the client shows a warning.
A saved profile keeps its fingerprint configuration when reopened. After a browser engine update, startup adjusts the UA version to the current Chromium version while retaining the fingerprint seed. That version change does not mean the whole fingerprint was regenerated. See fingerprint settings for the profile creation and editing workflow.
WebGL, Canvas and ClientRects
WebGL exposes graphics capabilities and GPU information. Canvas lets a page draw content and read the result, which can contribute to a fingerprint. Check the reported graphics information against your selected template instead of treating one GPU label or drawing result as a verdict on the entire profile.
WGBrowser configures GPU parameters through its templates and offers stable Canvas noise. Stable noise uses the profile's saved configuration rather than choosing a new random result for every read. If you change the noise settings or regenerate the fingerprint, save and restart the profile before checking it again.
ClientRects concerns the geometry of page elements and has its own stable noise option. It is a separate interface from Canvas. Check each relevant option under Noise; enabling Canvas noise does not tell you which setting is selected for ClientRects.
Audio, fonts, screen and hardware fields
Audio processing, available fonts, screen resolution, device pixel ratio, CPU cores and memory describe different aspects of the browser profile. Compare these values with the intended device configuration. You do not need every field to differ across all profiles to understand whether a setting is working.
WGBrowser supports audio noise, template-based fonts, screen resolution, device pixel ratio, CPU and memory settings. The editor labels audio noise as AudioContext. Use the template as your starting point, and record any manual changes so you can identify which setting produced a different result.
Fonts and media behavior can still depend on the host operating system. Recheck relevant fields and page rendering when moving between Windows and Mac, especially with a template for another OS. The Mac support page explains the supported client platform; selecting a template does not change your computer's physical hardware.
Time zone, language and location
A proxy controls the network route; time zone, language and location are separate browser settings. Confirm the actual exit IP before comparing these fields. A provider's proxy name or connection address is not sufficient evidence of the exit's location.
WGBrowser can check the exit before a profile opens and use it to set these regional values. In the editor, choose Follow IP where appropriate. Custom values are also supported, and Location can be set to Deny. Interpret a missing location result in light of that permission choice.
For a profile intended to use a fixed region, establish the proxy connection first and then review its regional settings. Authentication failures and unreachable proxies need network troubleshooting. Repeatedly changing fingerprint fields will not fix those connection problems; use the proxy setup guide.
WebRTC and the proxy exit IP
WebRTC supports real-time communication in web pages and can provide network information to fingerprint tests. Record its results separately from the IP shown for ordinary page requests. Seeing a proxy exit on a web page is not a reason to skip the WebRTC check.
WGBrowser offers Proxy only and Disabled policies for WebRTC. Choose the policy according to the profile's use, then verify both the displayed network information and any communication features you need on the target website. An unavailable feature can be consistent with a disabled setting.
Profiles can use HTTP, HTTPS or SOCKS5 proxies. Review proxy management for the proxy library, exit checks and extraction sources. Fingerprint configuration and a proxy address remain separate parts of the profile, and both need to match your intended setup.
Check the saved profile in a fingerprint test
BrowserScan and Pixelscan are public tools for inspecting browser and network characteristics. Run them inside the profile you want to check. Keep a record of specific fields rather than relying on an overall score or a colored label.
- Record the profile name, OS template, noise options and current proxy, then open a test site inside that profile.
- Compare UA, Client Hints, graphics, audio, fonts and screen values. Check the exit IP alongside time zone, language, location and WebRTC.
- If a field differs from your intended setting, change only the relevant option, save it and restart the profile. Repeat the same test and compare the recorded values.
FAQ
Is changing the user agent enough to change a browser fingerprint?
The user agent covers only part of the information a website can read. Client Hints, graphics, fonts, screen settings and regional values also matter when checking a configuration. WGBrowser uses device templates to generate related fields together. Compare those fields with the saved profile settings instead of assuming a UA change also changed the rest.
Does passing a browser fingerprint test mean my account is safe?
A test reports the characteristics it collected and applies its own checks. It does not show the full decision process of a marketplace, advertising service or social platform. Use its results to investigate configuration mismatches, then check your actual login and required website functions. A passing result cannot guarantee that an account will remain unrestricted.
Should I generate a new browser fingerprint every time I open a profile?
A saved profile is designed to reuse its fingerprint configuration, including the seed used for stable noise. Regenerating it changes that configuration. Make such changes when you have a specific reason, record what you changed, and restart before checking the result. An engine update can change the UA version without resetting the seed.
Why does my browser time zone not match my proxy?
Check the actual exit IP and whether Time zone is set to Follow IP. A custom time zone may intentionally differ, and a proxy's label may not describe the exit you received. Resolve connection or region issues first, then reopen the profile and compare its time zone with the exit detected for that session.