fingerprint-chromium is a free, open source browsers & extensions project written in several languages and released under BSD-3-Clause. It has 3,223 GitHub stars, 455 forks and 28 open issues, and was last pushed 1 months ago. On this registry it ranks #82 of 150 tracked projects in Browsers & Extensions, with 5 head-to-head comparisons available. It gained 128 stars over the last 30 tracked days.

What is fingerprint-chromium?

fingerprint-chromium is an open source fingerprint browser based on Ungoogled Chromium, distributed as prebuilt browser binaries for Windows, Linux, and macOS, and aimed at anyone who needs to control the fingerprint their browser presents to a website — anti-bot testing, anti-detection research, scraping, and privacy work.

What it is

fingerprint-chromium lives in the Chromium ecosystem. It is a build of Ungoogled Chromium, the Chromium variant with Google integration stripped out, carrying changes that let the browser present an altered or controllable fingerprint. Each Chromium major version is compiled into its own release, and the repository publishes a matching source branch alongside the binaries. The artifacts follow a predictable naming scheme, for example ungoogled-chromium_148.0.7778.215-1.1_installer_x64.exe and ungoogled-chromium-148.0.7778.215-1-x86_64.AppImage, so a specific Chromium level can be pinned deliberately rather than drifting with whatever ships today.

The concrete problem it addresses is that a stock Chromium build presents a consistent, identifiable fingerprint, and that hardening against that is tedious to do yourself. Ungoogled Chromium is a privacy-oriented base but is not itself a fingerprint browser; fingerprint-chromium supplies the modified build ready to download, replacing the work of patching Ungoogled Chromium and rebuilding it from source. It is released under BSD-3-Clause.

Key capabilities

  • Prebuilt binaries per Chromium major version: Chrome 148, 144, 142, and 139 are listed, each as a separate release.
  • Windows distribution as both _installer_x64.exe and _windows_x64.zip.
  • Linux distribution as -x86_64.AppImage and -x86_64_linux.tar.xz.
  • macOS distribution as a .dmg package, for example 148.0.7778.215-1.1_macos.dmg.
  • Matching source code branches published per version, such as 144.0.7559.132 and 142.0.7444.175.
  • Fingerprint control as the core modification on top of Ungoogled Chromium, reflected in the fingerprint, anti-detection, and anti-bot topics.
  • Chromium upstream tracking, with the Chrome 148 entry recorded as released alongside Chrome 149.

Who uses it and how

  • Scraping and automation operators who need a browser that does not present a fixed, easily clustered fingerprint to the sites they drive.
  • Anti-bot and anti-detection work, where the operator needs to see how a site responds to a browser whose identifying signals have been changed.
  • Privacy-focused users who want Ungoogled Chromium plus fingerprint control without maintaining a private patch set.
  • Windows, Linux, and macOS users, with a separate artifact per platform and per Chromium level for each.
  • Anyone pinning a specific Chromium version for compatibility with an existing automation stack, since the older release lines remain downloadable.

Getting started

There is no package manager, container image, or hosted service documented. Download the release matching the operating system from the links in the release table — the Windows installer or ZIP, the Linux AppImage or TAR.XZ, or the macOS DMG — and run it.

How it compares

Among the tools named in the facts, the only comparable one is Ungoogled Chromium itself, which is the base this project builds on rather than a competitor. fingerprint-chromium sits downstream of it as a recompiled variant that adds fingerprint control, and no paid or commercial fingerprint browser is named in the available facts.

When to use it — and when not to

The README states plainly that the project provides no technical support and that anyone contacting you for payment is a scammer, so a self-hoster must be prepared to work things out alone against a thin README. The documented setup is download and run; there is no description of updates, an API, or automation integration, and the newest source entry is noted as released with Chrome 149, which suggests version lag worth checking before adopting it. If you need vendor support, a maintained release channel, or documentation beyond a download table, this project is not the right pick.

project readme (upstream, from github) — read inline

fingerprint-chromium

中文文档

A fingerprint browser based on Ungoogled Chromium.

⚠️ Notice: This project provides no technical support. Please do not contact me for help. Anyone who contacts you asking for payment is a scammer — do not be fooled.

Installation and Usage

Download

Please download the version suitable for your system from the links below. Each major version of Chromium is compiled into a corresponding release. Choose the appropriate version for your operating system:

For chinese users, you can download via cloud storage

Quark: https://pan.quark.cn/s/9bb65af874fb


You can find the compiled versions for each major Chromium release on the GitHub Release page. Download the appropriate file for your platform.

Build from Source

SOURCE CODE IS AVAILABLE IN THE GITHUB REPOSITORY TAGS, NOT IN THE MAIN BRANCH!

To maintain the integrity of this free and open source project, we've adopted a delayed source code release policy:

  • Current Version: Compiled binaries are immediately available for all users
  • Source Code: patch files will be released when the next version is published (typically one month later)

This approach helps prevent unauthorized repackaging and profiteering from our work while maintaining our open source commitment.

Once the source code is released, you can build by referring to the ungoogled-chromium documentation. Simply replace the ungoogled-chromium submodule URL with the fingerprint-browser repository URL.

