Fair usage.

Authenticated API requests share a limit of 10 requests per second per user across nodes. Bulk file actions accept at most 100 unique file codes. Respect HTTP 429 responses and Retry-After, use backoff, and avoid retry loops that increase load.

Legacy APIs can report failures inside an HTTP 200 response body. Check the envelope status as well as the HTTP status. See the API documentation for both formats. Always use HTTPS and keep credentials out of logs and public code.

Per-file upload limits are 20 GiB for free accounts and 50 GiB for active Premium accounts. The standard free storage allocation is 200 GiB; account-specific quotas may differ.

Remote uploads have a standard limit of 20 queued or working jobs for free accounts and at least 100 for active Premium accounts. Account configuration may raise the limit. A slot stays occupied until the job completes or fails.

Premium has no fixed storage quota. This does not mean unlimited throughput, concurrent jobs or processing capacity. Upload concurrency, file limits, rate limits and abuse protections still apply.

Do not bypass limits, rotate accounts or keys to evade controls, create artificial views or downloads, run disruptive automation, upload malware, or use content without the required rights. Keep backups and monitor failed uploads before retrying them.

Free files can be pruned for inactivity; see retention details. No additional numeric suspension thresholds or guaranteed throughput are established by this draft.

Check your dashboard for account-specific limits and contact support with expected request rates, file sizes and concurrent jobs. Capacity increases require confirmation.