ClaudeCloudflare Developer PlatformMay 28, 2026, 12:00 AM

Browser Run - Use Browser Run Quick Actions directly from Workers

A condensed section focused on the key takeaways first.

Original Post

Quick Digest

Summary

A condensed section focused on the key takeaways first.

claudeen

Browser Run - Use Browser Run Quick Actions directly from Workers Summary

Key Points

  • Point 1: Changelog New updates and improvements at Cloudflare.
  • Point 2: Subscribe to RSS View RSS feeds ← Back to all posts Use Browser Run Quick Actions directly from Workers May 28, 2026 Browser Run You can now call Browser Run Quick Actions directly
  • Point 3: This simplifies how Workers interact with Browser Run by removing the need for API tokens or external HTTP requests.

Summary

This is an English summary of "Browser Run - Use Browser Run Quick Actions directly from Workers" published on 2026-05-28.

Key Points

  • Point 1: Changelog New updates and improvements at Cloudflare.
  • Point 2: Subscribe to RSS View RSS feeds ← Back to all posts Use Browser Run Quick Actions directly from Workers May 28, 2026 Browser Run You can now call Browser Run Quick Actions directly
  • Point 3: This simplifies how Workers interact with Browser Run by removing the need for API tokens or external HTTP requests.

Full Translation

Translations

A translation section that keeps the flow of the original article.

claudeja

Browser Run - Use Browser Run Quick Actions directly from Workers(原文タイトル)

概要

公開日: 2026-05-28 翻訳生成に失敗したため、原文をそのまま保存しています。

原文

Changelog New updates and improvements at Cloudflare. Subscribe to RSS View RSS feeds ← Back to all posts Use Browser Run Quick Actions directly from Workers May 28, 2026 Browser Run You can now call Browser Run Quick Actions directly from a Cloudflare Worker using the quickAction() method on the browser binding. This simplifies how Workers interact with Browser Run by removing the need for API tokens or external HTTP requests. Your Worker communicates with Browser Run directly over Cloudflare's network, resulting in simpler code and lower latency. With the quickAction() method you can: Capture screenshots from URLs or HTML Generate PDFs with custom styling, headers, and footers Extract HTML content from fully rendered pages Convert pages to Markdown Extract structured JSON using AI Scrape elements with CSS selectors Get all links from a page Capture snapshots (HTML + screenshot in one request) To get started, add a browser binding to your Wrangler configuration: wrangler.jsonc wrangler.toml JSONC { " compatibility_date " : "2026-03-24" , " browser " : { " binding " : "BROWSER" } } TOML compatibility_date = "2026-03-24" [ browser ] binding = "BROWSER" Then call any Quick Action directly from your Worker. For example, to capture a screenshot: JavaScript TypeScript JavaScript const screenshot = await env . BROWSER . quickAction ( "screenshot" , { url : "https://www.cloudflare.com/" , } ) ; TypeScript const screenshot = await env . BROWSER . quickAction ( "screenshot" , { url : "https://www.cloudflare.com/" , } ) ; The quickAction() method requires a compatibility date of 2026-03-24 or later. For setup instructions and the full list of available actions, refer to Browser Run Quick Actions . Resources API New to Cloudflare? Directory Sponsorships Open Source Cloudflare Research Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Cloudflare Labs Speed Test Is BGP Safe Yet? Certificate Transparency Community Community forum X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings Was this helpful? Yes No

Browser Run - Use Browser Run Quick Actions directly from Workers | Cloudflare Developer Platform | DocsDigest