Skip to content

Blend in.
Stay clear.

Clearcote is an open-source, de-Googled Chromium with fingerprint control built into the engine — one coherent, plausible identity instead of an accidentally unique one. A drop-in for Playwright & Puppeteer.

Star on GitHub 41 Run the test

Free & open source (BSD-3) · on npm, PyPI & NuGet · no phone-home · every change is a readable patch.

clearcote · python
$ pip install clearcote

from clearcote import launch

# one coherent identity from a single seed
browser = launch(fingerprint="acct-1", geoip=True)
page = browser.new_page()
page.goto("https://abrahamjuliot.github.io/creepjs")

# navigator.webdriver = false · one real machine · 0% detected

Live from your browser

  • navigator.webdriver…
  • UA ↔ platform…
  • hardware signals…
Run the full fingerprint test

Built on & works with

Chromium 150ungoogled-chromiumPlaywrightPuppeteerBrave farblingadryfish
0

Chromium base

0/6

CreepJS checks passed

0

Trackers & phone-home

Features

Built for builders

Engine-level controls with the ergonomics you already know.

Engine-level, not script injection

Identity controls are compiled into the binary — not bolted on via injected JavaScript that's brittle and self-revealing. Pages see native behavior, not a patched DOM.

ChromiumungoogledClearcote patchesReproducible buildBrowser + SDK

Coherent per-site identity

Signals are controlled together so they stay consistent and stable per site — inspired by Brave's farbling.

Drop-in automation

Native Playwright & Puppeteer support. Same APIs — just point them at the Clearcote binary.

De-Googled base

ungoogled-chromium removes Google services, telemetry and integration. Privacy by default.

Tunable fingerprint flags

Seed, platform, brand, GPU, hardware concurrency, timezone, geolocation — all command-line switches.

Signals it controls

Canvas 2DWebGL renderer (session-constant GPU)WebGL getParameter limitsWebGPU adapterAudioContextFontsTimezonenavigator.language / primary languageUser-Agent + UA-CHTLS ClientHello persona (JA3/JA4)hardwareConcurrencydeviceMemoryScreen geometryStorage quotaClient rectsnavigator.webdriverHeadless hintsClosed shadow rootsWebRTC proxy-IPnavigator.getBatterynavigator.connectionKeyboard layout mapgetScreenDetails / multi-screenCSS pointer/hover mediaAudioContext metadatanavigator.shareURL drive-letter OS coherenceIn-browser AI agentMediaCapabilities codecsenumerateDevicesUA-CH bitness/WoW64
Quickstart

A drop-in for your stack

Your existing automation, pointed at Clearcote, hitting any site or fingerprint check. Migration is a one-line import.

from clearcote import launch

browser = launch(fingerprint="seed-123", platform="windows")
page = browser.new_page()
page.goto("https://abrahamjuliot.github.io/creepjs/")
browser.close()
Ecosystem

One browser, every way to drive it

The SDK is the front door — but agents, infrastructure and plain humans all steer the same verified binary.

For Playwright & Puppeteer

SDKs

launch() returns a standard Playwright Browser in Python or Node — migration is a one-line import.

SDK docs

For AI agents

MCP server

Point Claude Desktop, Cursor or Cline at Clearcote — about twenty tools drive one shared stealth browser. npx -y clearcote-mcp

MCP docs

For infrastructure

Docker · CDP endpoint

docker run a standing stealth endpoint on :9222 — attach Playwright, Puppeteer or browser-use with no code change. navigator.webdriver stays false by construction.

Deployment docs

For humans

Profile Manager

A Windows desktop app: create, organize and launch persistent identities as interactive windows. No code at all.

About the app

Go deeper: Canvas bridge (real-GPU readbacks, experimental) · Real device profiles · Capture your own machine

Why Clearcote

Why Clearcote instead of the others?

Most anti-detect browsers are closed, paid binaries that rewrite your fingerprint with injected JavaScript or CDP hooks — brittle, self-revealing, and asking you to trust code you can't read. Clearcote inverts every one of those choices.

Source

✓100% open — every change is a readable patch

Closed binary

Price

✓Free (Pro optional)

Paid subscription

How signals change

✓Compiled into the C++ engine — invisible to the page

Injected JS / CDP hooks (detectable artifacts)

Coherence

✓One seed → a whole consistent machine; JS identity and the real TLS/JA3/JA4 + HTTP-2 stack agree

Per-surface values that disagree — with each other or the network

