How stealth works
Bot detection is the set of checks that a site runs to tell a person from a program. A site that suspects automation can block the request with 403 or an "access denied" page, send the browser into a loop of redirects, or show a challenge such as a CAPTCHA. Sites check several things at once, so one fix rarely clears every block. Each Steel stealth feature handles one kind of check.
What to expect
Stealth lowers the chance that a site blocks a session. It cannot promise that a site lets the session in. Some sites block every browser that they think is automated, and some forbid automation in their terms.
By default, Steel gives a session a fingerprint whose traits agree, and the session uses a datacenter address. CAPTCHA solving is off. You add the rest when a site needs it: a residential proxy, CAPTCHA solving, a mobile device, human-like input, a dedicated IP, or Stealth Browser on Enterprise. Proxy bandwidth and CAPTCHA solves have their own prices, so turn them on for the sites that block you, not for every session.
What sites check
| Check | What the site looks at | Steel feature |
|---|---|---|
| IP address | Where the request comes from: a datacenter or a home connection, and which country | Proxies, dedicated IPs |
| Browser fingerprint | What the browser reports about itself, and whether the parts agree | Fingerprints, mobile sessions, Stealth Browser on Enterprise |
| Behavior | How the mouse moves and how keys are typed | Human-like input over CDP, with stealthConfig. |
| Challenges | Whether the visitor can pass a test, such as a CAPTCHA | CAPTCHA solving, a person in the live view |
IP address
A site sees the IP address of every request. A session without a proxy uses the address of the machine that runs it, which is a datacenter address. Many sites trust datacenter addresses less than home connections, and some block them. A site can also show different content, or none, to visitors from a given country.
Steel proxies route the session through a residential address, in the United States by default or in a country that you choose. Each session gets a new address. You can also bring your own proxy.
Some sites check that a returning account comes from the same place. A login that comes from a new address each time can trigger a new check. A dedicated IP keeps one address from one session to the next.
Browser fingerprint
A fingerprint is what a browser reports about itself: the user agent, the screen and window size, the device, and many other traits that a script can read. A site compares these traits with each other and with what a real browser reports. A desktop browser that claims a phone's user agent does not match, and a site can see that.
Steel applies a fingerprint to every session by default, so the traits that the session reports agree with each other. A mobile session reports a whole mobile device, not only a mobile user agent. If your own code sets the fingerprint, you can turn Steel's off. Fingerprints shows how.
A session that starts from a profile or sets its own user agent gets no fingerprint from Steel, as Fingerprints explains.
Some sites still detect a browser that has Steel's fingerprint. For those sites, a session on Enterprise can run on Stealth Browser, Steel's own Chromium fork. Stealth Browser sets the fingerprint inside the browser, instead of having Steel inject it.
Behavior
A script can move the mouse in straight lines, click without moving it, and type at a fixed speed. A person does not. Some sites watch the input on a page and score how human it looks.
Set stealthConfig.humanizeInteractions to true when you create the session, and Steel moves the mouse along a curved path and adds a short random pause before each key event. The option changes only the mouse and keyboard input that your code sends over CDP, for example with Playwright or Puppeteer. It does not change the input of Commands, computer actions, the MCP server or the CLI. Session configuration lists it with the other stealth options.
Challenges
A challenge is a test that the site asks the visitor to pass. Some are visible, such as a checkbox, a set of images or a slider. Others run in the background and score the visitor without a widget.
With CAPTCHA solving on, Steel detects a challenge on the page, solves it, and checks that the page accepted the answer. It solves common types, such as reCAPTCHA and Cloudflare Turnstile. It does not solve some others, such as DataDome and FunCAPTCHA. For those sites, work on the other checks so that the challenge does not appear.
Prevention comes first. A session with a consistent fingerprint and a residential address triggers fewer challenges, and CAPTCHA solving handles the ones that still appear. When a challenge needs a person, someone can solve it in the live view. Hand control to a human shows how.
How to tell what blocked you
A few seconds after a session ends, Steel adds signals for what it saw during the run. A block shows up as bot_detection_triggered, a CAPTCHA as captcha_encountered, and a proxy failure as proxy_connection_failed. A session with no signals can still have been blocked. Signals reference lists every signal and the limits of detection.
To see the block itself, watch the session's recording. It shows the page that the site served, such as an access-denied page or a challenge.
Then change one thing at a time. Get past bot detection gives the order in which to try the features.