Test canvas, WebGL, and font fingerprinting to see how uniquely identifiable your browser is. A VPN hides IP — not fingerprint signals.
Sites collect hardware and software attributes to identify users without cookies. Combined with IP data, fingerprints enable cross-site tracking even in private browsing.
Canvas pixel hashes, WebGL renderer/vendor strings, and installed-font enumeration — common tracker signals.
Browser Fingerprinting Tests exists to show canvas, WebGL, and font signals this browser emits so you know what a site can use to recognize the device. It is not a second copy of the tool homepage. The homepage introduces the whole product. This page stays on one job so a search for that job lands on instructions you can follow without hunting through other tabs. Read the result on this page against the input you actually used. A screenshot without the input is not evidence. If the result surprises you, change one thing and run it again before you change your VPN, browser, or server config.
Work through Browser Fingerprinting Tests in order. 1. Open the fingerprint overview and note which signals are present. 2. Open canvas, WebGL, and fonts one at a time. 3. Compare a private window and a normal window. 4. Do not expect a VPN to change these signals. Write down the input and the output together. When you ask someone for help, send both. Repeat the same input once. A stable tool returns the same answer. If it does not, the input changed or the page is talking to a different network path than you think.
A VPN changes your IP. It does not rewrite canvas pixels or the font list. Uniqueness is not the same as your legal identity. Extensions can change the fingerprint and also make you stand out more. Treat the output as a measurement, then decide. RookVPN does not log the contents of a client-side tool, and a measurement is not a promise that every other app on the device behaves the same way. Compare a second path when the decision matters: a terminal command, another browser, or the matching guide linked below.
Example: two browsers on one laptop produce different canvas hashes, and a VPN exit shared by thousands of users does not make those hashes match. If you needed the IP hidden, use the leak test. If you needed the browser to look common, this page tells you which signals are still distinct.
After you finish Browser Fingerprinting Tests, open the public IP check when the question is the network, not the browser if the next question is different from the one this page answers. Stay here if you are still on the same job. Extra pages help only when they answer a new question, such as a different algorithm, a different leak channel, or a different file type. The documentation link on this page is the long form of the same workflow, including the checks that do not fit in the tool UI.
No. VPNs hide IP addresses but do not change canvas, WebGL, or font signals. Use hardened browsers or anti-fingerprint tools.
Yes. All RookCheck fingerprint tools are free at rookvpn.com/check/browser-fingerprinting.
No. Fingerprints come from the browser, not from the IP.
No. It is a summary of browser features. It can still reidentify a returning browser.
The canvas, WebGL, or font subpage for the signal you saw here.