> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/transfer-media-encode-and-publish/understand-upload-states-quotas-and-limits.md).

# Understand upload states, quotas, and limits

Reference Podigee upload states, resumability, file limits, quotas, and expiry.

## Upload states

| State          | Meaning and action                                              |
| -------------- | --------------------------------------------------------------- |
| `initializing` | Wait. Do not send bytes.                                        |
| `pending`      | The session can accept or resume transfer.                      |
| `uploading`    | Transfer or resume missing parts.                               |
| `completing`   | Wait for server validation.                                     |
| `aborting`     | Wait for cleanup.                                               |
| `completed`    | Use the upload ID before the session expires.                   |
| `aborted`      | The transfer ended and cannot resume.                           |
| `expired`      | Create a new session if the file is still needed.               |
| `failed`       | Inspect the error and create a new session only after recovery. |

Only `pending` and `uploading` are resumable byte-transfer states.

## Current limits

| Limit                                   | Value      |
| --------------------------------------- | ---------- |
| Multipart threshold                     | 30 MiB     |
| Multipart part size                     | 30 MiB     |
| Maximum file size                       | 20 GiB     |
| Maximum part count                      | 10,000     |
| Active sessions per account             | 10         |
| Active declared bytes per account       | 40 GiB     |
| Declared bytes per account per 24 hours | 100 GiB    |
| Declared parts per account per 24 hours | 20,000     |
| Signed URL lifetime                     | 15 minutes |
| Upload session lifetime                 | 24 hours   |

Clients must consume values returned by the server instead of hard-coding them. A completed upload must be attached during its session lifetime and can belong to only one production.

## Related tasks

* [Resume an interrupted media upload](/documentation/start-here/ai-agents/transfer-media-encode-and-publish/resume-an-interrupted-media-upload.md)
* [Complete or abort an upload](/documentation/start-here/ai-agents/transfer-media-encode-and-publish/complete-or-abort-an-upload.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/transfer-media-encode-and-publish/understand-upload-states-quotas-and-limits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.