> ## Documentation Index
> Fetch the complete documentation index at: https://developer.litprotocol.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits

> Default resource limits for Lit Actions on the Chipotle network.

## Limits

The following limits apply to all Lit Action executions on Chipotle. They are designed to keep the network stable and fair for all users while covering the vast majority of real-world use cases.

***

### Code & Upload

| Limit                                         | Default |
| --------------------------------------------- | ------- |
| Maximum combined `code` + `js_params` payload | 16 MB   |
| Maximum IPFS action size                      | N/A     |

Action code and `js_params` share a single 16 MB budget — `code` and `js_params` may each be as large as you like as long as the sum of their sizes (code bytes + JSON-serialized `js_params` bytes) does not exceed 16 MB. Downloading actions via IPFS is not currently supported. If your action requires large static data, consider fetching it at runtime via `fetch` rather than bundling it into the action itself.

***

### Execution

| Limit                                     | Default    |
| ----------------------------------------- | ---------- |
| Maximum execution time                    | 15 minutes |
| Maximum memory                            | 64 MB      |
| Maximum outbound HTTP requests per action | 50         |
| Maximum response payload size             | 1 MB       |
| Maximum console log output                | 100 KB     |
| Maximum key/signature requests per action | 10         |

Actions that exceed the execution time limit are terminated and return a timeout error. Long-running workflows should be broken into smaller actions or offload heavy computation to an external service and fetch the result.

***

### Need Higher Limits?

The defaults above are suitable for most development and production workloads. If your use case requires higher limits — more throughput, longer execution time, larger payloads, or increased concurrency — we're happy to discuss it.

Reach out through any of the following:

* **Email:** [support@litprotocol.com](mailto:support@litprotocol.com)
* **Discord:** [litgateway.com/discord](https://litgateway.com/discord)
* **Telegram:** Contact the team via the Lit Protocol Telegram channel

When you reach out, include a brief description of your use case and the specific limits you need — this helps us respond quickly with the right configuration for your account.