Cloudflare exposes DevTools API

Cloudflare now lets developers connect directly to its Browser Rendering service with the full Chrome DevTools Protocol, the same remote control system behind Chrome’s own developer tools. (developers.cloudflare.com) A headless browser is a web browser without the visible window, used for jobs like loading pages, clicking buttons, and taking screenshots by code instead of by hand. Cloudflare said on April 10, 2026 that outside clients can now reach those browser sessions through a Chrome DevTools Protocol endpoint from “any environment.” (developers.cloudflare.com, developers.cloudflare.com) Chrome DevTools Protocol is the message format Chrome uses for inspection, debugging, profiling, and automation over WebSocket connections. Cloudflare’s documentation says the new `/devtools` endpoints can create persistent browser sessions, manage tabs, and expose the complete protocol schema with domains, commands, events, and types. (chromedevtools.github.io, developers.cloudflare.com, developers.cloudflare.com) That changes who can drive Cloudflare’s hosted browsers. Before this update, the service already supported higher-level tools such as Puppeteer, Playwright, screenshots, PDFs, and scraping flows inside Workers; the new endpoint opens lower-level control for custom clients, local machines, and continuous integration systems outside Cloudflare’s runtime. (developers.cloudflare.com, blog.cloudflare.com, developers.cloudflare.com) Cloudflare has been moving toward this for years. In its 2022 open beta post, the company said Browser Rendering already relied on a WebSocket endpoint that “speaks the DevTools Protocol,” but most customers used Cloudflare’s own wrappers instead of talking to the browser directly. (blog.cloudflare.com) The company has also been expanding the scale around those browser sessions. In an October 2025 platform update, Cloudflare said Browser Rendering could run 30 concurrent headless browsers per account, up from 10, and in a later changelog it raised Workers WebSocket message limits to 32 mebibytes from 1 mebibyte for workloads including Chrome DevTools Protocol traffic. (blog.cloudflare.com, developers.cloudflare.com) Cloudflare paired the DevTools Protocol rollout with support for Model Context Protocol clients, a format used by artificial intelligence tools to call external systems. The changelog says developers can now connect either with raw browser-control messages or with Model Context Protocol clients for browser automation. (developers.cloudflare.com) The practical effect is that a browser running on Cloudflare’s network can now be treated more like a remote lab machine: open a page, inspect network traffic, trace performance, set breakpoints, or capture output without operating your own browser fleet. Cloudflare’s update turns that internal browser channel into a public interface developers can script against directly. (developers.cloudflare.com, developers.cloudflare.com, blog.cloudflare.com)