cloudflare-browser-rendering

Automate browser interactions via REST endpoints and Workers bindings.

Updated Jul 23, 2025
One-click install
npx skills add https://github.com/levanminhduc/LuongHoaThoNew --skill cloudflare-browser-rendering-levanminhduc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloudflare-browser-rendering
Source: https://github.com/levanminhduc/LuongHoaThoNew/tree/main/.claude/skills/cloudflare-browser-rendering
Command: npx skills add https://github.com/levanminhduc/LuongHoaThoNew --skill cloudflare-browser-rendering-levanminhduc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cloudflare Browser Rendering provides REST API, Worker bindings (Puppeteer/Playwright), MCP server integration, and AI-assisted automation to render pages, take screenshots, generate PDFs, and scrape data.

Core Features & Use Cases

  • REST API Endpoints: /screenshot, /pdf, /content, /markdown, /scrape, /links, /json, /snapshot
  • Workers Bindings: Puppeteer/Playwright bindings with session reuse and caching
  • MCP Server & AI: Stagehand-like automation and model context protocols
  • Use Case: Generate a PDF report from a dynamic page and extract structured data

Quick Start

POST to the REST API with a target URL to receive a screenshot or content, or deploy a Worker to render pages.

Frequently Asked Questions about cloudflare-browser-rendering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate screenshots and PDF generation from dynamic web pages?▼

Cloudflare Browser Rendering automates screenshots and PDF generation through REST API endpoints or Worker bindings with Puppeteer/Playwright. POST a target URL to /screenshot or /pdf endpoints to render and capture pages server-side without running a browser locally.

Can I scrape dynamic content and extract structured data with browser automation?▼

Yes. Cloudflare Browser Rendering provides /scrape, /content, /markdown, /json, and /links endpoints to extract data from JavaScript-rendered pages. It supports session reuse and storage state for authenticated scraping workflows.

What's the difference between using REST API endpoints versus Worker bindings for browser rendering?▼

REST API endpoints offer quick, stateless rendering for screenshots and PDFs. Worker bindings with Puppeteer/Playwright provide programmatic control, session persistence, caching, and fine-grained automation within Cloudflare Workers for complex workflows.

Does Cloudflare Browser Rendering work with MCP servers and AI automation?▼

Yes. Cloudflare Browser Rendering integrates with MCP servers and supports AI-powered automation patterns similar to Stagehand, enabling model-driven browser interactions and intelligent data extraction.

Do I need to handle authentication and rate limiting when rendering pages at scale?▼

Cloudflare Browser Rendering supports session reuse with storage state for managing authentication. You must implement rate limiting and caching strategies within your Workers code or API calls to handle production-scale rendering safely.

Can I generate PDFs and take screenshots from REST API calls without deploying Workers code?▼

Yes. Cloudflare Browser Rendering's REST API allows direct POST requests to /screenshot and /pdf endpoints with a target URL, returning rendered output without requiring Worker deployment or local browser infrastructure.