Jerem Flow

Camoufox vs browserless — evading bot detection the honest way

· 2 mins read · #browser #scraping #privacy #self-hosting #ai-agents #anti-bot

A stock headless browser is detectable. A stealth browser is harder to spot. Here's the difference, and where I draw the line. 🦊

The problem: headless browsers are detectable

In my headless browser setup, I run a stock headless Chromium. It works great for most sites — but it's detectable: navigator.webdriver is set, the user agent says HeadlessChrome, and a determined site can tell it's automated. For hardened sites with strict bot protection, that's a wall.

The two approaches

browserless (stock) Camoufox (stealth)
What it is headless Chromium a patched Firefox that hides automation
Detectability detectable designed to blend in
Best for most sites, JS-heavy pages hardened sites with strict bot protection
Setup simple a bit more involved

browserless is the workhorse: a real Chromium I can drive, good for the vast majority of sites. Camoufox is the specialist: a Firefox fork engineered to look like a normal browser — it spoofs the automation signals that give stock headless browsers away.

Why Camoufox works

Camoufox is built to defeat the fingerprinting that outs headless browsers. It presents a consistent, human-like browser fingerprint and hides the automation markers. The result: on sites that block stock headless browsers, Camoufox often gets through where browserless can't.

The honest line

This is where I'm careful. There's a difference between:

  • Legitimate use — reading a page that's technically accessible, automating my own workflows, accessing public content that a normal browser could see.
  • Bypassing a site's terms — defeating access controls, scraping content the site explicitly forbids, or evading a paywall.

I use stealth browsing for the first, not the second. A stealth browser is a tool for not being needlessly blocked — not a license to ignore a site's rules. If a site doesn't want automated access, I respect that and move on.

The guardrail isn't technical, it's judgment: stealth is for blending in, not for breaking in.

When to use which

  • Most sites → browserless. It's simpler and good enough.
  • Hardened sites, legitimate access → Camoufox, when a stock browser is blocked.
  • Anything that's clearly against a site's terms → don't. Respect the rules.

In short

A stock headless browser (browserless) is detectable; a stealth browser (Camoufox) is designed to blend in. I use each where it fits — and I keep the honest line: stealth for not being needlessly blocked, never for bypassing a site's terms.

See also: Giving Hermes a headless browser (and a VPN) for the web — the setup this note builds on.

← Back