Quick answer
GitHub Packages documents included monthly transfer as Free: 1 GB; Pro/Team: 10 GB; Enterprise Cloud: 100 GB. Package transfer resets monthly and some GitHub Actions downloads are treated differently.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| 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 |
Why does this limit matter?
Public CI consumers can turn a modest package into a high-transfer artifact.
This value is scoped to Account plan; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Measure monthly package download bytes by owner and account for Actions exemptions.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Storage and transfer are independent billing dimensions.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related