Current documented limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| included package storageFree organizations also receive 500 MB included storage. | Free: 500 MB; Pro/Team: 2 GB; Enterprise Cloud: 50 GB | Account plan | GitHubAug 22, 2026 |
| included monthly transferPackage transfer resets monthly and some GitHub Actions downloads are treated differently. | Free: 1 GB; Pro/Team: 10 GB; Enterprise Cloud: 100 GB | Account plan | GitHubAug 22, 2026 |
How to apply GitHub Packages limits safely
The monitored baseline covers included package storage, included monthly transfer. 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.
- Match the production workload to the exact scope printed beside each value and confirm it in the active GitHub Packages console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- 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.
GitHub Packages Storage Limits by Plan
GitHub Packages Storage Limits by Plan, verified against GitHub Packages's official documentation with scope, implementation impact, caveats, and a direct check.
GitHub Packages Data Transfer Limits
GitHub Packages Data Transfer Limits, verified against GitHub Packages's official documentation with scope, implementation impact, caveats, and a direct check.