Product · Browser
A browser built for agents. It runs page scripts. It speaks Chrome's protocol. It uses a twenty-fourth of the memory.
Webfold has its own browser engine. It runs page scripts. Your Playwright or Puppeteer code connects over CDP unchanged. It passes all 1,928 Lexbench tasks. Chrome scores 1,926 in the benchmark's own run.
See it work
Try it from wherever you work.
1webfold headless serve 9222
What you get
What Browser does.
Passes the agent-browser benchmark
1,928 of 1,928 Lexbench tasks: 1,740 protocol and driver tasks across 13 drivers plus raw CDP, and 188 web-platform tasks that are judged by what the page actually does. [The result and its limits](/benchmarks/browser-compatibility/).
A fraction of Chrome's cost
On the same scripted task: 8 ms to start against 240 ms, 106.6 tasks a second against 12.1, 30 MB against 724 MB. [Head to head](/benchmarks/headless-engine/).
Same answers as Chrome
68 of 68 ordinary page-script expressions, and 300 of 300 more, return exactly what Chrome returns, over raw CDP.
Logins that work
Generic sign-in, one-time codes sealed in a local secret store, and profiles that keep a session across restarts.
Debugger, network and service workers
Breakpoints and stepping, request and response interception, authentication challenges, push and sync events, per-context storage.
Ask what it supports
`headless capabilities` lists every protocol method as implemented, a named no-op, or unsupported. No silent success.
Real Chromium when a page needs it
`scrape --render` extracts from a Chromium you run, in a fresh isolated context per request, through a proxy that refuses private addresses.
How it works
Three steps.
- 1
Serve
Start the engine on a port. It answers in about 8 ms.
- 2
Connect
Point Playwright, Puppeteer, Selenium or raw CDP at it.
- 3
Drive
Navigate, click, fill, wait and read, as you would with Chrome.
Limits up front.
Know the limits
- Not yet in the engine: canvas drawing, WebGL, web workers, WebAssembly and media playback. BigInt works. Pages that depend on them need a real Chromium, which Webfold can connect to.
- It answers 242 of Chrome's 640 protocol commands: every stable command automation drivers use, not the DevTools-frontend and device-emulation domains.
- Screenshots use Webfold's own renderer. They are stable for regression tests and are not pixel-identical to Chrome.
- Getting past bot protection is not something to plan around yet.
Keep reading.
FAQ
Questions.
Is it a Chrome replacement?
For agent work, usually yes: it runs the page, answers the protocol your driver speaks and costs far less per session. Keep Chrome for pages that need canvas, WebGL, workers or WebAssembly, and for pixel-exact screenshots.
Is Lexbench your benchmark?
No. It is published by Lexmount, who make a competing engine. We ran their 1,928 tasks against Webfold; every attempt passed in three full runs. Their published run has Chrome at 1,926 and the other lightweight engines between 762 and 1,556.
Use Browser with Webfold.
Run the command-line tool today. Join the waitlist for the hosted API.