Home / GitHub
GitHub Releases
docs.github.com/en/repositories/releasing-projects-on-githubStatic file host (CDN backed)egress/github-releases-cdnJSONcomparereport an errorprovider JSON
- Free allowance
- No total size and no bandwidth limit; under 2 GiB per file; 1,000 assets per release
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- per-object-capunder 2 GiB per asset; 1,000 assets per release
- Evidence
- measured3 sources; a live request was made and its output kept
- Freshness
- stale on 2026-12-23checked 2026-10-23 (live); stale on 2026-12-23
| Free tier | no total size and no bandwidth limit; under 2 GiB per file; 1,000 assets per release unit unlimited; metered on downloaded-bytes |
|---|
| Price | none stated |
|---|
| Limits | - per-object-cap (binding) under 2 GiB per asset source
- per-object-cap (binding) 1,000 assets per release source
|
|---|
| Binding | per-object-cap 2 GiB per asset sets the shard size; the volume itself is not metered. |
|---|
| Identity | email a GitHub account |
|---|
| Egress | no bandwidth limit stated; ranged GETs served from release-assets.githubusercontent.com with a fresh signature per request |
|---|
| Per-object cap | under 2 GiB per asset (2147483648 bytes) |
|---|
| Retention | an asset lives until the release is deleted |
|---|
| Interface | rest, cli https://github.com/OWNER/REPO/releases/download/TAG/NAME, redirecting to a signed release-assets URL |
|---|
| Tooling | gh release, curl |
|---|
| Composes with | the bulk egress lane that needs no domain and no card: the 2 GiB per-asset cap sets the shard size and the volume is not metered, so it composes with a manifest and a ranged fetcher. |
|---|
| Reliability | the download URL redirects to a signed release-assets host; the signature is per request |
|---|
| Notes | A control download from proof.ovh.net on the same machine at the same time reached 29.5 MiB/s, so this is not the machine's ceiling. |
|---|
| Parsed numbers | |
|---|
Evidence 3
| date | source | what it proved |
|---|
| 2026-10-22 | docs.github.com/en/repositories/releasing-projects-on-github | 'Up to 1000 release assets may be associated with a single release. Each file included in a release must be under 2 GiB. There is no limit on the total size of a release, nor bandwidth usage' |
| 2026-10-22 | probe: https://release-assets.githubusercontent.com/github-production-release-asset/ | 206 with Content-Range bytes 0-1023/40227721 and Accept-Ranges: bytes on a freshly resolved URL |
| 2026-10-22 | probe: https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 | 1 connection: 40,227,721 bytes in 5.71 s = 6.72 MiB/s. 4 connections with a minted URL each: 40,227,721 bytes in 2.72 s = 14.11 MiB/s |
More fields 3
{
"stale_after_days": 180,
"bytes_transit": "yes",
"transit_note": "the asset is served from release-assets.githubusercontent.com"
}