curl_cffi
Make HTTP requests with browser connection profiles. The current 30-site pass uses direct Chrome150 mode without JavaScript.
29 September 2026 UTC · frozen public-30-v1 · no proxy
Direct Chrome150 HTTP mode on all 30 targets
14 of 30 bodies met unchanged checks. curl_cffi 0.16.3 used fresh Session.get requests with default Chrome150 headers, no added Google Referer, three ordinary redirects maximum and no retries, browser or JavaScript. Inspect all 240 records across eight tools, including HTTP 200 content failures and one empty checked-text response, exact headers, dates, hashes and PSS. Raw bodies and logs stay private; Scrapling’s wrapper pass remains separate.
Compare all 30 targets across eight toolsPublished test history
These May 2026 runs used one network without a proxy. Their pass counts describe those older attempts, not how the tool will perform today.
| Mode | Date | Version | Observed result | Network |
|---|---|---|---|---|
| curl cffi | 2026-05-24 | 0.15.0 | 5/21 required-content checks | No proxy |
Where it fits
First pick for static-page scraping at scale when you don't want a browser: you get real fingerprint benefits at HTTP-client speed and cost. Add proxies for IP reputation and a browser tier for JS challenges.
This guidance comes from the May 2026 review. Check a recent run before choosing for production.
What it can do
- Use a proxy
- Fetch HTML
Capabilities are catalog notes, not outcomes from the benchmark above.
Project record
- Type
- Fetch pages
- Ecosystem
- python
- Repo check
- 2026-05-23
- License
- MIT
Repository metadata is a dated snapshot, not a live health guarantee.
See how we validate pages, including what a pass does and does not mean.