
Cloudflare Workers is an edge serverless platform that runs code across Cloudflare's global network.
Key Features:
Whether you're building lightweight scrapers, deploying proxy endpoints, or processing webhook data at the edge, Cloudflare Workers provides the speed and global distribution your applications demand.
Web scraping workflow
Cloudflare Workers can make outbound HTTP requests through the Fetch API. A scraping-related Worker can coordinate a bounded fetch or call an extraction service, then pass its response into your own processing logic.
Use this for small HTTP-oriented collection steps or an API layer around a larger pipeline. Keep the accepted targets and outputs explicit so the endpoint does not become an unrestricted proxy.
The Fetch API retrieves responses; it does not execute a target page's JavaScript like a browser. Rendering requires a separate component. Runtime and subrequest limits still apply, and access controls, redirect validation, response-size limits and pacing belong in your implementation before accepting user-supplied URLs.
Cloudflare Workers runs application code on Cloudflare’s infrastructure, including HTTP handlers, APIs and scheduled work. Your Worker connects to the services and storage configured for the application.
Sources (checked ): Workers documentation
Workers has Free and Paid plans. Request and CPU allowances differ by plan, and additional storage or platform services can have their own charges. Estimate the Worker’s requests and compute usage separately from connected services.
Sources (checked ): Workers pricing
A Worker isolate has a 128 MB memory limit. CPU budgets, request allowances and subrequest limits depend on the plan and invocation type. CPU time and time spent waiting for network I/O are different measurements; consult the limits for the trigger your Worker uses.
Sources (checked ): Workers limits
Verified against the official Cloudflare Workers website and documentation.
Infrastructure · API / SaaS
Infrastructure · API / SaaS