Trust model

✓Signed, checksummed, reproducible from source

“Trust us”

Automation

✓Drop-in Playwright / Puppeteer — returns a standard Browser

Proprietary API / GUI profiles

Real identities

✓Import a real machine and verify it loaded

Rare / unverifiable

Privacy

✓De-Googled, zero telemetry / phone-home

Varies

The deeper reason it holds up: how bot detection actually works.

And the “real identities” row is literal — wear a machine from the open profiles library, or manage them in the Profile Manager app.

Pricing

Free forever. Pro keeps it alive.

The free build is fully functional and reproducible from source — it is not crippled to sell you Pro. Pro funds the upkeep and gets you a maintained build plus a direct line to the person who makes it.

Free

$0

Open source, forever.

  • 100% open source (BSD-3-Clause)
  • Reproducible & verifiable from source
  • All public patches — full fingerprint control
  • Windows + Linux builds
  • New Chromium majors land ~2 months after release (Pro gets them first)
  • Community support via GitHub issues
Get started

Pro

Supports development

$49/month

Billed monthly in USD. Cancel anytime.

Everything in Free, plus:

  • Latest builds first. A new Chromium major (e.g. 150) is available to you the day it ships — the free build gets it later, roughly 2 months after release.
  • The maintained, always-current build — latest Chromium and the newest anti-detection patches, kept up to date for you.
  • A few extra stealth patches I keep private so they aren't trivially copied. Being blunt: this build is therefore not reproducible from public source — the free build is.
  • Unlimited concurrency — while in beta. No cap today; fair-use limits may come later, with notice.
  • Direct email support from me, the owner. You email, I answer.
Get Pro

Straight talk about what you're paying for.

Clearcote is a Chromium fork. Keeping it current with upstream, porting the anti-detection work to every new version, testing it, and building for two platforms is a lot of ongoing effort — mostly mine. $49/month pays for that. You get a build that stays up to date without you lifting a finger, a handful of patches I don't publish, and a direct line to the person who builds it. That's the whole deal — no lock-in, no dark patterns, and the free build stays open and reproducible.

Don't trust us. Verify us.

Every release is checksummed and GPG-signed against a pinned key. Import it, confirm the fingerprint, check the signature — then run a binary you proved is exactly what was built.

Pinned signing key

CA96F185 F96A 693A EDB3 AC1F CB00 D851 B7A8 6B0F

How to verify a release

Inspiration & credits

Chromium

BSD-3-Clause

The engine.

ungoogled-chromium

BSD-3-Clause

The de-Googled base and patch tooling.

fingerprint-chromium

BSD-3-Clause

Pioneering engine-level fingerprint controls (by adryfish).

Brave

Inspiration

The per-site deterministic 'farbling' model.

Camoufox

Inspiration

A sibling open anti-detect browser (Firefox-based).

Questions

Questions, answered

Is it really open source?

Yes — BSD-3-Clause. Every patch is human-readable and the free build is reproducible from source.

What do I actually get with Pro ($49/mo)?

A maintained, always-current build (latest Chromium + newest anti-detection patches), a few extra stealth patches I keep private, unlimited concurrency while in beta (fair-use limits may come later, with notice), and direct email support from me, the owner. Being blunt: it mostly funds the ongoing upkeep. The free build is fully functional and not crippled to sell Pro.

Is the Pro build reproducible too?

No — and I won't pretend otherwise. Pro includes a few patches I don't publish, so it can't be rebuilt from public source. The free build stays 100% open and reproducible; that promise doesn't change.

How is this different from JS stealth plugins?

Those overwrite navigator properties with injected JavaScript, which is brittle and self-revealing. Clearcote changes the C++ engine, so values come from Chromium's own code paths.

Can I drive it from an AI agent?

Yes — that's what the MCP server is for. Point Claude Desktop, Cursor or Cline at it (npx -y clearcote-mcp) and about twenty tools drive one shared stealth browser; the persona is set once via environment config, so every agent session lands in the same verified identity. Details are in /docs/mcp.

Which platforms are supported?

Windows x64 today. More platforms are on the roadmap.

More in the full FAQ.

Learn

Go deeper

Documentation

Install, the SDKs, fingerprint flags, deployment and verification.

Research

Deep-dives on bot detection, fingerprinting and how the browser is built.

Q&A & concept map

Plain-English answers and a connected map of every stealth concept.

Alternatives

How Clearcote compares with other anti-detect browsers and stealth tools.