--- title: Cloudflare's Kitesurf is a Rust-based headless browser... description: Cloudflare has launched Kitesurf, a headless browser built for AI agents that runs on Cloudflare Workers using V8 isolates, WebAssembly, and Rust — with no... canonical: https://daily.dev/posts/cloudflare-s-kitesurf-is-a-rust-based-headless-browser-for-ai-agents-that-uses-far-less-cpu-and-memo-jnxt4bdw5 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Cloudflare's Kitesurf is a Rust-based headless browser for AI agents that uses far less CPU and memory than Chromium | daily.dev og:description: Cloudflare has launched Kitesurf, a headless browser built for AI agents that runs on Cloudflare Workers using V8 isolates, WebAssembly, and Rust — with no... og:url: https://daily.dev/posts/cloudflare-s-kitesurf-is-a-rust-based-headless-browser-for-ai-agents-that-uses-far-less-cpu-and-memo-jnxt4bdw5 og:image: https://api.daily.dev/og/posts/jNxT4bDw5.png og:image:alt: Cloudflare's Kitesurf is a Rust-based headless browser for AI agents that uses far less CPU and memory than Chromium og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Cloudflare's Kitesurf is a Rust-based headless browser for AI agents that uses far less CPU and memory than Chromium **[Collections](https://daily.dev/sources/collections)** · 2 min read · 6 upvotes · 0 comments ## Summary Cloudflare has launched Kitesurf, a headless browser built for AI agents that runs on Cloudflare Workers using V8 isolates, WebAssembly, and Rust — with no Chromium dependency. It achieves 3–7× lower CPU and memory usage than Chromium at the cost of ~1.7× slower wall time. The architecture splits work across a sandboxed outbound worker, a PageScript isolate for DOM/JS execution, and a PageRenderer for rasterization. Despite being a ground-up rewrite, it already passes 215,000+ Web Platform Tests and supports Puppeteer, Playwright, and MCP clients via Chrome DevTools Protocol. Kitesurf is currently free in beta through Browser Run, with open source plans announced. ## Content Cloudflare launched Kitesurf this week, a headless browser built specifically for AI agents that runs entirely on Cloudflare Workers. The pitch is straightforward: existing browsers like Chromium were designed for humans, and running them at scale for agentic tasks is expensive and slow. Kitesurf strips out everything a human would need - tabs, extensions, 60fps scrolling, pixel-perfect rendering - and focuses on what agents actually do: extract HTML, take screenshots, and isolate sessions. The whole thing was built in 12 weeks, written in Rust and compiled to WebAssembly. Under the hood it uses a modular rendering engine from Blitz, Firefox's CSS parser Stylo, and the Boa JS ECMAScript engine. The architecture breaks into four main components: - **Engine** - an HTTP/CDP interface compatible with Playwright and Puppeteer - **PageScript** - a V8 + Boa JS Wasm runtime that handles DOM and JS execution - **SandboxOutbound** - a Dynamic Worker that handles external requests securely - **PageRenderer** - a Wasm-based renderer that outputs JPEG, PNG, or PDF Benchmarks show 3-7x lower CPU and memory usage compared to Chromium for common agentic tasks. The tradeoff is wall-clock time: Chromium is about 1.7x faster because it has JIT compilation and Kitesurf doesn't. For tasks where you're spinning up many isolated sessions rather than running one browser hard, that's probably a reasonable trade. Kitesurf currently passes over 215,000 Web Platform Tests and works with Puppeteer, Playwright, and MCP/CDP clients. It doesn't support WebGL, video playback, or long-running sessions yet. It's free in beta through Browser Run. Cloudflare plans to open source it and allow self-hosted deployments. ## Questions this post answers ### What is Cloudflare Kitesurf and how is it different from using headless Chromium for AI agents? Kitesurf is a headless browser built by Cloudflare specifically for AI agent workloads, running entirely on Cloudflare Workers. Unlike Chromium, it strips out human-facing features like tabs, extensions, and smooth scrolling, focusing only on HTML extraction, screenshots, and session isolation. It's written in Rust, compiled to WebAssembly, and uses Blitz's rendering engine, Firefox's Stylo CSS parser, and the Boa JS engine. _Compare browser automation options for AI agents as new alternatives to Chromium emerge on daily.dev._ ### How much CPU and memory does Kitesurf save compared to Chromium for agentic browsing tasks? Kitesurf uses 3-7x less CPU and memory than Chromium for common agentic tasks, according to Cloudflare's benchmarks. The tradeoff is speed: Chromium runs about 1.7x faster in wall-clock time because it has JIT compilation, which Kitesurf lacks. This makes Kitesurf better suited for running many isolated sessions rather than pushing one browser instance hard. _Weigh CPU efficiency against raw speed when picking a browser backend for agent workloads, a comparison daily.dev keeps current._ ### Does Cloudflare's Kitesurf browser support Playwright and Puppeteer? Yes, Kitesurf exposes an HTTP/CDP interface compatible with Playwright and Puppeteer, as well as MCP/CDP clients. It currently passes over 215,000 Web Platform Tests but does not yet support WebGL, video playback, or long-running sessions. It's free in beta through Browser Run, with Cloudflare planning to open source it for self-hosted deployments. _Track compatibility gaps like WebGL and long sessions before adopting Kitesurf in an automation pipeline via daily.dev._ ## Community take How the wider developer community reacted, aggregated from 4 discussions and 48 comments across lobsters, hackernews (as of 2026-09-13). **TL;DR:** Developers are genuinely impressed by the technical architecture—especially the Blitz/Rust/Wasm stack and the 3–7× resource savings—but raise real concerns about anti-bot bypass potential, privacy of cloud-hosted browsing, and whether the agent-browser use case is mature enough to justify the complexity. **Sentiment:** 45% positive · 35% mixed · 20% skeptical **The case for** - The 3–7× lower CPU and memory usage compared to Chromium is a meaningful engineering achievement that could benefit agent workloads. - The modular Blitz engine (decoupled HTML parser, layout, networking, JS engine, rendering) is praised as an unusually clean architecture for a browser engine. - Passing 215,000+ Web Platform Tests gives credibility to the compatibility story for an early-stage project. - Real-world agent use cases—grocery shopping automation, receipt lookup, navigating painful enterprise UIs—show genuine demand for this kind of tool. - Cloudflare's commitment to always flagging requests as bot traffic and open-sourcing the project addresses two common concerns up front. **The pushback** - Concern that Cloudflare profits from locking the web behind Turnstile/bot protection and then renting a browser to get back in is seen as a cynical business model. - Running a browser on a cloud provider's infrastructure raises privacy concerns for sensitive tasks like medical research. - The ~1.7× slower wall time compared to Chromium is a real trade-off that isn't fully addressed. - Websites could easily fingerprint and block Kitesurf given its distinctive headers and bot-flagged requests. - The underlying Blitz engine is still early-stage with many features unimplemented, which limits general-purpose use. - No WebDriver BiDi support yet, leaving it dependent on the proprietary CDP protocol. **By community** - lobsters (mixed): Discussion quickly pivoted to whether Cloudflare's own bot-protection creates the problem this product solves, though commenters were reassured that requests are always flagged as bots and never bypass Turnstile. - hackernews (positive): Technically enthusiastic—especially from the Blitz engine author and browser automation veterans—with lively side threads on real agent use cases, though some skepticism about privacy, fingerprinting, and Cloudflare's dual role as gatekeeper and browser vendor. **Hottest debate:** Whether Cloudflare is cynically monetizing a problem it created by using Turnstile to restrict web access and then charging for a browser that can navigate it. **Open questions** - Will Kitesurf ever be viable for human browsing given its resource efficiency, or is the rendering fidelity gap too large? - How will websites respond once they can reliably fingerprint Kitesurf's mandatory headers and block it outright? - When will WebDriver BiDi support be added so the tool isn't locked into CDP? - Will Cloudflare's cloud-hosted browser model ever be acceptable for privacy-sensitive use cases? - Now that the Blitz engine is getting commercial backing, will Cloudflare fund or sponsor its development directly? **Highlights** > > Are you effectively building a separate renderer outside of Webkit? Yes, it's new engine separate to Webkit/Blink/Gecko/Servo/Ladybird/etc > Just curious on your thoughts about how Webkit was architected then, I guess it's not a modular system where you can separate out things like "Localstorage" support? Honestly, I'm not super-familiar with Webkit's architecture. It's a huge codebase, and it's also C++ which is always pretty intimidating. I believe Webkit is more modular than most of the others, but Blitz goes quite extreme into modularity: - The core is not coupled to the HTML parser - The core is not coupled to the networking - The core is not coupled to the rendering backend - The core is not coupled to the windowing/input layer - The core is not coupled to the JS/scripting engine - The style engine (Stylo - shared with Servo and Firefox) is mostly implemented as a library which can be used independently - The layout engine is mostly implemented in two libraries which can be used independently of the rest of the engine (Taffy for Flexbox/Grid/Block layout and Parley for Text/Inline layout) So, yes I'd hope that it will be possible to individually opt-in to features like localstorage (once we implement them), but it goes a bit further than that. > — [nicoburns on hackernews](https://news.ycombinator.com/item?id=49214990) > any plans to support webdriver bidi for automation? (i'd be happy to help!) [edit: for others reading who don't usually nerd out on browser automation protocols: webdriver bidi is the new-ish w3c cross-browser standard inspired by CDP - the main magic was the upgrade to websockets and also to standardize the capture of network-level traffic. there are still feature gaps between CDP and BiDi (in spec and implementation), but long term, i believe we should bet on web standards, not proprietary protocols controlled by one company. (disclosure: i started the selenium and appium projects.)] > — [hugs on hackernews · 2 comments](https://news.ycombinator.com/item?id=49211186) > > I’ve heard executive leaders tout that “people use agents to buy things for them” but I haven’t actually seen that. My wife really dislikes building up the shopping cart for our weekly grocery delivery, so I built an agent... thing with earendil's npm libs. It takes the menu my wife has decided on, confers with her about the ingredients (if it hasn't seen a recipe before), and then uses Chrome's devtools protocol to head to Walmart and add everything to the shopping cart. It works fairly well and uses the local models I have running on my Mac Studio. > — [nozzlegear on hackernews · 2 comments](https://news.ycombinator.com/item?id=49211949) > From the page https://developers.cloudflare.com/browser-run/ linked to from this article: > Run headless Chrome on Cloudflare's global network for browser automation, web scraping, testing, and content generation. Does Cloudflare the CDN allow these browser instances to bypass their own anti-bot mechanisms? Or will Cloudflare the CDN block them the same as if someone was running scraping bots from a different provider? Will Kitesurf in Cloudflare workers get special bypass privileges to content protected by Cloudflare the CDN? > — [QuantumNomad\_ on hackernews · 1 comments](https://news.ycombinator.com/item?id=49210248) > What a fun business model: use Turnstile to lock out random people from a horrific amount of the Internet but for _a small fee_ one can rent a browser from them. Turns out those Opera folks just started from the wrong end of the pipe > — [mdaniel on lobsters · 2 points, 1 comments](https://lobste.rs/s/9bxkgi/introducing_kitesurf_agent_first#c_it9plh) **Source threads** - [lobsters](https://lobste.rs/s/9bxkgi/introducing_kitesurf_agent_first) · 4 points · 6 comments - [hackernews](https://news.ycombinator.com/item?id=49196184) · 18 points · 8 comments - [hackernews](https://news.ycombinator.com/item?id=49203287) · 3 points · 2 comments - [hackernews](https://news.ycombinator.com/item?id=49208393) · 104 points · 32 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#rust](https://daily.dev/tags/rust), [#webassembly](https://daily.dev/tags/webassembly), [#cloudflare](https://daily.dev/tags/cloudflare) [View this post on daily.dev](https://daily.dev/posts/cloudflare-s-kitesurf-is-a-rust-based-headless-browser-for-ai-agents-that-uses-far-less-cpu-and-memo-jnxt4bdw5) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Cloudflare's Kitesurf is a Rust-based headless browser for AI agents that uses far less CPU and memory than Chromium","url":"https://daily.dev/posts/cloudflare-s-kitesurf-is-a-rust-based-headless-browser-for-ai-agents-that-uses-far-less-cpu-and-memo-jnxt4bdw5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/cloudflare-s-kitesurf-is-a-rust-based-headless-browser-for-ai-agents-that-uses-far-less-cpu-and-memo-jnxt4bdw5"},"datePublished":"2026-08-07T13:58:15.899Z","dateModified":"2026-09-13T20:00:21.866Z","description":"Cloudflare has launched Kitesurf, a headless browser built for AI agents that runs on Cloudflare Workers using V8 isolates, WebAssembly, and Rust — with no...","image":"https://pbs.twimg.com/media/HPHl_31WEAAP6yX.png","thumbnailUrl":"https://pbs.twimg.com/media/HPHl_31WEAAP6yX.png","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/cloudflare-s-kitesurf-is-a-rust-based-headless-browser-for-ai-agents-that-uses-far-less-cpu-and-memo-jnxt4bdw5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,rust,webassembly,cloudflare","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Cloudflare's Kitesurf is a Rust-based headless browser for AI agents that uses far less CPU and memory than Chromium"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/cloudflare-s-kitesurf-is-a-rust-based-headless-browser-for-ai-agents-that-uses-far-less-cpu-and-memo-jnxt4bdw5#faq","mainEntity":[{"@type":"Question","name":"What is Cloudflare Kitesurf and how is it different from using headless Chromium for AI agents?","acceptedAnswer":{"@type":"Answer","text":"Kitesurf is a headless browser built by Cloudflare specifically for AI agent workloads, running entirely on Cloudflare Workers. Unlike Chromium, it strips out human-facing features like tabs, extensions, and smooth scrolling, focusing only on HTML extraction, screenshots, and session isolation. It's written in Rust, compiled to WebAssembly, and uses Blitz's rendering engine, Firefox's Stylo CSS parser, and the Boa JS engine. Compare browser automation options for AI agents as new alternatives to Chromium emerge on daily.dev."}},{"@type":"Question","name":"How much CPU and memory does Kitesurf save compared to Chromium for agentic browsing tasks?","acceptedAnswer":{"@type":"Answer","text":"Kitesurf uses 3-7x less CPU and memory than Chromium for common agentic tasks, according to Cloudflare's benchmarks. The tradeoff is speed: Chromium runs about 1.7x faster in wall-clock time because it has JIT compilation, which Kitesurf lacks. This makes Kitesurf better suited for running many isolated sessions rather than pushing one browser instance hard. Weigh CPU efficiency against raw speed when picking a browser backend for agent workloads, a comparison daily.dev keeps current."}},{"@type":"Question","name":"Does Cloudflare's Kitesurf browser support Playwright and Puppeteer?","acceptedAnswer":{"@type":"Answer","text":"Yes, Kitesurf exposes an HTTP/CDP interface compatible with Playwright and Puppeteer, as well as MCP/CDP clients. It currently passes over 215,000 Web Platform Tests but does not yet support WebGL, video playback, or long-running sessions. It's free in beta through Browser Run, with Cloudflare planning to open source it for self-hosted deployments. Track compatibility gaps like WebGL and long sessions before adopting Kitesurf in an automation pipeline via daily.dev."}}]} ```