📢 Author's Other Projects

🌟 EasyChat - Claude Official Site Mirror

🔥 EasyChat is a Claude official site mirror providing China direct access experience with 1:1 restoration of official features for efficient AI assistant services!

  • 🌐 China Access: Direct connection to Claude official services without VPN.
  • 🤝 Shared Membership: Cost-effective way to enjoy Claude member features with no account ban risks.
  • 👤 Dedicated Membership: Exclusive account for your personal use with Claude Code support, full member privileges with stable and uninterrupted service.
  • 🔑 Account Hosting: Securely host your own account with Claude Code support for seamless China direct access.

🔗 Visit: https://easychat.top

🛠️ Flapcode

A one-stop solution designed for users who need Claude Code / Codex but prefer not to self-host.

Core Advantages:

  • 🌐 Direct China Access: Access full Claude Code / Codex functionality at high speed without VPN
  • 👤 Dedicated Accounts: Individual account per user, no shared account pools, lower cost, stable and reliable
  • 💾 Full Cache Support: 100% cache availability for improved efficiency and cost savings
  • 🌍 Web Supported: Claude account also work on the Claude mirror

🔗 Visit: https://flapcode.com

Features

Fingerprint Support

You can use creepjs and browserleaks to test fingerprint modification effects.

  • User-Agent: Modify the browser's navigator.userAgent, navigator.platform, navigator.userAgentData and Client Hints information.
  • Operating System
  • Audio
  • Plugins: After removal in version 133+, the browser returns a fixed plugin list.
  • CPU Cores
  • Memory
  • WebGL Image
  • WebGL Metadata: Modify GPU vendor and graphics card model (currently only supports Linux).
  • Fonts
  • Canvas Image
  • Canvas Text
  • ClientRects
  • WebRTC
  • Language Support
  • Timezone Support

Automation Support

Optimized for automation scenarios, offering the following features:

  1. Fake Shadow DOM Support
    Adds the fakeShadowRoot property, equivalent to the shadowRoot property, enabling access to Closed Shadow Root for easier automation handling.

  2. Avoid CDP Detection
    Prevents Chrome DevTools Protocol (CDP) detection when invoking Runtime.enable, enhancing stealthiness for automation tools.

  3. Webdriver
    Sets navigator.webdriver to false to avoid detection of automation tools.

  4. Headless
    Only changes User-Agent from HeadlessChrome to Chrome. Other headless characteristics remain unchanged, use with caution.

Enabling Fingerprint Features with Command Line Arguments

You can enable or customize fingerprinting and privacy protection features by passing command line arguments when launching the browser:

Command Line Argument Description Examples
--fingerprint Specifies the fingerprint seed. When enabled, most fingerprinting features take effect 32-bit integer
--fingerprint-platform Specifies the operating system type windows, linux, macos
--fingerprint-platform-version Specifies the operating system version Uses default version if not specified
--fingerprint-brand Specifies the browser brand in User-Agent and User-Agent Data Chrome, Edge, Opera, Vivaldi (default is Chromium if not specified)
--fingerprint-brand-version Specifies the version number for the browser brand Uses default version if not specified
--fingerprint-hardware-concurrency Specifies the number of CPU cores Integer value (randomly generated from fingerprint seed if not provided)
--disable-non-proxied-udp Specifies WebRTC policy, by default non-proxied UDP connections are disabled Recommended to keep default setting
--lang Sets the browser language Language code (e.g., en-US)
--accept-lang Sets the languages accepted by the browser Language codes (e.g., en-US,en)
--timezone timezone Timezone (e.g., Asia/Shanghai, UTC)
--proxy-server proxy server http, socks proxy (password authentication not supported)
--disable-spoofing Disable specific fingerprint spoofing (Chrome 144+) Comma-separated values: font, audio, canvas, clientrects, gpu
--fingerprint-gpu-vendor Customize GPU vendor for WebGL fingerprinting (Removed in Chrome 144) Vendor string. Removed in Chrome 144
--fingerprint-gpu-renderer Customize GPU renderer/model for WebGL fingerprinting (Removed in Chrome 144) Renderer string. Removed in Chrome 144
--disable-gpu-fingerprint Disable GPU fingerprint (Removed in Chrome 144, use --disable-spoofing=gpu instead) Removed in Chrome 144

New Command Line Arguments in Chrome 139

GPU Fingerprinting Parameters

Note: --fingerprint-gpu-vendor and --fingerprint-gpu-renderer have been removed in Chrome 144. Use --disable-spoofing=gpu to disable GPU fingerprint spoofing instead.

Starting from Chrome 139, GPU fingerprinting is automatically enabled when using the --fingerprint parameter. The following optional parameters allow for custom GPU configuration:

  • --fingerprint-gpu-vendor (Optional)

    • Customize the GPU vendor string for WebGL fingerprinting.
    • Examples: Intel Inc., NVIDIA Corporation, AMD, Apple
    • If not specified, GPU vendor will be automatically generated based on the fingerprint seed.
  • --fingerprint-gpu-renderer (Optional)

    • Customize the GPU renderer/model string for WebGL fingerprinting.
    • Examples: Intel Iris OpenGL Engine, NVIDIA GeForce GTX 1060, AMD Radeon RX 580
    • If not specified, GPU renderer will be automatically generated based on the fingerprint seed.

