At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Supported file up to 350 KiB | Use direct upload | Immediate ingestion result | Resolver payload remains bounded |
| Supported file over 350 KiB | Create a staged session | Server-owned upload identity | Maximum 25 MiB |
| File bytes | Upload ordered chunks | Hash-checked chunk receipts | 256 KiB and no more than 100 chunks |
| Complete staged session | Finalize and assemble | Verified file ingestion | Session expires after one hour |
How it works
- Open Upload controlled evidence.
- Select a supported file.
- Set its retention class and date.
- Select Upload evidence.
- Let the UI choose direct or staged upload by size.
- Keep the page open until final verification completes.
Example
A 12 MiB XLSX workbook exceeds the direct-upload limit. The UI opens a staged session and sends 256 KiB chunks. The server verifies each chunk, checks the assembled file against its declared SHA-256 value, then runs the normal ingestion path.
What this does not mean
Size is only one gate. Extension and MIME type must match the allow-list. Encrypted, malformed, unsupported, expired, incomplete, or parser-budget failures remain visible. A successful upload does not approve the content.
Related questions
Next step
Check file type, retention, and size before starting the upload.
View on Atlassian Marketplace