Cloudflare Browser Rendering

Give your AI agent headless browser superpowers at the edge

Your AI agent renders web pages on Cloudflare's global network, captures pixel-perfect screenshots, scrapes structured data from HTML elements, and delivers full DOM snapshots. All from a single conversation, running on headless browsers with near-zero cold start.

Chosen by 800+ global brands across industries

Browser automation without the browser

Capture screenshots, extract page data, and render full snapshots through headless Chromium instances on Cloudflare's edge, triggered by your AI agent in real time.

Cloudflare Browser Rendering

Use Cases

Visual web intelligence on demand

From competitive monitoring to compliance archiving, see how AI agents use headless browsers on Cloudflare's edge to capture, scrape, and analyze web content automatically.

Competitor Page Monitoring Made Visual

Your marketing team wants daily screenshots of a competitor's pricing page. Your AI Agent navigates to the URL using Cloudflare's headless browser, captures a full-page screenshot with a desktop viewport, and stores the image. When someone asks for changes, the agent compares today's capture with last week's. Visual intelligence without manual browsing.

Automated Price Extraction from Vendor Sites

Your procurement team needs current pricing from three supplier websites. Your AI Agent scrapes each page using CSS selectors targeting price elements, extracts the text and attributes, and compiles a comparison table in the conversation. The agent handles JavaScript-rendered pages that traditional scrapers miss because it runs real Chromium on Cloudflare's network.

Compliance Archival of Published Content

Regulations require your legal team to archive published terms and conditions pages weekly. Your AI Agent takes a full snapshot of each page, capturing both the rendered HTML and a screenshot in one request. The DOM text provides searchable records while the screenshot serves as visual proof of what was displayed on the capture date.

Try
Cloudflare Browser Rendering

Cloudflare Browser Rendering

FAQs

Frequently Asked Questions

What rendering engine does Cloudflare Browser Rendering use?

It runs headless Chromium instances on Cloudflare's global edge network. Pages render with full JavaScript execution, CSS rendering, and modern web API support, identical to what a real Chrome browser would display. This means dynamic, JavaScript-heavy sites are captured accurately.

Can the agent scrape pages that require JavaScript to load content?

Yes. Because Browser Rendering executes real Chromium, it handles single-page applications, dynamically loaded content, and lazy-loaded elements. The agent can set a waitForSelector or waitForTimeout to ensure target elements are fully rendered before scraping begins.

What permissions does the Cloudflare API Token need for Browser Rendering?

Your API Token requires the 'Browser Rendering - Edit' permission. Create the token in your Cloudflare dashboard under My Profile, API Tokens. You also need to provide your Cloudflare Account ID, found on the Workers & Pages overview page.

Can screenshots capture specific regions of a page instead of the full viewport?

Yes. The screenshotOptions parameter accepts a clip object with x, y, width, and height values to capture a specific rectangular region. Alternatively, set fullPage to true to capture the entire scrollable page beyond the viewport.

How does caching work for screenshots and scrapes?

Every endpoint accepts a cacheTTL parameter in seconds. Set it to a positive integer to cache results for that duration, reducing repeated renders of the same page. Set cacheTTL to 0 to disable caching and always get a fresh render.

Does Tars store the scraped data or screenshots?

No. Screenshots and scraped HTML data are returned directly in the API response during the conversation. Tars does not persist rendered content, DOM snapshots, or image captures. If you need long-term storage, configure your agent to export results to your own storage system.

Can I scrape multiple elements from a page in one request?

Yes. The scrape endpoint accepts an array of CSS selectors in the elements parameter. The agent extracts text, innerHTML, attributes, and bounding box dimensions for every matching element across all provided selectors in a single API call.

How is this different from using Puppeteer or Playwright on my own servers?

Running headless browsers on your infrastructure requires managing Chromium installations, handling memory, and scaling capacity. Cloudflare Browser Rendering runs on their global edge network with near-zero cold start, built-in caching, and no server maintenance. Your agent gets browser access without provisioning any compute resources.

How to add Tools to your AI Agent

Supercharge your AI Agent with Tool Integrations

Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security

We’ll never let you lose sleep over privacy and security concerns

At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.

GDPR
ISO
SOC 2
HIPAA

Still scrolling? We both know you're interested.

Let's chat about AI Agents the old-fashioned way. Get a demo tailored to your requirements.

Schedule a Demo