Platform hub

PyPI limits

Distribution file, project storage, and responsible API-access limits. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  PyPI has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

ConstraintCurrent valueScopeVerified source
per-file uploadProjects can request an increase through the documented process when justified.100 MBDefault project limitPython Packaging AuthorityAug 22, 2026
aggregate project storageAll release files for the project contribute to aggregate storage.10 GBDefault project limitPython Packaging AuthorityAug 22, 2026
API rate posturePyPI requires responsible access, caching, identification, and supported APIs.No current edge-wide numeric rate; XML-RPC may rate-limitPublic APIsPython Packaging AuthorityAug 22, 2026

How to apply PyPI limits safely

The monitored baseline covers per-file upload, aggregate project storage, API rate posture. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active PyPI console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.

Specific limit pages

These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.

Compare alternatives

Official sources

View PyPI change history