Pricing

Note

Workflows is included in both the Free and Paid Workers plans. Billing for Workflows steps and storage will apply starting August 10th, 2026.

Workflows uses Workers Standard pricing for CPU time and requests. Workflows are billed on four dimensions:

• CPU time: the total amount of compute (measured in milliseconds) consumed by a given Workflow.
• Requests (invocations): the number of Workflow invocations. Subrequests made from a Workflow do not incur additional request costs.
• Storage: the total amount of storage (measured in GB) persisted by your Workflows.
• Steps: the number of steps executed by your Workflows.

A Workflow that is waiting on a response to an API call, paused as a result of calling step.sleep, or otherwise idle, does not incur CPU time.

Workflows pricing

Unit	Workers Free	Workers Paid
Requests (millions)	100,000 per day (shared with Workers requests)	10 million included per month + $0.30 per additional million
CPU time (ms)	10 milliseconds of CPU time per invocation	30 million CPU milliseconds included per month + $0.02 per additional million CPU milliseconds
Storage (GB-mo)	1 GB	1 GB included per month + $0.20/ GB-month
Steps	3,000 per day	500,000 included per month + $0.80/ additional 100,000 per month

Cloudflare will not bill step and storage usage before the start date announced in the Workflows billing changelog.

CPU limits

You can increase the CPU limit available to your Workflow instances up to 5 minutes per Workflow by setting the limits.cpu_ms property in your Wrangler configuration.

Storage Usage

Storage is billed using gigabyte-month (GB-month) as the billing metric, identical to Durable Objects SQL storage. A GB-month is calculated by averaging the peak storage per day over a billing period (30 days).

• Storage is calculated across all instances, and includes running, errored, sleeping, and completed instances.
• By default, instance state is retained for 3 days on the Free plan and 30 days on the Paid plan.
• When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows. Refer to the retention option in WorkflowInstanceCreateOptions for more information.
• Deleting instances via the Workers API, Wrangler CLI, REST API, or dashboard will free up storage. It may take a few minutes for storage limits to update.

An instance that attempts to store state when you have reached the storage limit on the Free plan will throw an error.

Frequently Asked Questions

Frequently asked questions related to Workflows pricing:

Are there additional costs for Workflows?

Yes. Workflows are priced based on the same compute (CPU time) and requests (invocations) as Workers, as well as storage (state from a Workflow) and steps.

Are Workflows available on the Workers Free plan?

Yes.

What is a Workflow invocation?

A Workflow invocation is when you trigger a new Workflow instance: for example, via the Workers API, wrangler CLI, or REST API. Steps within a Workflow are not invocations.

How do Workflows show up on my bill?

Workflows are billed as Workers, and share the same CPU time and request SKUs. Workflows billing also includes storage and step usage.

Are there any limits to Workflows?

Refer to the published limits documentation.