简体中文 | English

---

My Fingerprint

Protect your browser fingerprints and enhance privacy. Chrome, Edge, Firefox supported.

A lightweight, zero-disruption browser extension built on Manifest V3.

---

✨ Features | 🧬 Fingerprint | 🧰 Installation | ⚙️ Configuration | 🧪 Testing | 🛠️ Development | ❓ FAQ | 💝 Support | 📜 Disclaimer | 🙏 Credits

✨ Features

• 🚀 Supports Chrome, Edge, and Firefox
• ⚙️ Works instantly upon installation, no configuration required
• 📦 Built on Manifest V3 for modern compatibility
• 🔍 Monitors fingerprint API access on web pages
• 🧱 Customizable protection rules and whitelist support
• 📤 Import/export configuration and subscription support
• 🧩 Lightweight native injection, zero dependencies, negligible performance cost

🧬 Fingerprint Protection

• Canvas fingerprint
• Audio fingerprint
• Fonts fingerprint
• WebGL fingerprint
• WebRTC protection
• WebGPU fingerprint
• DomRect fingerprint
• Language and timezone
• Graphics driver info
• UserAgent series
• Screen size and resolution

🧰 Installation

🧩 Extension Store Installation

💡 Extension store updates may lag behind GitHub due to review delays.

• Edge
• Firefox
• Firefox for Android
• Chrome: Not yet available. Please use manual installation.

📦 Manual Installation

Chrome / Edge

• Required version: Chrome/Edge 102+
• Recommended: 120+
• Download .zip → Drag into extension manager → Enable
• Optional: Enable in Incognito/InPrivate mode

Firefox

• Required version: Firefox 136+
• Download .xpi → Drag into browser window → Click “Add”

⚙️ Configuration Module

This module provides flexible options for customizing fingerprint protection behavior:

• Strong Fingerprint Group

  • Simulates highly unique user characteristics
  • Typically used in combination with other fingerprints or IP data

• Weak Fingerprint Group

  • Captures basic, high-repetition information
  • Suitable for lightweight protection scenarios

• Script Settings

  • Global Seed: Used for the “Random by Global Seed” option to ensure consistent output
  • Injection Mode: Recommended to enable “Fast Injection” for better compatibility and performance

• Whitelist Management

  • Supports editing whitelist entries
  • Subdomain matching supported: e.g., example.com matches *.example.com, *.*.example.com

• Subscription Options

  • Use configuration templates for quick setup (subscription can be disabled after initial use)
    • Standard Mode – Default Template
  • Empty value disables subscription
  • Supports manual subscription or auto-fetching remote config (JSON format) on extension startup
  • Subscription config will override existing settings and merge whitelist entries

🧪 Testing Targets

• webbrowsertools.com
• browserleaks.com
• CreepJS
• browserscan.net
• yalala.com
• uutool.cn

🛠️ Development

cd <project>
npm install
npm run dev          # Chrome / Edge
npm run dev:firefox  # Firefox

❓ FAQ

Q: What should I do if the extension doesn't work properly or some pages behave abnormally?

A: Try enabling Fast Injection Mode in the script settings to improve compatibility. For abnormal pages, you can either add them to the whitelist or apply the Known Issues List from the configuration presets to resolve common problems.

Q: Why do I need this extension?

A: Browser fingerprints can be used for cross-site tracking, compromising user privacy. This extension disguises key fingerprint data to reduce the risk of identification and tracking.

Q: How is this extension different from a fingerprint browser?

A: A well-designed fingerprint browser simulates a complete environment for deep obfuscation, ideal for anti-detection scenarios. This extension uses JS injection, offering lightweight protection suitable for everyday use and most fingerprint-related threats.

Q: Are browser fingerprints a unique identifier?

A: Not strictly. A single fingerprint may not be unique, but when combined with IP address, browser storage, and other data, it can strongly identify a user.

Q: Is it better to protect as many fingerprints as possible?

A: Not necessarily. In many cases, modifying just one key fingerprint is enough to break tracking. Overprotecting may cause site compatibility issues or expose abnormal behavior. Choose protection items based on actual needs.

Q: What's the difference between strong and weak fingerprints?

A: Strong fingerprints are highly unique and often used for precise tracking—modifying them greatly enhances privacy. Weak fingerprints have low uniqueness and are usually safe to leave unchanged to maintain compatibility.

💝 Support

• If you find this project helpful, give it a ⭐
• Your feedback helps make this project better. Every star counts!
• Support me on Ko-fi

📜 Disclaimer

This project is for educational and research purposes only. Do not use it for illegal activities. The developer is not responsible for any consequences.

🙏 Credits

Thanks to all contributors and the open-source community!