Browser Use vs Cloudflare Browser Run

The decision

Start with the product contracts for saved browser state, credential handling, website sign-in, code execution. Different labels do not establish different functionality; compare the implementation and conditions behind each one.

Browser Use has separate hosted-browser and hosted-agent paths. For browser infrastructure, create a browser and connect your own code over CDP. Profiles and secret bindings handle different parts of authenticated work.

Cloudflare Browser Run provides headless browser sessions through CDP and browser code deployed in Workers. This comparison concerns sessions and their execution model, rather than the separate Quick Actions APIs.

At a glance

Sources: docs.browser-use.com [1] ↗docs.browser-use.com [2] ↗docs.browser-use.com [3] ↗docs.browser-use.com [4] ↗developers.cloudflare.com [5] ↗

What survives a session

Browser Use: Profiles persist cookies, local storage and login state between browsers. Browser settings select a profile for a run. A session's conversation history and a profile's browser state are different resources.

Cloudflare Browser Run: Cloudflare documents reuse of browser sessions and a Durable Objects integration. Keeping a session alive is different from exporting a portable authenticated profile; design the required state store explicitly.

Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗

Website login

Browser Use: V4 secret bindings give credentials aliases and allowed hostnames for use in a run. Profiles reuse existing state; the separate 2FA guide addresses verification during authenticated work.

Cloudflare Browser Run: Use browser code to implement the website's sign-in flow and retain the necessary session state. The reviewed overview does not establish a managed website connection that checks sign-in readiness before a workflow starts.

Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗

Where the code runs

Browser Use: The cloud offers hosted-agent runs and separately created browsers. The reviewed browser documentation does not establish a deploy-your-own Python Function equivalent. Keep an external script runner separate from a hosted agent when comparing execution ownership.

Cloudflare Browser Run: Deploy browser automation within a Cloudflare Worker or connect to Browser Run from an external process over CDP. Workers provide the execution layer; compare their runtime and deployment model separately from browser access.

Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗

Published browser measurements

These are the latest provider runs in the saved BrowserArena snapshot checked on October 18, 2026. Dates and runner environments can differ. A lifecycle test opens, connects, navigates and releases a browser; the throughput test runs a separate browser action sequence. Neither measures managed authentication or deployed Function reliability.

Use these observations to choose what to test in your application. An account-configuration failure, an incompatible page action and a timed-out navigation require different interpretations. BrowserArena is maintained by Notte and publishes its source and methodology.

Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗github.com [3] ↗

Pricing model

Browser Use: Browser time and hosted-agent/model usage are separate pricing questions. Select the infrastructure path before comparing rates, and account for retained idle browser time and network usage where applicable.

Cloudflare Browser Run: Price browser usage and the Worker execution components required by the workload. The Browser Run pricing page, rather than a single browser-hour estimate, defines included allowances and applicable limits.

Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗

Capacity and limits

Browser Use: The concurrency guide distinguishes concurrent browser capacity from the HTTP request budget. Keys in a project share capacity and credits. Polling frequency can exhaust request capacity even when there are free browser slots.

Cloudflare Browser Run: Browser Run has its own limits and pricing alongside Workers. Account browser capacity, session creation limits and the Worker execution budget constrain different parts of a workflow.

Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗

Which approach fits?

Choose Browser Use when you use Browser Use's framework or want its hosted browsers while retaining the option of a hosted browser agent.

Browser Use tradeoff: A hosted-agent run is a different execution unit from your deployed browser script. Keep comparisons focused on the browser path when measuring session speed and price.

Choose Cloudflare Browser Run when you already deploy Workers and want browser automation within that application's execution and scheduling model.

Cloudflare Browser Run tradeoff: A Worker and a browser session have separate resource and lifecycle constraints. Confirm the chosen browser library and binding path instead of assuming an unchanged local browser script will deploy directly.

Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗

Check the browser connection

Install playwright-core in your application and provision a session through the provider's documented creation flow. Run this smoke test from the intended controller region with the returned CDP endpoint. It checks connection and navigation, not login, rendering parity or a complete business workflow.

Keep browser connection URLs on your backend. After the test, release the owned session through the provider's API. Product-specific lifecycle APIs and profile identifiers are not portable between providers.

import { chromium } from "playwright-core";

// Provision the owned browser using the provider's documented session API.
// Keep the connection URL in your backend's secret environment.
const endpoint = process.env.BROWSER_CDP_URL;
if (!endpoint) throw new Error("Set BROWSER_CDP_URL for an owned session");

const browser = await chromium.connectOverCDP(endpoint);
try {
  const context = browser.contexts()[0] ?? await browser.newContext();
  const page = context.pages()[0] ?? await context.newPage();
  await page.goto("https://example.com", { waitUntil: "domcontentloaded" });
  if ((await page.title()) !== "Example Domain") {
    throw new Error("The browser did not reach the expected page");
  }
  console.log({ connected: true, expectedPage: true });
} finally {
  await browser.close();
  // Release the owned session with the provider's documented API as well.
  // A disconnected socket alone is not a portable session-cleanup contract.
}

Sources: playwright.dev ↗

Before you switch

Keep the same target workflow when evaluating both products. Separate infrastructure facts from measurements and test the required account state, action sequence and artifacts. A successful connection test does not establish that a long or authenticated task will complete.

Use the focused guides for Browser Use and Cloudflare Browser Run below when the deciding requirement is pricing, persistence or code execution. Provider-owned resources such as session IDs, profiles and managed connections need a new mapping during migration.

When Notte belongs on this shortlist

Browser Use's hosted-agent offering and standalone browser infrastructure are separate options. Keep the comparison at the browser layer when your application already owns its controller; compare execution ownership separately if the hosted agent is part of the requirement.

Cloudflare can be an economical architectural choice when Workers and the surrounding scheduling already exist in your application. Notte is worth evaluating when a browser, deployed Python handler and authentication workflow should share a product rather than a Workers composition.

Notte: Create an owned browser session, connect Playwright or Puppeteer over CDP, and stop the session when the work finishes. Browser lifecycle management remains necessary even when the control socket disconnects.

Consider this third option when its documented mechanism addresses a requirement left open by the two providers above. A working configuration on either original provider can still be the better choice; compare the task and ownership cost before switching.

Sources: docs.browser-use.com [1] ↗developers.cloudflare.com [2] ↗docs.notte.cc [3] ↗

Keep comparing