User-Agent Customization Command Line Arguments (Chrome 131)

Chrome 131 introduced two command line arguments for advanced customization of User-Agent and User-Agent Data:

  • --fingerprint-brand

    • Specifies the browser brand used in User-Agent and User-Agent Data.
    • Supported values: Chrome, Edge, Opera, Vivaldi, or custom brand names.
    • If not specified, the default brand is Chromium.
  • --fingerprint-brand-version

    • Specifies the version number for the specified brand.
    • Default values: Chrome, Edge, Opera, Vivaldi all provide default versions, custom versions can also be passed.

These arguments enhance browser environment simulation capabilities, suitable for automation and testing scenarios. If --fingerprint-brand is not specified, the default brand will be used.

New Features in Chrome 142

  1. Updated UserAgent and UserAgentData Fingerprint Implementation

    • Improved fingerprint implementation for navigator.userAgent and navigator.userAgentData.
  2. Updated Audio Fingerprint Implementation

  3. Updated Canvas Fingerprint Implementation

    • Improved Canvas fingerprint modification for better anti-detection.
  4. GPU Fingerprint Disable Option

    • GPU fingerprint may have issues in some scenarios. Use --disable-gpu-fingerprint parameter to disable GPU fingerprint if needed.
    • Removed in Chrome 144. Use --disable-spoofing=gpu instead.

New Features in Chrome 144

  1. Removed GPU Fingerprint Parameters

    • Removed --fingerprint-gpu-vendor, --fingerprint-gpu-renderer, and --disable-gpu-fingerprint parameters.
  2. New --disable-spoofing Parameter

    • A comma-separated parameter to selectively disable specific fingerprint spoofing.
    • Available values: font, audio, canvas, clientrects, gpu
    • Example: --disable-spoofing=font,gpu disables font and GPU fingerprint spoofing.

Usage Examples

Here are command line examples for several common use cases:

Basic Usage

./chrome --fingerprint=1000 --user-data-dir=/tmp/chromium/1000 --timezone="America/Los_Angeles" --proxy-server="your_proxy_server_address"

Customizing User-Agent

chrome.exe --fingerprint=2023 --fingerprint-platform=macos --fingerprint-platform-version="15.2.0" --fingerprint-brand="Edge"  --user-data-dir=%TEMP%\chromium

Fingerprint Testing

Testing Platform Status
CreepJS ✔️ 51.5%.
PixelScan ✔️ Pass audio fingerprint detection.
BrowserScan ✔️ GPU fingerprint may have issues.
BrowserLeaks ✔️ Supports multiple fingerprint leak detection
Cloudflare ✔️
‣ Turnstile ✔️

User Communication

Scan the QR code to join QQ groups to communicate with other users

If you need Chrome customization development services or are looking for custom development opportunities, please join the development customization group (QQ group 1055930761)

Sponsors

IPdodo

A trusted proxy IP provider that delivers all-in-one solutions of high-anonymity, high-speed, and secure proxy IPs combined with S5 forwarding services, tailored for cross-border e-commerce, social media operations, web scraping, data collection, and global business growth.

Offer: Register today to get 1GB of free residential proxy traffic.

  • Invitation Code: ATUQ3Q0O

🔗 Register Now

IPFly

A cost-effective IP service provider with high-quality IPs and 7x24 customer support.

Offer: Register via exclusive link to enjoy 10% off sitewide.

  • Discount Code: adryfish
  • Invitation Code: 9A2WLGX9

🔗 Register Now

RapidProxy

A high-performance proxy provider offering clean residential and native static ISP IPs with high anonymity, fast speeds, and low block rates. Designed for web scraping, social media automation, e-commerce, and global business operations.

Offer: Free trial available with non-expiring residential proxy traffic. Highlight: Native static IPs with low detection and stable performance.

  • Discount Code: adryfish (10% OFF)

🔗 Register Now

OKKproxy

🔥 OKKproxy offers 80 million global residential IPs as a first-hand provider, with TB-level bulk purchasing as low as $0.4/GB.

  • 🌐 Coverage: Rotating residential proxy IPs / overseas mobile IPs / static residential IPs.
  • 🎀 Proxy Types: Supports HTTP(S) and SOCKS5 proxies.
  • 🎉 Use Cases: Suitable for e-commerce, social media, multi-accounting, and SEO.
  • 🤝 Established: 3 years.

🔗 Register Now

Credits

License

BSD-3-clause. See LICENSE

Frequently asked questions

Is fingerprint-chromium free to use?

fingerprint-chromium is open source under the BSD-3-Clause licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does fingerprint-chromium do?

An open source fingerprint browser based on Ungoogled Chromium. 指纹浏览器 隐私浏览器

What is fingerprint-chromium written in?

fingerprint-chromium's source is publicly available at https://github.com/adryfish/fingerprint-chromium, with 3,223 GitHub stars.