Search & Discovery

Cloudflare Browser Rendering

Name: Cloudflare Browser Rendering
Brand: Cloudflare Browser Rendering
Availability: InStock

Cloudflare Browser Rendering (rebranded to Browser Run in 2026) runs headless Chrome on Cloudflare's global edge with one-call Quick Actions for /screenshot, /pdf, /markdown, /scrape, /json, and /crawl.

Starting atFree

Visit Cloudflare Browser Rendering →

💡

In Plain English

Overview

Cloudflare Browser Rendering — renamed Browser Run in 2026 — gives you programmatic headless Chrome on Cloudflare's global edge network without the operational pain of running Chromium pods yourself. The product has two integration shapes: Quick Actions (stateless one-call endpoints like /content, /screenshot, /pdf, /markdown, /scrape, /json, /links, /snapshot, and the new /crawl beta) and Browser Sessions (full Puppeteer / Playwright / CDP control with session management). Both are available on Free and Paid Workers plans. The Free plan includes 10 minutes of browser time per day and 3 concurrent browsers; Workers Paid ($5/mo base) includes 10 browser hours per month and 10 concurrent browsers (averaged monthly), then $0.09 per additional hour and $2.00 per additional concurrent browser. The /json Quick Action uses AI to extract structured data from a page in one call, and /crawl handles multi-page extraction. Compare with <a href="/tools/browserbase">Browserbase</a> for a managed Playwright-first alternative, <a href="/tools/firecrawl-ai">Firecrawl</a> for crawler/scrape-first, <a href="/tools/browser-use">Browser Use</a> for agent-driven browser control, and <a href="/tools/stagehand">Stagehand</a> for natural-language Playwright.

🎨

Vibe Coding Friendly?

▼

Difficulty:intermediate

Suitability for vibe coding depends on your experience level and the specific use case.

Learn about Vibe Coding →

Was this helpful?

Editorial Review

Cloudflare Browser Rendering revolutionizes web scraping and browser automation with global scale and edge performance. The viral /crawl endpoint and AI-powered extraction make it a game-changer for data-intensive applications.

Key Features

•Browser Automation
•Screenshot Generation
•PDF Creation
•Web Crawling
•Data Extraction
•Session Management

Pricing Plans

Workers Free

Free

Workers Paid

$5/month Workers Paid base

Enterprise

Custom

See Full Pricing →Free vs Paid →Is it worth it? →

Ready to get started with Cloudflare Browser Rendering?

View Pricing Options →

Getting Started with Cloudflare Browser Rendering

1Sign up for Cloudflare and enable Browser Rendering in your dashboard
2Choose between REST API for simple tasks or Workers for complex automation
3Test with a basic screenshot or PDF generation request
4Explore the /crawl endpoint for content discovery and extraction
5Scale to batch processing and session management for production workflows

Ready to start? Try Cloudflare Browser Rendering →

Best Use Cases

🎯

AI agents that need to read modern SPA content rendered via JavaScript (one /content or /markdown call)

⚡

Multi-page crawlers using /crawl beta for documentation, e-commerce, and knowledge-base scraping

🔧

Generating screenshots and PDFs at scale for OG images, invoices, and report exports

🚀

Workers backends that need to spawn a headless browser for a few seconds and tear it down

Integration Ecosystem

7 integrations

Cloudflare Browser Rendering works with these platforms and services:

☁️ Cloud Platforms

cloudflare

🌐 Browsers

chromechromium

💾 Storage

⚡ Code Execution

cloudflare-workers

🔗 Other

webhooksrest-api

View full Integration Matrix →

Limitations & What It Can't Do

We believe in transparent reviews. Here's what Cloudflare Browser Rendering doesn't handle well:

⚠Browser automation costs 10-100x more than simple HTTP requests due to resource-intensive Chrome instances
⚠Debugging complex browser workflows in serverless environments lacks traditional development tools and logging
⚠Complete dependency on Cloudflare's global infrastructure creates vendor lock-in for browser automation workflows
⚠Sub-100ms cold starts still add latency compared to pre-warmed browser instances in dedicated solutions
⚠Session management complexity increases for applications requiring persistent browser state across multiple requests
⚠Limited customization options for specialized browser configurations or non-standard automation requirements

Pros & Cons

✓ Pros

✓Quick Actions (/screenshot, /pdf, /markdown, /scrape, /json, /crawl) are exactly the surface AI agents want
✓$0.09 per browser-hour and $2.00 per extra concurrent browser is among the cheapest hosted headless Chrome on the market
✓Native MCP servers (Browser Run MCP, WebMCP, Playwright MCP) let coding agents drive it directly

✗ Cons

✗10 concurrent browsers on Workers Paid is generous but not unlimited — high-burst crawlers need enterprise tiers
✗/crawl Quick Action is still beta and crawl-depth/breadth controls are evolving
✗Some advanced Playwright features lag the upstream release by a few weeks

Frequently Asked Questions

How does Cloudflare Browser Rendering compare to traditional scraping services?+

Browser Rendering runs actual Chrome instances on Cloudflare's edge network, providing true JavaScript execution and DOM manipulation capabilities. This enables handling modern SPAs, complex user interactions, and visual content that traditional scrapers miss. The global distribution and massive scale make it ideal for high-volume applications, though it's more expensive per request than simple HTTP scraping.

Can I use existing Puppeteer or Playwright scripts?+

Yes, Browser Rendering provides compatible APIs for both Puppeteer and Playwright. You can port existing automation scripts with minimal changes, though some features may have limitations in the serverless environment. The REST API is also available for language-agnostic integration without browser automation libraries.

What are the performance characteristics at scale?+

