AI web-reading tools
Give agents a short-lived browser for sites that require JavaScript rendering, DOM access, or screenshots but do not need full Chromium fidelity.
Independent tool overview
Kitesurf at a glance
Kitesurf is Cloudflare's beta browser engine for AI agents and one-shot web automation. It runs in V8 isolates on Cloudflare Workers, exposes a subset of the Chrome DevTools Protocol, and can be selected in Browser Run Quick Actions or CDP sessions. Compared with warm Chromium in Cloudflare's 14-URL test, Kitesurf used materially less CPU and memory for screenshots and HTML extraction but took longer in wall-clock time. It is a useful fit for ephemeral extraction, screenshots, PDFs, and compatible browsing tasks—not a full Chromium replacement for persistent logins, video, WebGL, bot challenges, or pixel-perfect rendering.
Visit the official Kitesurf site ↗
- Developer
- Cloudflare
- Released
- August 6, 2026
- Status
- Public beta
- Product type
- Stateless agent-first browser engine within Cloudflare Browser Run
- Runtime
- Cloudflare Workers, V8 isolates, Dynamic Workers, and WebAssembly
- Interfaces
- Browser Run Quick Actions, CDP WebSocket, REST, Puppeteer, Playwright, chrome-remote-interface, and CDP-based MCP
- Best fit
- One-shot extraction, screenshots, PDFs, DOM inspection, and compatible agent browsing
- Session model
- Ephemeral and isolated; persistent authenticated sessions are not a target
- Not supported yet
- Video playback, WebGL, real-TLS bot challenges, and long persistent authenticated sessions
- Rendering trade-off
- Lower CPU and memory than Chromium in Cloudflare's test, but slower wall time and lower fidelity
- Pricing
- Free while in beta, behind per-account limits
- Reviewed
- August 31, 2026 from Cloudflare's launch article, documentation, pricing, limits, changelog, and current Agents integration
Overview
What Kitesurf is
Cloudflare introduced Kitesurf on August 6, 2026 as an agent-first alternative to running a full human-oriented browser. It removes capabilities that an automated model often does not need and focuses on structured page access, DOM inspection, screenshots, extraction, scalability, isolation, and lower compute consumption.
Kitesurf runs entirely on Cloudflare Workers. Its Engine exposes HTTP and CDP endpoints and holds the short-lived session state; separate PageScript and PageRenderer components process untrusted page code and visuals. A dedicated outbound component controls network access, applies browser-shaped headers and CORS policy, filters responses, and keeps cookies isolated by page.
Developers select Kitesurf by adding browser=kitesurf to a Browser Run Quick Action or CDP endpoint. Existing Puppeteer, Playwright, chrome-remote-interface, and CDP-compatible MCP clients can connect, but Kitesurf implements only the protocol surface needed for current agent and automation scenarios.
The engine is intentionally ephemeral and stateless wherever possible. That makes it well suited to bursty one-shot tasks and recovery by replay, but it is the wrong choice when a workflow needs a long authenticated session or cross-request browser state.
Cloudflare reports that Kitesurf passed more than 215,000 Web Platform Tests at launch. Its own five-run, 14-URL comparison found 3.1–7.0 times lower CPU or memory for screenshot and extraction work, while warm Chromium completed the same tasks about 1.7–1.8 times faster in wall time. Those are provider-run medians on a small corpus, so teams should benchmark their own sites.
Kitesurf starts every page from untrusted input, but isolation does not make an AI browsing workflow safe by itself. Agents can still follow malicious page instructions, leak authorized data through permitted actions, submit the wrong form, or violate a site's rules. Use domain and action restrictions, short-lived credentials, human approval, audit logs, and a Chromium fallback for unsupported pages.
Use cases
Who Kitesurf is best for
The strongest fit depends on the job you need the product to complete, not the size of its feature list.
One-shot Quick Actions
Generate a screenshot, PDF, rendered document, link list, snapshot, or structured extraction from a compatible URL.
Bursty automation
Start isolated sessions only for the duration of a task and scale many independent jobs without maintaining a warm browser fleet.
CDP-compatible agent stacks
Connect existing Puppeteer, Playwright, chrome-remote-interface, or MCP tooling through a Cloudflare endpoint with a browser selector.
Compute-sensitive workloads
Reduce CPU and memory for compatible extraction and screenshot tasks when those resources matter more than minimum wall-clock latency.
Browser-engine evaluation
Route simple pages to Kitesurf and complex or stateful pages to Chromium after testing both against explicit correctness and rendering criteria.
Capabilities
Core Kitesurf features
Workers-native browser engine
Runs the engine, page scripting, rendering, and controlled outbound access on Cloudflare's serverless platform rather than launching desktop Chrome.
Quick Actions
Supports Browser Run's one-request endpoints by adding the browser=kitesurf query parameter for operations such as screenshots and extraction.
CDP endpoint
Exposes a Chrome DevTools Protocol WebSocket so compatible automation libraries and agent clients can drive a short-lived page.
Public playground
Lets developers enter a URL, inspect the rendered page, explore DOM and console output, watch network activity, and view isolate memory without first writing code.
Fresh session isolation
Treats every page as untrusted and starts each session clean to reduce state leakage and make failures recoverable by replay.
Controlled network component
Routes page asset and fetch requests through a dedicated outbound worker that enforces policy, response filtering, headers, CORS, and separate cookie jars.
DOM and script execution
Implements the HTML, DOM, selection, SVG, XHR, CSS, and JavaScript behavior needed for many agent-oriented web tasks.
Software rendering
Builds page visuals without a full Chromium stack, prioritizing compute efficiency over perfect visual compatibility.
Broad framework coverage
Cloudflare reports successful rendering for TodoMVC variants across React, Vue, Angular, Preact, and vanilla JavaScript plus several content and dashboard sites.
Web Platform Test program
Uses a growing WPT suite and continuous performance tests to expand standards coverage and catch regressions.
Chromium fallback path
Lives inside Browser Run, allowing developers to choose standard Chromium when a page needs capabilities Kitesurf does not yet implement.
Process
How the Kitesurf workflow works
Step 1
Classify the browser task
Use ordinary HTTP fetch for static data, Kitesurf for compatible rendered one-shot work, and Chromium for video, WebGL, difficult bot challenges, pixel-perfect output, or persistent login state.
Step 2
Create scoped Cloudflare access
Use a Browser Run API token with the minimum account permissions, store it in a secret manager, rotate it, and never expose it to page JavaScript or model output.
Step 3
Start in the playground
Test the exact target page, inspect DOM, network, console, memory, screenshot fidelity, and required interactions before committing it to automation.
Step 4
Build an expected-output fixture
Record required text, fields, links, screenshots, actions, and error behavior for representative pages, languages, frameworks, cookie states, and redirects.
Step 5
Select Kitesurf explicitly
Add browser=kitesurf to the Quick Action or CDP URL; do not assume a default Browser Run session uses this engine.
Step 6
Constrain destinations
Allow only required schemes, domains, redirects, ports, and download types; block local, metadata, administrative, and sensitive internal endpoints.
Step 7
Treat page content as hostile
Keep webpage text and scripts in the data boundary, ignore instructions that attempt to change agent policy, and prevent pages from requesting credentials or broader tools.
Step 8
Limit actions and state
Prefer read-only extraction; require explicit confirmation for logins, submissions, purchases, uploads, messages, deletions, or any action affecting another person or system.
Step 9
Set resource budgets
Cap session time, redirects, pages, retries, concurrency, output size, and total browser hours; record X-Browser-Ms-Used where applicable.
Step 10
Validate the result
Compare extracted values against the DOM or authoritative source, inspect screenshots and PDFs, and reject partial pages, missing controls, or silently blocked requests.
Step 11
Implement a fallback
Detect unsupported APIs, low-fidelity rendering, login persistence, challenge pages, and timeouts, then retry through Browser Run's Chromium engine when allowed.
Step 12
Monitor production
Track completion, accuracy, latency, CPU, memory, browser time, rate limits, site-level failure, policy violations, and engine-version changes.
Cost
Kitesurf pricing and free plan
Cloudflare states that Kitesurf is free while in beta and subject to per-account limits. Browser Run itself is available on Workers Free and Paid plans with published browser-hour and concurrency pricing for its general service. Because beta treatment may change, confirm the dashboard and current Kitesurf documentation before forecasting production cost.
Kitesurf beta
Free during beta
Current Kitesurf engine access through Browser Run, behind per-account limits.
- Requires a Cloudflare account and Browser Run access for API use
- Available through Quick Actions and the CDP endpoint
- Public playground is available for compatibility exploration
- Published beta pricing and limits can change before general availability
Workers Free Browser Run context
10 browser minutes per day included
The standard Browser Run free-plan allowance and limits surrounding the service.
- Three concurrent browsers for Browser Sessions
- One new browser instance every 20 seconds
- 60-second browser timeout
- One Quick Action request every 10 seconds
- No paid overage on the Free plan
Workers Paid Browser Run context
10 hours/month included, then $0.09/hour
The standard paid Browser Run model; verify how it will apply to Kitesurf during and after beta.
- 200 concurrent browsers is the current default limit for Browser Sessions
- The pricing page lists 10 concurrent browsers included for billing, then $2 per additional monthly-average concurrent browser
- Three new Browser Sessions per second
- 30 Quick Action requests per second
- Higher account limits may be requested
Pricing checked . Check current pricing at the source ↗
Assessment
Kitesurf strengths and limitations
Where it stands out
- Purpose-built around the needs and economics of AI agents rather than human browsing features
- Runs entirely on Cloudflare Workers without maintaining a separate Chrome fleet
- Current beta is free behind account limits
- Uses familiar Quick Action, CDP, Puppeteer, Playwright, and MCP integration paths
- Fresh isolated sessions reduce cross-task state and simplify recovery by replay
- Dedicated outbound access narrows which components can reach the network
- Cloudflare's launch benchmark reports substantially lower CPU and memory than warm Chromium for two common tasks
- Public playground makes site compatibility and memory behavior easy to inspect
- Chromium remains available in the same broader Browser Run product for unsupported tasks
- Cloudflare publishes concrete unsupported cases rather than presenting Kitesurf as a universal browser
- A large and growing Web Platform Test suite provides a measurable compatibility program
What to consider
- Kitesurf is an early beta and Cloudflare says it is still working toward production readiness
- It implements a subset of CDP, so a compatible client library does not guarantee that every command or workflow works
- It does not yet play video or render WebGL
- It cannot negotiate bot challenges that depend on genuine browser TLS fingerprints
- Long-running authenticated sessions and persistent cross-request state are not suitable use cases
- Rendering is not intended to be pixel-perfect and can differ from Chromium on complex CSS, fonts, graphics, or layout
- In Cloudflare's launch test, Kitesurf used less CPU and memory but was about 1.7–1.8 times slower in wall-clock completion
- The published performance comparison used medians of five runs across only 14 URLs and is not an independent benchmark
- The count of passing Web Platform Tests does not establish compatibility with a specific production site or automation sequence
- Sites can change markup, scripts, authentication, challenges, and terms without notice, breaking a previously successful workflow
- Statelessness can force an agent to replay work and makes multi-step login or continuity flows harder
- A 60-second Browser Run timeout can be too short for slow pages or lengthy agent interactions
- Cloudflare account, API token, network, regional, and service availability become dependencies for hosted automation
- Free beta access is not a durable production price commitment
- Page isolation reduces some technical risk but does not stop prompt injection, social engineering, unsafe tool arguments, or misuse of authorized credentials
- Automated extraction may encounter personal, licensed, paywalled, or contract-restricted data and still requires lawful collection and retention practices
- Automated actions can submit forms, alter accounts, purchase items, or communicate externally if the surrounding agent grants too much authority
- Browser fingerprints and Cloudflare IP ranges may be identified or blocked by origin sites
- Teams need a Chromium fallback and site-specific monitoring to avoid silently incomplete data
- Cloudflare's broader Browser Run pricing, concurrency billing, and beta-specific limits must be rechecked before scaling
Compare
Kitesurf alternatives
The right alternative depends on the specific output, workflow, controls and budget your project requires.
Data Analysis
AgentQL
A web-automation and structured-query platform for teams that prefer high-level semantic extraction over direct browser-engine control.
Explore AgentQL →Agents
Gemini Computer Use
A specialized computer-use model for visually operating browser interfaces when model-driven UI actions matter more than a lightweight engine.
Explore Gemini Computer Use →Agents
ChatGPT Agent
A managed end-user agent with its own browser and tools for people who want delegated tasks rather than developer infrastructure.
Explore ChatGPT Agent →Consumer
ChatGPT Atlas
A user-facing AI browser experience for interactive browsing, unlike Kitesurf's ephemeral headless developer runtime.
Explore ChatGPT Atlas →Questions
Kitesurf FAQs
What is Kitesurf?
Kitesurf is Cloudflare's lightweight, stateless browser engine for AI agents. It runs in V8 isolates on Workers and is accessed through Cloudflare Browser Run Quick Actions or a CDP endpoint.
Is Kitesurf a web browser for people?
No. It is a headless engine built for automated tasks. It intentionally omits human-oriented features such as tabs, extensions, synchronization, and pixel-perfect interactive rendering.
Is Kitesurf free?
Cloudflare says Kitesurf is free while in beta, behind per-account limits. The surrounding Browser Run service has Workers Free and Paid allowances, so recheck the current dashboard and documentation before production budgeting.
How do I use Kitesurf?
Add browser=kitesurf to a Browser Run Quick Action or CDP endpoint. You need a Cloudflare account ID and scoped Browser Run token for API access; the public playground offers a faster compatibility test.
Does Kitesurf work with Playwright and Puppeteer?
It exposes CDP for Playwright, Puppeteer, chrome-remote-interface, and CDP-based MCP clients. Kitesurf implements only part of CDP, so test the exact methods, navigation, events, and page features your automation needs.
Is Kitesurf faster than Chromium?
It depends on the metric. In Cloudflare's small launch benchmark, Kitesurf used 3.1–7 times less CPU or memory for screenshots and HTML extraction, while warm Chromium finished about 1.7–1.8 times faster in wall time.
Can Kitesurf handle logged-in sites?
Short in-session interactions may work on compatible pages, but Cloudflare specifically says long-running authenticated sessions requiring persistent state are not a good fit. Protect credentials and use Chromium when continuity is required.
Can Kitesurf play video or render WebGL?
Not as of this review. Use Browser Run's default Chromium engine for video, WebGL, high-fidelity graphics, and other unsupported browser APIs.
Can Kitesurf bypass bot protection?
It is not designed to negotiate challenges that require genuine browser TLS fingerprints. Do not use browser automation to evade access controls; use authorized APIs or Chromium only where the site's rules permit automation.
Is Kitesurf secure against prompt injection?
No browser engine can solve the full agent problem. Kitesurf isolates sessions and network components, but malicious page content can still manipulate the model. Keep webpage instructions untrusted, restrict tools and destinations, and require approval for consequential actions.
When should I choose Kitesurf instead of Chromium?
Choose it for compatible, ephemeral extraction, screenshots, PDFs, and agent browsing when CPU and memory efficiency matter. Choose Chromium for persistent sessions, higher fidelity, video, WebGL, difficult challenges, or broader CDP coverage.
Is Kitesurf ready for production?
Cloudflare labels it beta and says it is continuing CDP, rendering, WPT, and efficiency work. A controlled production pilot may be reasonable if you test target sites, validate outputs, implement Chromium fallback, and monitor regressions.
Bottom line
Our Kitesurf verdict
Kitesurf is a compelling beta for developers whose agents need brief, isolated access to rendered web pages and can tolerate lower browser fidelity. Its value is compute efficiency and serverless scale, not raw wall-clock speed or universal compatibility. Start with the playground, benchmark the exact URLs and actions that matter, lock down destinations and credentials, validate every extracted result, and keep a Chromium fallback. Avoid it for persistent authenticated work, video, WebGL, challenge-heavy sites, or any task where a subtle rendering difference can cause a consequential error.
Visit Kitesurf website ↗Similar Miscellaneous Tools
View all Miscellaneous AI tools →
Inkling-Small
Inkling-Small - Thinking Machines' compact open model that rivals full-size version
Router
Ramp’s endpoint that matches each AI request to the cheapest fitting model
.jpeg)
Lyria 3.5
Lyria 3.5 - Google's new music model with more realistic vocals
Gemini Omni 1.1 Flash
Google's video model update with scene extensions and 4K upscaling
AI training for the future of work.
Get access to all our AI courses, hundreds of real-world AI use cases, live expert-led workshops, an exclusive network of AI early adopters, and more.
AI Courses
Get unlimited access to all of our current & upcoming industry-specific AI courses for the duration of your subscription.
Daily Guides
To keep up with the rapid pace of AI, our team publishes AI implementation guides daily. Our library contains 300+ practical use cases to automate real-world work.
Workshops
Join weekly, live, interactive sessions with industry leaders who are at the forefront of AI for hands-on implementation guidance and exclusive insights.
Community
Network with an exclusive community of AI-first professionals who are working smarter with AI. Learn how early adopters are using AI in their work and businesses.