Kitesurf, Cloudflare’s new browser for AI agents, uses up to seven times less memory than Chromium. Chromium powers Google Chrome, so it carries many human-focused features, and every extra feature costs memory. Agents need browsers for many tasks, so the costs multiply across every session.
Because memory limits how many agents a server can host, Cloudflare launched Kitesurf to combat that. Kitesurf strips away everything machines never use, and Cloudflare offered it free during the beta testing.
Kitesurf Gives AI Agents a Lighter Browser
Cloudflare’s engineers explain the trade-off plainly, “Agents care about token counts, costs, and scale, not smooth scrolling. The browser therefore accepts slightly imperfect rendering in exchange for efficiency’. Cloudflare recommends Kitesurf for one-shot jobs, such as extracting content or capturing screenshots on compatible sites.
Moreover, safety also shapes the design. Agents visit arbitrary sites, so the browser treats every page load as untrusted input. The browser runs entirely on Workers, Cloudflare’s serverless platform, which isolates components by design. Most components keep no state, so a failed session restarts cheaply.
Engineers built Kitesurf in 12 weeks by pairing AI coding agents with public Web Platform Tests. In addition, the suite checks standards conformance, and the browser already passes more than 215,000 tests, adding hundreds weekly.
Lower Memory Use Lets More Agents Run
Cloudflare tested the browser against a warm Chromium pool on 14 web addresses, using median results from five runs. Screenshots used 57.8 MiB of memory on Kitesurf but 271.0 MiB on Chromium, a 4.7-fold gap.
In addition, HTML extraction showed the widest gap, 39.4 MiB against 273.7 MiB, a sevenfold cut. CPU use fell, by 3.1 times for screenshots and 3.8 times for extraction.
Also, Cloudflare’s engineers argue Chromium costs too much to give every agent its own browser. Lighter sessions change the math, so more agents can have a browser of their own. Then, cheaper agents reach more of the web.
However, speed is the trade-off because Chromium finishes tasks about 1.7 to 1.8 times faster. Chromium stays warmed up between jobs, while the new browser starts fresh each time. Drawing and saving the final image causes most of the lag.
Furthermore, slower runs can also cost more, because Browser Run charges for time, not memory. Complex sites still need Chromium because Kitesurf cannot play video or show 3D graphics. It also cannot handle bot checks or hold long logged-in sessions
Cloudflare’s Roadmap After the Beta
Consequently, engineers will keep working to close the speed gap. The team will also track processing work, memory, and speed continuously. Sharper screenshots and PDFs come next, because AI models often read images better than text.
Then, wider support for standard browser commands should let more automation tools connect. Finally, Cloudflare plans to publish the browser’s code once it is ready, so customers can run their own versions.
Beta limits still apply per account, so teams should test sites first. The public playground shows each page’s memory use. As AI agents multiply, lighter browsers could decide how cheaply software reads the web. If Kitesurf closes the speed gap, it could win more high-volume work from Chromium
