Quick answer
Choose Kitesurf for compatible, ephemeral, stateless agent workloads that value lower CPU and memory and can tolerate incomplete browser parity. Choose Browser Run Chromium for full-browser features, persistent authenticated state, pixel-sensitive output, or any site and CDP requirement that Kitesurf does not pass.
This is a per-workload choice, not a one-time platform migration. Use the Kitesurf readiness checker and keep both engines behind explicit policy-aware routing.
Comparison
| Dimension | Kitesurf beta | Browser Run Chromium |
|---|---|---|
| Design | Agent-first browser on Workers | Full Chromium browser engine |
| Best fit | Stateless, bursty, compatible extraction, PDF, screenshot tasks | Broad web compatibility and stateful browser workflows |
| Rendering | Not intended for pixel-perfect parity | Better choice for browser-faithful rendering |
| Video and WebGL | Not currently supported | Preferred |
| Bot challenge with real TLS fingerprints | Not currently supported | Preferred |
| Long authenticated persistent session | Not currently supported | Preferred |
| CDP | Growing subset for agent and automation needs | Broader Chromium CDP behavior |
| Resource hypothesis | Lower CPU and memory in provider corpus | Higher resources in that corpus |
| Wall-time hypothesis | Slower than warm Chromium in provider corpus | Faster in that bounded comparison |
Do not optimize before compatibility
First compare task success, extraction and visual accuracy, authentication, required CDP commands, and security controls. Then compare latency, CPU, memory, browser usage, retries, reviewer effort, and current price.
Cloudflare’s benchmark uses medians from five Quick Action runs across 14 URLs. It is provider evidence for that corpus, not a universal performance or cost promise.
Route per workload
Keep a versioned compatibility registry keyed by target, task, client, engine, and acceptance revision. Send traffic to Kitesurf only after the exact combination passes. Fall back to Chromium on documented exclusions or failed acceptance—not on arbitrary errors that could signal authorization or security problems.
Use the compatibility testing guide to build the registry and the CDP client guide to test protocol behavior.
Frequently asked questions
When is Kitesurf a better fit than Chromium?
Kitesurf is a candidate for compatible, short-lived, stateless, bursty agent tasks such as one-shot HTML extraction, PDFs, or screenshots that tolerate rendering differences.
When should I choose Browser Run Chromium?
Choose Chromium for video, WebGL, real-TLS bot-challenge handshakes, long authenticated stateful sessions, pixel-sensitive rendering, or any required site or CDP behavior that Kitesurf does not pass.
Is Kitesurf always faster or cheaper?
No. Cloudflare’s bounded benchmark reports lower CPU and memory for Kitesurf but slower wall time than warm Chromium. Measure the real workload and current pricing.
Official sources
Source check: August 12, 2026. Recheck beta, exclusions, CDP coverage, benchmarks, price, limits, and Chromium behavior before routing.