.png){kind=logo}
Lower resource use: Kitesurf can use up to 7× less memory than Chromium for certain browser tasks.
Built for agents: Kitesurf focuses on extraction, screenshots, PDFs, and browser automation rather than human-focused browser features.
Clear trade-offs: Kitesurf uses fewer resources but can take longer than Chromium for some tasks and lacks video, WebGL, and persistent sessions.
A browser built for humans carries many features that an AI agent does not need. Tabs, themes, extensions, device sync, smooth page movement, and exact visual output all add weight. Cloudflare took a different route with Kitesurf, a new browser built for AI agents.
Kitesurf runs on Cloudflare Workers and uses V8 isolates instead of a full Chromium setup. The result targets lower CPU use, lower memory use, lower cost, and better scale for short AI tasks.
Cloudflare launched Kitesurf on August 6, 2026, as a free beta inside Browser Run. The company calls it a stateless and highly scalable browser for AI agents. Kitesurf focuses on token count, context windows, scale, performance, and cost rather than the features that matter most to human users.
It also gives each page its own cookie jar and uses a separate SandboxOutbound Worker for network access. That design adds isolation and limits direct network access from other parts of the browser.
Kitesurf can render web pages, extract HTML, take screenshots, create PDFs, and support short browser tasks. It can also work with Puppeteer, Playwright, chrome-remote-interface, and AI agents that use the Model Context Protocol (MCP) and Chrome DevTools Protocol (CDP). Current clients can use Kitesurf with the browser=kitesurf parameter, so a new browser automation stack does not need to start from scratch.
The clearest Kitesurf advantage appears in resource use. Cloudflare tested five Browser Run Quick Action runs across a 14-URL set and compared Kitesurf with a warm Chromium pool. For screenshots, Kitesurf used 380 ms of CPU versus 1,173 ms for Chromium, a 3.1× lower figure. For HTML extraction, Kitesurf used 229 ms versus 877 ms, or 3.8× less CPU.
Memory results show an even wider gap. A screenshot used 57.8 MiB with Kitesurf versus 271.0 MiB with Chromium, a 4.7× lower figure. HTML extraction used 39.4 MiB versus 273.7 MiB, which gave Kitesurf a 7.0× memory advantage. These figures explain the focus on large agent workloads, where many short browser tasks can create a heavy infrastructure bill.
Also Read - 10 Real-World Loop Engineering Examples Powering Modern AI Agents
Kitesurf does not win every test. Chromium finished the screenshot task in 637 ms, while Kitesurf took 1,148 ms. That made Kitesurf 1.8× slower in wall time. For HTML extraction, Chromium took 472 ms and Kitesurf took 820 ms, which made Kitesurf 1.7× slower.
The trade-off has a clear reason. Chromium can use a just-in-time system that has already processed the same page, while Kitesurf uses a cold software renderer for these tests. Rasterization and JPEG or PNG image conversion also add time. Kitesurf therefore aims at a different goal: lower CPU and memory use rather than the fastest result on a single task.
Kitesurf does not replace Chromium for every site or workflow. It cannot yet play video, render WebGL, complete a bot challenge with real TLS fingerprints, or support a long authenticated session that needs persistent state. Browser Run still offers its default Chromium option for such cases.
Compatibility has improved fast. Cloudflare reports that Kitesurf passes more than 215,000 Web Platform Tests, and its team adds hundreds of tests each week. Core areas such as CSS, the Document Object Model (DOM), HTML, selection, Scalable Vector Graphics (SVG), and XMLHttpRequest (XHR) already have good coverage. Kitesurf can also render TodoMVC, Wikipedia, Hacker News, the Cloudflare Blog, and much of the Cloudflare dashboard.
Also Read - Top AI Agent Frameworks for Building Loop-Driven Applications in 2026
Kitesurf fits into a wider Cloudflare plan for an Agentic Internet. At its August Agents Week, Cloudflare also previewed WebMCP, a browser standard that lets websites expose tools to AI agents through a page. Kitesurf handles the browser side of that idea: it gives an agent a lighter way to access and act on web pages.
The current Kitesurf beta matters less as a replacement for Chrome and more as a sign of where browser infrastructure can go. An AI agent does not need every feature that a human browser offers.
It needs fast access to useful page data, safe page isolation, low resource use, and easy scalability. Kitesurf makes those priorities the core of its design, while Chromium remains the better choice for rich visual sites and long sessions.
1. What is Kitesurf Browser?
Kitesurf is Cloudflare’s browser runtime built for AI agents and large-scale browser tasks.
2. How is Kitesurf different from Chromium?
Kitesurf removes many human-focused browser features and targets lower CPU and memory use for agent workloads.
3. How much memory can Kitesurf save?
Cloudflare reports up to 7× lower memory use than Chromium for HTML extraction in its tests.
4. Does Kitesurf support Playwright and Puppeteer?
Yes. Kitesurf supports tools such as Playwright, Puppeteer, chrome-remote-interface, and compatible Model Context Protocol clients.
5. Can Kitesurf replace Chromium?
Not in every case. Chromium remains better for video, WebGL, persistent authenticated sessions, and other complex browser tasks.
