AO-PDF Operating Limits
Every workflow processes locally. Transformations use the AO-PDF operation worker; assurance parsing uses PDF.js's local worker while local rendering, hashing and packaging remain in the browser. The common boundary is 100 MiB per file, 250 MiB aggregate, up to 500 PDF pages, a 120-second timeout and a 1,024 MiB estimated working-memory limit. Permanent redaction is additionally capped at 50 pages. Encrypted PDFs are unsupported.
| Tool | Inputs | Page limit | Material limitations |
|---|---|---|---|
| Merge PDFs | 2–20 | 500 |
|
| Split PDF | 1–1 | 500 |
|
| Optimize PDF | 1–1 | 500 |
|
| Rotate Pages | 1–1 | 500 |
|
| Delete Pages | 1–1 | 500 |
|
| Add Watermark | 1–1 | 500 |
|
| Add Page Numbers | 1–1 | 500 |
|
| Flatten Form Fields | 1–1 | 500 |
|
| Images to PDF | 1–20 | 20 |
|
| Inspect PDF | 1–1 | 500 |
|
| Compare Documents | 2–2 | 500 |
|
| Evidence Manifest | 1–20 | 500 |
|
| Permanent Redaction | 1–1 | 50 |
|
Estimated memory is not measured memory
AO-PDF conservatively estimates working bytes from input size, decoded image pixels, page-object overhead, simultaneous outputs, serialization duplication and operation multipliers. Browsers do not expose a reliable cross-browser measurement of PDF-library memory. Passing admission does not guarantee that a device can complete an operation.