Upload limits

The current Public API accepts files up to 100 MiB (104,857,600 bytes) at POST /api/v1/files.

Why the limit differs from the app

Public API uploads currently travel through the New Archive application server: the request is streamed to a temporary file and then stored in S3. The 100 MiB cap bounds application-server bandwidth, temporary disk use, and the lifetime of one HTTP request.

The browser app uses a different transport. It creates an S3 multipart upload and sends 10 MiB parts directly from the browser to object storage using short-lived presigned URLs. That app-only path accepts files up to 2 GiB.

Files over 100 MiB

API keys cannot currently access the app's presigned multipart procedures. For now, upload files between 100 MiB and 2 GiB through the New Archive app. Increasing the request size does not opt into direct-to-S3 upload.

json

{
  "error": {
    "code": "payload_too_large",
    "message": "File exceeds the 104857600 byte direct-upload cap"
  }
}

A future public multipart flow can raise the API limit without proxying file bytes through the app server. Until that flow is released and documented, 100 MiB is the authoritative public limit.

PreviousSearching NextErrors