Browser Rendering is designed for massive scale with thousands of concurrent browser sessions and sub-100ms cold start times. The global edge deployment ensures consistent performance worldwide. Session management can further improve performance by reusing browser contexts across requests, reducing overhead for multi-step workflows.

How does pricing work for browser automation?+

Pricing is based on browser execution time, with costs varying by the complexity and duration of operations. Simple screenshots or data extraction typically cost fractions of a cent, while long-running automation workflows cost more. The free tier provides 1,000 requests monthly for testing, with pay-as-you-go pricing for production use.

🔒 Security & Compliance

🛡️ SOC2 Compliant

✅

SOC2

Yes

✅

GDPR

Yes

❌

HIPAA

✅

SSO

Yes

—

Self-Hosted

Unknown

❌

On-Prem

✅

RBAC

Yes

✅

Audit Log

Yes

✅

API Key Auth

Yes

❌

Open Source

✅

Encryption at Rest

Yes

✅

Encryption in Transit

Yes

Data Retention: configurable

Data Residency: GLOBAL

📋 Privacy Policy →🛡️ Security Page →

🦞

New to AI tools?

Read practical guides for choosing and using AI tools

Read Guides →

Get updates on Cloudflare Browser Rendering and 370+ other AI tools

Weekly insights on the latest AI tools, features, and trends delivered to your inbox.

What's New in 2026

Launched the viral /crawl endpoint that gained 9.2M views on X, added AI-powered data extraction via natural language prompts, introduced Stagehand integration for intent-based browser control, and expanded global availability to 300+ edge locations.

Alternatives to Cloudflare Browser Rendering

Browserbase

Browser Automation

Managed headless-browser infrastructure for AI agents — spins up isolated Chromium sessions with stealth defenses, proxy rotation, and live-view debugging so your agent can browse the real web without you running the fleet.

Firecrawl

Web Scraping & Data Extraction

Firecrawl is the context API for AI agents that turns any website into clean Markdown or structured JSON. It handles crawling, scraping, extraction, and search across dynamic and JavaScript-heavy pages so agents can ingest live web data without wrestling with browsers, proxies, or brittle selectors. Firecrawl exposes both a REST API and an official Model Context Protocol (MCP) server so any MCP-compatible client — Claude, Cursor, Windsurf, VS Code — can crawl the web natively.

ScrapingBee

Search & Discovery

ScrapingBee is a web scraping API for fetching pages without managing proxies, browsers, or anti-bot defenses. It supports JavaScript rendering, AI-assisted extraction, Markdown and JSON outputs, screenshots, dedicated scraper APIs, and integrations for automation and AI workflows.

Browser Use

Browser Automation

Browser Use is an open-source Python harness plus a paid cloud platform that lets AI agents drive real web browsers with stealth fingerprints, residential proxies, and vision-based task automation.

View All Alternatives & Detailed Comparison →

User Reviews

No reviews yet. Be the first to share your experience!

Quick Info

Try Cloudflare Browser Rendering Today

Get started with Cloudflare Browser Rendering and see if it's the right fit for your needs.

Get Started →

Need help choosing the right AI stack?

Take our 60-second quiz to get personalized tool recommendations

Find Your Perfect AI Stack →

Want a faster launch?

Explore 20 ready-to-deploy AI agent templates for sales, support, dev, research, and operations.

Browse Agent Templates →

More about Cloudflare Browser Rendering

Pricing Review Alternatives Free vs Paid Pros & Cons Worth It?Tutorial

📚 Related Articles

Firecrawl vs Cloudflare Crawl API: Which Web Scraper for AI Agents? (2026)

Compare Firecrawl and Cloudflare's new Browser Rendering crawl endpoint for AI agent web scraping. Features, pricing, performance analysis for RAG pipelines and data extraction.

2026-03-128 min read

Overview

Getting Started with Cloudflare Browser Rendering

1Sign up for Cloudflare and enable Browser Rendering in your dashboard

2Choose between REST API for simple tasks or Workers for complex automation

3Test with a basic screenshot or PDF generation request

4Explore the /crawl endpoint for content discovery and extraction

5Scale to batch processing and session management for production workflows

Best Use Cases

🎯

AI agents that need to read modern SPA content rendered via JavaScript (one /content or /markdown call)

⚡

Multi-page crawlers using /crawl beta for documentation, e-commerce, and knowledge-base scraping

🔧

Generating screenshots and PDFs at scale for OG images, invoices, and report exports

🚀

Workers backends that need to spawn a headless browser for a few seconds and tear it down

Limitations & What It Can't Do

We believe in transparent reviews. Here's what Cloudflare Browser Rendering doesn't handle well:

⚠Browser automation costs 10-100x more than simple HTTP requests due to resource-intensive Chrome instances

⚠Debugging complex browser workflows in serverless environments lacks traditional development tools and logging

⚠Complete dependency on Cloudflare's global infrastructure creates vendor lock-in for browser automation workflows

⚠Sub-100ms cold starts still add latency compared to pre-warmed browser instances in dedicated solutions

⚠Session management complexity increases for applications requiring persistent browser state across multiple requests

⚠Limited customization options for specialized browser configurations or non-standard automation requirements

Pros & Cons

✓ Pros

✓Quick Actions (/screenshot, /pdf, /markdown, /scrape, /json, /crawl) are exactly the surface AI agents want
✓$0.09 per browser-hour and $2.00 per extra concurrent browser is among the cheapest hosted headless Chrome on the market
✓Native MCP servers (Browser Run MCP, WebMCP, Playwright MCP) let coding agents drive it directly

✗ Cons

✗10 concurrent browsers on Workers Paid is generous but not unlimited — high-burst crawlers need enterprise tiers
✗/crawl Quick Action is still beta and crawl-depth/breadth controls are evolving
✗Some advanced Playwright features lag the upstream release by a few weeks

Frequently Asked Questions