How browser fingerprinting combines ordinary details
A browser exposes details so websites can choose compatible features, format content, and respond to the device. Examples include the user-agent string, screen dimensions, language list, time zone, touch support, and processor count. Each value can be common on its own. The combination can be less common and may help a site recognize a returning browser.
Fingerprinting is not one universal identifier stored inside the browser. Different scripts collect different signals, process them in different ways, and combine them with cookies, account activity, IP history, or behavioral data. This page shows a limited sample so you can see the raw ingredients without claiming to reproduce every commercial fingerprinting system.
Canvas and WebGL signals
The canvas check asks the browser to draw a fixed rectangle and text, then hashes the resulting image data into a short local value. Small differences in operating system, font rendering, graphics software, and browser behavior can change the output. The displayed hash describes this sample only. Another site can draw different content and produce a different value.
WebGL provides accelerated graphics in the browser. When available, a debug extension can reveal the renderer name associated with the graphics driver. Browsers or privacy settings may remove, standardize, or replace that value. A missing renderer is a valid result and does not stop the page from showing language, time zone, screen, hardware, and other available signals.
What the result does not prove
A long list of available signals does not mean that a stranger can immediately identify you by name. It means a page can read those values. Identifying a person usually requires additional records, an account, a previously labeled browser, or another link between activity and a real identity. The same signal combination can also be shared by many devices.
A short list does not guarantee anonymity. A site may use signals not displayed here, including font measurements, audio processing, storage behavior, network timing, and interaction patterns. It may also rely on login details or server-side history. Treat this output as a readable inventory, not a score and not a promise of protection.
Reducing fingerprint consistency
Browsers designed for stronger privacy may standardize values across many users, limit high-entropy interfaces, or ask before exposing certain capabilities. Standardization can be more useful than making random changes because a highly unusual configuration may become easier to distinguish. Follow the privacy guidance for the browser you actually use rather than changing many advanced settings at once.
Extensions can add protection, but they also add code and can create a rare configuration. Keep the browser updated, remove extensions you no longer need, separate sensitive browsing from accounts when appropriate, and understand the tradeoffs of strict privacy modes. Re-run the check after a meaningful browser change to see which displayed signals differ.