Workers, Now Even More Unbound: 15 Minutes, 100 Scripts, and No Egress Fees

Cloudflare Workers Unbound: Bigger Scripts, Longer Runs, No Transfer Fees

Cloudflare is making a notable push to position its Workers platform for heavier, data-centric workloads. The company has announced the elimination of data egress transfer fees for Workers Unbound and Durable Objects, effective immediately. This removes a significant cost barrier, as these fees traditionally discourage developers from moving substantial volumes of data in and out of a cloud provider's network.

This move is part of a broader trend for Cloudflare, following its earlier introduction of R2 Storage, which also waived similar egress charges. The company is also a member of the Bandwidth Alliance, a coalition of providers committed to reducing or eliminating these transfer costs. For existing Users Unbound customers, the change will be reflected directly on their next invoice.

Extended CPU Limits for Heavy Lifting

In addition to the pricing update, Cloudflare is extending support for more demanding computation. Developers can now allocate up to 15 minutes of CPU time per Worker request. While Workers are often associated with low-latency, user-facing tasks, this new limit aims to support heavy-duty, compute-intensive jobs, such as bulk batch processing via Cron Triggers.

To access the extended duration, you must ensure your Worker is running on the Unbound usage model. After confirming this in the Settings tab of the Worker, you can enable the longer runtime by navigating to the Triggers tab. There, adding a new Cron Trigger will display the appropriate maximum duration limit for the workload.

Higher Script Limits and Growing Bundles

Cloudflare is also eliminating a significant administrative hurdle by raising the account limit to 100 deployable Worker scripts. Combined with the Services architecture, this allows users to maintain up to 100 distinct environments, providing more room to migrate and isolate various application use cases without hitting hard constraints.

The platform is also preparing developers for future, larger applications. Cloudflare has stated it plans to support bigger script sizes on Workers, which would enable the use of heavier libraries and tools. This includes the potential to run code compiled to WebAssembly (WASM), such as esbuild, a bundler that has been demonstrated on the network in a script exceeding 2MB compressed.

These changes represent a combined effort to remove the common limits—cost, time, and volume—that have traditionally restricted serverless deployments. The goal is to make the edge network a viable option not just for quick API calls, but for substantial application workloads and data-heavy processing.