Kitesurf

Kitesurf is Cloudflare's agent-first headless browser, announced in August 2026, that runs entirely in V8 isolates on Cloudflare Workers. Instead of shipping a full desktop browser engine like Chromium, it focuses on what matters to an agent — token count, context windows, scalability, performance, and cost — while trading away features only humans need, such as tabs, themes, extensions, and pixel-perfect rendering.

Key Features

• Runs on Workers, not Chromium: A stateless browser engine that lives entirely on Cloudflare's edge, so you can spin up sessions without managing browser infrastructure.
• Radically lighter: Uses 3-7x less CPU and memory than Chromium for common agentic tasks such as screenshots and HTML extraction.
• CDP-native: Speaks the Chrome DevTools Protocol, so existing Puppeteer, Playwright, and chrome-remote-interface clients work by adding browser=kitesurf to the endpoint.
• MCP-ready: Any AI agent that speaks MCP and CDP can drive Kitesurf through the Browser Run MCP configuration.
• Built from modern components: A modular rendering engine (Blitz), Firefox's Stylo CSS parser, and the Boa JS engine — passing 215,000+ web platform tests and adding more every week.
• Public playground: Explore Kitesurf rendering interactively at kitesurf.cloudflare.app with built-in DevTools inspection.

Use Cases

Who Should Use This Tool?

• Agent Developers: Teams building web agents that need to render pages, extract HTML, take screenshots, or fill forms without a heavyweight Chromium fleet.
• Automation Engineers: Anyone running one-shot "Quick Actions" like content extraction, PDF generation, or screenshot capture at scale.
• Cloudflare Builders: Developers already on Workers who want browser capability co-located with their edge stack.

Problems It Solves

1. Browser fleet cost: Chromium's CPU and memory overhead makes scaling agent browsers expensive; Kitesurf cuts both by 3-7x.
2. Infrastructure complexity: No browser engine to install, patch, or horizontally scale — it runs as a stateless service on Workers.
3. Session churn: Bursty, AI-driven workloads get ephemeral, fully isolated sessions that exist only for the duration of a task.

Pricing

Advantages & Unique Selling Points

Compared to Competitors:

1. Lighter than Chromium-based browsers: 3-7x less CPU and memory for the tasks agents actually perform.
2. Edge-native: Runs on Cloudflare Workers rather than a pool of VMs, giving natural global scale.
3. Drop-in CDP compatibility: Your existing Puppeteer/Playwright code keeps working.

What Makes It Stand Out:

• Designed from the ground up for the "Agentic Cloud" threat model (prompt injection, context management).
• Open-source plans: Cloudflare intends to release Kitesurf so customers can deploy their own version.
• A browser whose success metric is token cost, not pixel fidelity.

Getting Started

Quick Start Guide

1. Use the playground: Explore rendering at kitesurf.cloudflare.app.
2. Point your client at the CDP endpoint: Connect Puppeteer or Playwright with browser=kitesurf in Browser Run.
3. Or wire up MCP: Add the chrome-devtools-mcp configuration pointing at the Kitesurf WebSocket endpoint.

Integration

Integrates seamlessly with:

• Puppeteer, Playwright, chrome-remote-interface
• Any agent speaking MCP and CDP
• Cloudflare Browser Run Quick Actions

Frequently Asked Questions

Is it pixel-perfect like Chromium?

No — Kitesurf trades pixel-perfect rendering for lower cost and higher scale. Use it when exact visual fidelity isn't required.

Does it support extensions and tabs?

No. Those are human-oriented features; Kitesurf strips them away for token efficiency and scalability.

Is the source code available?

Not yet — Cloudflare plans to open source Kitesurf so customers can deploy their own instances.

Alternatives

If Kitesurf isn't the right fit, consider these alternatives:

• Browserbase: Best for managed headless browser fleets with CAPTCHA solving and verified identities.
• Steel: Open-source browser API you can self-host with Docker.
• Cloudflare Computer: For persistent filesystem and code execution, not just browsing.

Tips & Best Practices

1. Use it for one-shot actions: Screenshots, PDFs, and HTML extraction are where Kitesurf shines.
2. Keep Chromium for visual QA: When rendering fidelity matters, keep a Chromium-based fallback.
3. Mind the trade-offs: Slightly slower wall time is the price for dramatically lower resource use.

Conclusion

Kitesurf is a genuinely new category of browser — one built for AI agents rather than humans, running on Workers with dramatically lower CPU and memory needs. If you're building web agents at scale and want to cut browser infrastructure cost, it's worth testing while it's free in beta.