my-fingerprint is a lightweight, open-source browser extension, written in TypeScript for Chrome, Edge and Firefox, that disguises the fingerprinting signals websites use to identify and track visitors across sites.
What it is
my-fingerprint is a Manifest V3 browser extension written in TypeScript and released under the Apache-2.0 licence. It lives in the Chrome, Edge and Firefox extension ecosystem, ships bilingual Chinese and English documentation, and is distributed through the Edge Add-ons store and the Firefox Add-ons gallery, including Firefox for Android, with manual .zip and .xpi packages covering the remaining cases. The extension uses lightweight native injection with no dependencies, and its stated design goal is to work immediately after installation without additional configuration.
The problem it addresses is browser fingerprinting: the practice of combining signals such as canvas rendering, audio output, installed fonts, WebGL and WebGPU characteristics, screen geometry, and language and time zone into an identifier that websites can use for cross-site tracking. The project notes that a single fingerprint item is rarely unique on its own, but that several combined, particularly alongside IP address and browser storage, can identify a user with high confidence. my-fingerprint therefore spoofs key fingerprint values to break that tracking chain, and it can also monitor how pages access fingerprint APIs. In scope it stands in for a dedicated fingerprint browser, which simulates a complete environment; this project takes the lighter route of injecting script into the page instead.
Key capabilities
- Spoofs Canvas, WebGL, Audio, Fonts, WebGPU, WebRTC and DomRect fingerprints, along with language and time zone, graphics driver information, UserAgent, and screen size and resolution.
- Divides protection into a strong fingerprint group, which simulates highly unique user characteristics, and a weak group covering basic signals with high repetition rates.
- Monitors page access to fingerprint APIs, so extension activity can be observed rather than assumed.
- Supports whitelist rules with subdomain matching, where
example.com also matches *.example.com and *.*.example.com.
- Provides configuration import and export, plus a subscription mechanism that pulls a remote JSON template, either manually or automatically at extension startup; subscription settings override local settings and merge whitelist entries.
- Offers a global seed for reproducible randomised values and a "quick injection" mode recommended for compatibility and performance.
- Builds on Manifest V3 with zero dependencies, keeping performance overhead low.
Who uses it and how
- Individuals on Chrome, Edge, Firefox or Firefox for Android who want everyday fingerprint protection without running a separate hardened browser.
- People who verify the result themselves against established testing targets such as browserleaks.com, CreepJS, browserscan.net, webbrowsertools.com, yalala.com and uutool.cn.
- Users who need per-site exceptions: a page that misbehaves under spoofing can be placed on the whitelist, or the "known issues" configuration preset applied.
- Anyone keeping settings consistent across several installations, who can export a configuration or subscribe each browser to a remote JSON template that is re-applied at startup.
- Developers and contributors who build the extension locally and file Issues or Pull Requests; the project also runs a QQ community group.
Getting started
Install from the Edge Add-ons store or the Firefox Add-ons gallery, which includes the Android build; Chrome users download the latest .zip release and drag it into the extension management page, with Chrome or Edge 102 or later required and 120 or later recommended, while Firefox users install the .xpi on Firefox 136 or later. Building from source takes npm install followed by npm run dev or npm run dev:firefox.
How it compares
The README positions my-fingerprint against fingerprint browsers as a category: a good fingerprint browser simulates a complete environment for deep disguise and suits anti-detection work, whereas this project relies on JavaScript injection, stays light, and covers most fingerprint-protection cases. The distinction drawn is between environment-level simulation and page-level modification, not between products on licence, hosting or cost.
When to use it — and when not to
There is nothing to operate server-side: it is a client-side extension with no database, storage or mail service to run. Anyone who needs full environment simulation for anti-detection should use a dedicated fingerprint browser instead, and users on Chrome must accept manual sideloading while no store listing exists. Over-spoofing is a genuine risk, since the project's own FAQ warns that masking more items than necessary can break page functionality or make behaviour look anomalous, and the README limits the project to learning and research purposes.