preferred on
Points of Focus
- Cloudflare launched Kitesurf, a browser designed specifically for AI-agent workloads.
- Cloudflare’s 14-URL test showed lower CPU and memory use than Chromium, but slower completion times.
- Kitesurf supports Chrome DevTools Protocol while dropping several full-browser features.
Cloudflare launched Kitesurf on Aug. 6, a cloud-hosted browser built specifically for AI agents to navigate websites, extract content, render pages and complete web-based tasks. Rather than competing for Chrome’s human users, Cloudflare is testing a different premise: whether autonomous software needs the weight and feature set of a full Chromium browser in the first place.
Agents should use tools that excel at what’s important for an AI model. Kitesurf is Cloudflare’s new stateless, highly scalable, and cost-effective web browser that runs entirely on top of Workers and was designed specifically for the Agentic Cloud. https://t.co/4579J174by…
— Cloudflare (@Cloudflare) August 6, 2026
Chrome still accounted for 68.22% of worldwide browser usage in July 2026, according to StatCounter. Cloudflare had been scaling browser automation around headless Chrome before Kitesurf introduced a non-Chromium option. In April, Browser Run gave agents access to on-demand headless Chrome, while a May rebuild on Containers raised concurrent browser capacity to 120.
Kitesurf changes the underlying browser engine while retaining Chrome DevTools Protocol compatibility. That lets Puppeteer, Playwright and other CDP-based tools connect without developers replacing their existing automation interface.
Kitesurf targets Chromium’s compute overhead
Cloudflare built Kitesurf in 12 weeks around a narrower set of browser functions. The design drops human-facing features such as themes, extensions and device sync, while prioritizing page structure, JavaScript execution, screenshots, HTML extraction and isolated sessions.
That narrower design produced a large resource gap in Cloudflare’s own tests. Across five runs on a 14-URL corpus, Kitesurf used 380 milliseconds of CPU time for screenshots versus 1,173 milliseconds for Chromium, while memory use was 57.8 MiB versus 271.0 MiB. For HTML extraction, memory fell to 39.4 MiB from 273.7 MiB.
The trade-off is speed. Kitesurf took 1,148 milliseconds to complete screenshot jobs compared with 637 milliseconds for Chromium, and 820 milliseconds for HTML extraction versus 472 milliseconds. The results favor Kitesurf on resource use, while Chromium remains faster at completing the same tasks.
Kitesurf beta still leaves Chromium with key advantages
Cloudflare says Kitesurf already passes more than 215,000 Web Platform Tests, but the company also acknowledges that standards tests don’t guarantee real-world browser compatibility. Kitesurf isn’t yet suited to video playback, WebGL, bot-challenge handshakes that depend on real TLS fingerprints, or long authenticated sessions that require persistent state.
For workloads that require those capabilities, Cloudflare still recommends Browser Run’s default Chromium browser. Cloudflare is keeping Chromium as Browser Run’s default for those unsupported workloads while Kitesurf remains in beta. Cloudflare plans to open-source Kitesurf once it is ready. The project remains only months old, with its first commit dating to May 2026.
Share
Most read articles
