Cloudflare · 2026-08-06 · major
Kitesurf — Cloudflare's agent-first browser runs in V8 isolates on Workers
Kitesurf is a new browser Cloudflare built for AI agents, not people — it runs entirely on Workers in V8 isolates, uses 4.7–7x less memory and 3.1–3.8x less CPU than Chromium, and passes 215,000+ Web Platform Tests.

A browser built for AI agents, not humans — Kitesurf runs in Workers and slashes CPU and memory versus Chromium.
Key specs
| Cpu vs chromium | 3.1–3.8x less |
|---|---|
| Memory vs chromium | 4.7–7.0x less |
| Wpt tests passed | 215,000+ |
Quick facts
| Maker | Cloudflare |
|---|---|
| Runtime | V8 isolates on Cloudflare Workers |
| Engines | Blitz (DOM), Stylo (CSS), Parley (text) |
| Interface | Chrome DevTools Protocol + Browser Run |
| Pricing | Free during beta on Browser Run |
| Playground | kitesurf.cloudflare.app |
| Status | Public beta — no video, WebGL, or persistent auth yet |
What is it?
Kitesurf is Cloudflare's new browser project, engineered for AI agents that measure success in tokens, latency, and cost rather than tabs or themes. Instead of running a full Chromium instance for each agent job, Kitesurf runs the whole browser inside V8 isolates on Cloudflare Workers.
How does it work?
Kitesurf splits into three Worker components: an Engine that speaks Chrome DevTools Protocol, a PageScript that runs the DOM and JavaScript on Rust-compiled Blitz plus Stylo, and a PageRenderer that draws pixels with Parley. Each page load is treated as untrusted, and all network traffic goes through a single SandboxOutbound worker that enforces CORS and cookie isolation.
Why does it matter?
Cloudflare measures Kitesurf at 3.1–3.8x less CPU and 4.7–7.0x less memory than a warm Chromium pool for screenshot and HTML jobs — the two operations agent workloads run most. That translates directly into cheaper Browser Run invocations and higher agent concurrency on the same account budget, even though wall-clock time is still 1.7–1.8x slower per job.
Who is it for?
developers building AI browser agents on Cloudflare Workers
Frequently asked questions
- How do I try Kitesurf without writing code?
- Kitesurf ships with a hosted playground at kitesurf.cloudflare.app where anyone can point the browser at a URL and see it render. From there, developers can switch to the Browser Run API by adding browser=kitesurf to the CDP endpoint or by calling the Quick Actions API.
- Why is Kitesurf faster on CPU and memory but slower on wall time than Chromium?
- Kitesurf skips the heavy rendering path most agents never look at, so screenshot and HTML jobs cost 3.1–3.8x less CPU and 4.7–7x less memory. Rasterizing and encoding pixels still happens on a slower single path, so wall time runs 1.7–1.8x behind Chromium on the same jobs today.
- What web features does Kitesurf not support yet?
- Kitesurf renders regular sites like Wikipedia, TodoMVC, and Hacker News, and passes 215,000+ Web Platform Tests. It is not built for video playback, WebGL, or long-lived authenticated sessions — Cloudflare says these are out of scope for the beta and points users to Chromium for those jobs.
- How is Kitesurf priced?
- Kitesurf is free during beta inside Browser Run, with per-account limits. Cloudflare has not published post-beta pricing yet. Access requires a Cloudflare account and goes through the Browser Run CDP endpoint or the Quick Actions API.
Try it
https://kitesurf.cloudflare.app