# Cloudflare Workflows has started charging for steps — durable jobs now need a cost model Cloudflare's durable Workflows product has crossed an important line for builders: step and stored-state usage are now billable on Workers Paid plans. The prices are not huge, but the change means workflow shape — not just CPU and requests — can affect the bill. Cloudflare Workflows now prices steps and persisted state on paid plans, making workflow structure and retention part of the cost calculation for durable jobs and AI automation. - Status: Active - Published: 2026-08-13T22:13:04+12:00 - Updated: 2026-08-13T22:13:04+12:00 - Categories: Web Development, Cloud & Infrastructure - Tags: AI infrastructure, Cloud pricing, Cloudflare, Durable execution, Workers, Workflows - Canonical HTML: https://beyondthe.news/dossiers/cloudflare-workflows-step-storage-billing ## What changed Cloudflare said step and storage billing for Workflows would begin no earlier than 10 August 2026. Its current pricing documentation now defines four billable dimensions for Workflows: requests, CPU time, storage and steps. On Workers Paid plans, 500,000 Workflow steps are included each month, with additional steps priced at $0.80 per 100,000. One GB-month of persisted Workflow state is included, with additional storage priced at $0.20 per GB-month. Requests and CPU time continue to use the wider Workers pricing model. Free-plan users receive 3,000 steps per day and 1 GB-month of storage without paid overages. ## Why it matters Cloudflare Workflows is attractive precisely because it hides much of the machinery needed for durable execution: retries, waiting, persisted state and long-running multi-step jobs. That is especially useful for AI products, automation and human-in-the-loop systems where a task may pause for minutes or days. The new pricing does not make Workflows expensive by default, but it changes what builders need to measure. A design with lots of tiny steps, long retention and large persisted results can cost differently from one that performs the same business task with fewer checkpoints and externalizes bulky state. The architecture of the workflow is now part of its unit economics. ## A step is now an economic unit Cloudflare bills each Workflow step as a unit of work, with the paid plan including 500,000 steps per month before an $0.80 charge for each additional 100,000. The pricing page notes that rollback handlers and retries are not counted as steps for billing. For a low-volume internal automation this may barely register. At product scale, however, a workflow that expands one customer action into dozens or hundreds of persisted steps can turn step count into a meaningful design variable. Teams should measure completed-business-task cost rather than looking at the headline price of an individual step. ## Persisted state also has a carrying cost Workflows automatically persists state so executions can survive waits, failures and restarts. On the paid plan, the first 1 GB-month is included and additional storage costs $0.20 per GB-month. Completed state can be retained for up to 30 days on the paid plan, and developers can configure a shorter retention period when they do not need that history. Large binary outputs still count toward storage, so Cloudflare recommends storing very large or long-lived artifacts elsewhere, such as R2, and persisting a reference instead. ## Waiting is still cheap in the way that matters A Workflow that is waiting on an API call, sleeping or otherwise idle does not consume CPU time. Waiting instances also do not count toward active concurrency limits. That preserves one of durable execution's main advantages: a process can pause for an approval, retry window or external event without paying for a continuously running server process. The pricing change therefore does not turn Workflows into metered wall-clock compute. It adds charges around the durable structure wrapped around the compute. ## AI automation makes this worth watching Agentic and AI-heavy applications often create exactly the kind of workloads Workflows is designed for: multi-step calls, long waits, retries, external APIs and human approvals. Those applications can also generate unusually large intermediate outputs and unpredictable execution paths. Builders using Workflows for agents should put step count and persisted-state size next to token spend in their observability. An AI task that is cheap at the model layer can still be inefficient if the surrounding orchestration repeatedly checkpoints or retains bulky results. ## Key details - Cloudflare announced that Workflows step and storage billing would start no earlier than 10 August 2026. - Workers Paid includes 500,000 Workflow steps per month, then charges $0.80 per additional 100,000 steps. - Workers Paid includes 1 GB-month of Workflow storage, then charges $0.20 per additional GB-month. - The Free plan includes 3,000 steps per day and 1 GB-month of storage. - Workflow requests and CPU time use the standard Workers pricing model. - Idle time while a Workflow sleeps or waits for I/O does not incur CPU time. ## Builder takeaways - Add step count and persisted-state size to production observability before your workflow volume grows. - Calculate cost per completed business task, not per Workflow invocation. - Use shorter retention periods for completed state when long history is not useful. - Keep large files and long-lived artifacts in purpose-built storage such as R2 and persist references in the Workflow. - For AI workflows, track infrastructure cost beside model-token cost; cheap inference does not guarantee a cheap end-to-end task. ## What to watch - Whether real-world agent workloads make step count a noticeable part of total infrastructure cost. - Whether Cloudflare changes included step allowances as Workflows adoption grows. - How much state developers retain in practice once storage appears directly on the bill. - Whether Cloudflare adds more granular cost controls or per-workflow budgets. - How Workflows pricing compares with competing durable-execution products for AI-heavy applications. ## Uncertainties - Cloudflare's changelog stated billing would begin no earlier than 10 August; account-level billing timing and enterprise contracts may differ. - The practical cost impact depends heavily on workflow shape, retention and volume, so there is no useful universal cost estimate for a typical application. ## Timeline - **3 March 2026 — Paid Workflow step limits expand:** Cloudflare raises the configurable maximum to 25,000 steps per Workflow instance. - **7 July 2026 — Cloudflare announces per-step billing:** The company publishes step pricing and says step and storage billing will begin no earlier than 10 August. - **10 August 2026 — Earliest announced billing start:** Step and storage usage becomes eligible for billing on Workers Paid plans under the published pricing model. ## Sources - [Pricing](https://developers.cloudflare.com/workflows/reference/pricing/) — Cloudflare Workflows Docs · Official pricing documentation · 2026-07-21T12:00:00+12:00. Current Workflows pricing dimensions, included usage and overage rates. - [Workflows Changelog](https://developers.cloudflare.com/changelog/product/workflows/) — Cloudflare Developers · Official changelog · 2026-07-07T12:00:00+12:00. Announcement of per-step pricing and the August 10 billing start date. - [Limits](https://developers.cloudflare.com/workflows/reference/limits/) — Cloudflare Workflows Docs · Official technical documentation · 2026-06-15T12:00:00+12:00. Step, state, concurrency, retention and execution limits. - [Cloudflare Workflows overview](https://developers.cloudflare.com/workflows/) — Cloudflare Developers · Official product documentation · 2026-06-02T12:00:00+12:00. Durable execution model, retries, long-running state and human-in-the-loop use cases.