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.