How anti-detection works
Santiago hides the fact that you’re using an automation-friendly browser by changing your fingerprint deep inside the browser engine, not with surface-level tricks that detection sites can spot. This page explains why that matters and what happens automatically when you launch a profile.
What a fingerprint is
Section titled “What a fingerprint is”Every website you visit can read dozens of small details about your browser and device: your operating system, screen size, graphics card, installed fonts, time zone, language, and more. Taken together, these details form a fingerprint that can identify you even without cookies.
If you open many accounts from one ordinary browser, every account shares the same fingerprint — and sites quietly link them together. Santiago gives each profile its own complete, believable fingerprint so your accounts look like they come from separate, real people on separate devices.
Why Santiago is hard to detect
Section titled “Why Santiago is hard to detect”Most anti-detect tools change the fingerprint by injecting JavaScript that overrides what the browser reports. The problem is that these overrides leave traces: a detection site can notice that a value was patched after the fact, and flag the browser as automated.
Santiago is built on Camoufox, a customized build of Firefox. The fingerprint changes happen inside the browser engine itself, at the level where the browser is written (native C++ code) — before any web page can look. There is no JavaScript layer sitting on top, so there’s nothing for a detection script to catch in the act.
| Approach | How it spoofs | How easy to detect |
|---|---|---|
| Typical anti-detect browser | JavaScript overrides on top of the browser | Easier — the patch is visible to scripts |
| Santiago (Camoufox engine) | Native changes inside the browser engine | Harder — the values look genuine |
A consistent fingerprint per profile
Section titled “A consistent fingerprint per profile”When you create a profile, Santiago generates a fingerprint that is statistically plausible — it’s based on real-world data about which browser and device combinations actually exist, so your profile blends in with genuine traffic instead of standing out.
Just as important, that fingerprint stays consistent:
- All the values match each other (for example, a macOS profile reports macOS-style fonts, voices, and graphics — not a random mix).
- The same profile keeps the same fingerprint every time you launch it, so the “person” behind the account doesn’t change identity between sessions.
You can generate a fresh fingerprint with one click, or fine-tune individual fields yourself. See Generate a fingerprint and Fingerprint parameters for the full list of what you can control.
What’s handled automatically
Section titled “What’s handled automatically”When you launch a profile, Santiago configures the difficult fingerprint surfaces for you. You don’t need to set these up by hand:
| Surface | What Santiago does |
|---|---|
| Canvas | Makes the profile’s canvas output consistent so it looks like a single real device. |
| WebGL | Reports a believable graphics card vendor and renderer. |
| Audio | Produces a stable, per-profile audio fingerprint. |
| Fonts | Presents a font list that matches the profile’s operating system. |
| WebRTC | Controls how your network identity is exposed (see modes below). |
| Time zone & language | Matched to the profile, and auto-aligned to your proxy when enabled. |
If you use a proxy with location matching turned on, Santiago can automatically align the profile’s time zone, language, and location with the proxy’s real-world location, so everything tells the same story. See Proxies and Geolocation.
WebRTC modes
Section titled “WebRTC modes”WebRTC is a common way for sites to discover your real IP address even behind a proxy. Each profile lets you choose how it behaves:
| Mode | Behavior |
|---|---|
real | Reports your actual network identity. |
fake | Reports your proxy’s public IP instead of your real one, so there’s no leak. |
disabled | Turns WebRTC off entirely. |
Human-like behavior with humanize
Section titled “Human-like behavior with humanize”A real person doesn’t move the mouse in straight lines or click instantly. When you enable humanize on a profile, Santiago moves the cursor along smooth, curved (bezier) paths instead of teleporting it, so on-page activity looks like a human rather than a script. This is especially useful when you automate a profile.
Where to go next
Section titled “Where to go next”- Generate a fingerprint — create a plausible fingerprint in one click.
- Fingerprint parameters — every field you can adjust.
- Geolocation — match time zone and location to your proxy.
- Create and edit profiles — put it all together.
- Automation overview — drive profiles programmatically with humanized behavior.