Quick answer
Treat Cloudflare Kitesurf compatibility as a workload-level test result, not a property inherited from CDP, a high Web Platform Test count, or one successful screenshot.
Cloudflare documents four clear Chromium cases: video, WebGL, real-TLS bot-challenge handshakes, and long authenticated sessions that require persistent state. Every other production workflow still needs representative testing. Use the readiness checker before building the corpus.
Build the test matrix
Cover four layers:
| Layer | Evidence to collect |
|---|---|
| Page and browser | DOM, CSS, fonts, SVG, JavaScript APIs, frames, storage, auth, downloads, media |
| Client and CDP | Required commands, events, timeouts, interception, screenshots, PDFs, cleanup |
| Agent and security | Prompt injection, target policy, tool arguments, credential boundaries, approvals |
| Operations | Success, accuracy, errors, retries, wall time, CPU, memory, browser usage, fallback, cost |
Version the URLs, tasks, inputs, expected outputs, client version, engine, endpoint, and acceptance thresholds. Keep sensitive targets and credentials out of public fixtures.
Interpret provider benchmarks correctly
Cloudflare publishes strong and growing WPT coverage plus a five-run, 14-URL Quick Actions benchmark. In that provider corpus, Kitesurf used less CPU and memory while warm Chromium completed the measured tasks faster in wall time.
Those numbers help form a hypothesis. They do not predict your sites, client commands, authentication, rendering, or bill. Reproduce the relevant measurements with your own traffic distribution.
Define promotion and fallback gates
Promote only when the task-success and output-quality bars pass, security controls hold, error and retry budgets are acceptable, and the Chromium fallback succeeds within policy and cost limits.
Fail closed for an unauthorized target, unsupported action, missing approval, credential leak, unbounded navigation, or incompatible output. A blank frame or missing element is still a failed task even if the session stays alive.
Use the CDP client guide for connection testing and Kitesurf vs. Chromium for engine selection.
Frequently asked questions
Which Kitesurf limitations are documented?
Cloudflare currently directs video, WebGL, real-TLS bot-challenge handshakes, and long authenticated sessions requiring persistent state to Browser Run Chromium.
Do Web Platform Test results prove a site works?
No. WPT coverage is useful conformance evidence, but a production decision needs real-site, CDP-command, output, security, reliability, and fallback tests.
What should a Kitesurf acceptance test measure?
Measure task success, extraction and visual accuracy, required CDP support, console and network errors, auth and state behavior, retries, CPU, memory, wall time, cost, and Chromium fallback.
Official sources
Source check: August 12, 2026. Recheck beta, WPT, CDP coverage, exclusions, benchmarks, price, and limits before each promotion decision.