Guides
Anti-bot & JS Rendering
What Thunderbit handles automatically — and what it doesn't
A lot of the friction in web extraction comes from infrastructure: rotating proxies, solving CAPTCHAs, rendering JavaScript, dealing with geo blocks. Thunderbit absorbs that so your code stays focused on the data.
What we handle
- JavaScript rendering — SPAs, hydration, async-loaded content (see Render Modes)
- CAPTCHA / bot walls — automatic solving on supported challenge types
- Proxy rotation — residential and datacenter pools, rotated per request
- Geo routing — pin a country with
countryCode(e.g."DE","JP") - Anti-fingerprinting — varied user agents, headers, viewport
- Retry on transient failures — DNS / connection / 5xx errors
What we don't handle
- Authenticated sessions — you can pass cookies via
headers, but interactive login flows aren't supported - Sites blocking us by domain reputation — rare, but possible; reach out for enterprise allowlisting
robots.txtoverrides — honored by default; enterprise plans can request override with proof of authorization
Knobs you can turn
| Parameter | When to set |
|---|---|
renderMode | Page needs JS to render |
waitFor | SPA hydration takes longer than default |
countryCode | Geo-aware site (pricing, search results) |
headers | Custom auth tokens or cookies |
This page is being expanded with troubleshooting steps — check back soon.