---
title: Limits · Cloudflare Pipelines Docs
description: If you consistently exceed the requests per second or throughput limits, your pipeline might not be able to keep up with the load. The pipeline will communicate backpressure by returning a 429 response to HTTP requests or throwing an error if using the Workers API.
lastUpdated: 2025-04-10T15:21:35.000Z
source_url:
  html: https://397b66cf.preview.developers.cloudflare.com/pipelines/platform/limits/index.md
  md: https://397b66cf.preview.developers.cloudflare.com/pipelines/platform/limits/
---

| Feature | Limit |
| - | - |
| Maximum requests per second, per pipeline | 14,000 default (configurable up to 100,000) |
| Maximum payload per request | 1 MB |
| Maximum data throughput per pipeline | 14 MB/s default (configurable up to 100 MB/s) |
| Shards per pipeline | 2 default (configurable up to 15) |
| Maximum batch size | 100 MB |
| Maximum batch records | 10,000,000 |
| Maximum batch duration | 300s |

## Exceeding requests per second or throughput limits

If you consistently exceed the requests per second or throughput limits, your pipeline might not be able to keep up with the load. The pipeline will communicate backpressure by returning a 429 response to HTTP requests or throwing an error if using the Workers API.

If you are consistently seeing backpressure from your pipeline, consider the following strategies:

* Increase the [shard count](https://developers.cloudflare.com/pipelines/build-with-pipelines/shards) to increase the maximum throughput of your pipeline.
* Send data to a second pipeline if you receive an error. You can setup multiple pipelines to write to the same R2 bucket.
