GitHub Git LFS
- Free allowance
- 10 GiB storage AND 10 GiB/month bandwidth on GitHub Free (also 10/10 on Pro and Free-for-orgs; 250 GiB each on Team/Enterprise Cloud).
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- cardcard required, no phone
- Binding limit
- per-object-capPer-file: 2 GB
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 10 GiB storage AND 10 GiB/month bandwidth on GitHub Free (also 10/10 on Pro and Free-for-orgs; 250 GiB each on Team/Enterprise Cloud). This is UP from the old 1 GiB/1 GiB — the docs now show a 10 GiB table. Pre-paid data packs are gone; it is metered with a budget setting. unit GiB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
Per-file: 2 GB on Free/Pro, 4 GB on Team, 5 GB on Enterprise Cloud. Storage is billed on all LFS objects ever associated with a repo, hourly-averaged, and 'If you delete Git LFS objects partway through a calendar month, the storage usage for that month is not recalculated'. Re-pushing a 1-byte change to a 500 MB file consumes another 500 MB. Actions pulling LFS counts against the repo owner's bandwidth. |
| Binding | per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota |
| Identity | card not published |
| Egress | Metered but included up to 10 GiB/month. Over quota with no payment method, 'Git LFS support is disabled on your account until the next month'. With a $0 budget, usage is blocked for the rest of the calendar month. No free CDN in front of LFS. free allowance: 10 GiB per month |
| Per-object cap | Per-file: 2 GB (2000000000 bytes) |
| Retention | not stated |
| Interface | rest, git part of the text of Limits, above |
| Tooling | git-lfs (git-lfs/git-lfs, ~10k stars). git-annex can also use GitHub LFS as a special-remote backend (see the git-lfs remote entry). REST API for repo management. |
| Composes with | 10 GiB per account x unlimited free accounts. Note the ownership trick in GitHub's own docs: 'Anyone with write access to a repository can push files to Git LFS without increasing their personal bandwidth and storage use' — usage lands on the REPO OWNER. So a collaborator-heavy layout concentrates the bill on one account, which is the opposite of what you want; the shardable axis is accounts-as-repo-owners. |
| Reliability | Hard-blocked (not billed) without a payment method, so it degrades safely. The monthly non-recalculation on delete means a big upload you remove still burns the month. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | docs.github.com/en/billing/concepts/product-billing/git-lfs | table: 'GitHub Free | 10 GiB | 10 GiB' (bandwidth | storage) |
| 2026-10-21 | docs.github.com/en/repositories/working-with-files/managing- | 'GitHub Free | 2 GB' maximum file size |
| 2026-10-21 | github.com/git-lfs/git-lfs.git/info/lfs/objects/batch | probe: POST (download, bogus oid) -> HTTP 200 (LFS endpoint live, anonymous batch accepted) |
Unknown values 4
$.identity_cost.detailboilerplate$.per_object_cap.notesthe field may be stated in a source that was not read$.retention.notesthe field may be stated in a source that was not read$.retention.statedthe field may be stated in a source that was not read