# Document limits

Document experiences have separate limits for upload, storage transfer, table extraction, and human review. The smallest applicable limit governs the complete operation. A file accepted by one stage can still exceed the next stage's processing limit.

## Managed document upload

Managed upload accepts one file per handoff, up to 100 MiB. It requires a canonical single filename. Creating a document and replacing a revision are different requests: replacement is conditional on the expected current revision.

Managed mode stores an immutable revision and does not automatically start ordinary ingestion. For normal ingestion, accepted formats and the maximum number of files are configured by the App's upload control. Check that App's instructions rather than assuming the managed limit applies to every upload experience.

## Deletion requests

A managed deletion ticket has a fifteen-minute deadline from its original request. An exact retry does not extend that deadline. Limits over a rolling fifteen-minute interval are:

| Scope | New requests |
| --- | --- |
| Requester and requesting actor pair | 20 |
| Requesting user | 100 |
| Workspace | 1,000 |

These limits apply across Apps. Replaying the same recorded request does not charge it again. Reaching a limit does not authorize another actor to bypass the approval or request binding.

## Extraction and review

For document-to-table extraction, see [table limits](/docs/tables/limits), including selected sources, fields, capture bytes, and active drafts. For human-review evidence and generation, see [review limits](/docs/reviews/limits). For provider transfers and browser multipart uploads, see [storage limits](/docs/storage/limits).

When planning a large batch, choose the relevant files explicitly, split work by a meaningful source group, and verify each outcome. Do not treat an intake acknowledgement as proof that all selected documents were fully processed.