GitHub LFS Storage Quota Exceeded

GitHub's Git LFS gives 10 GiB of free storage and 10 GiB/month bandwidth on Free and Pro (250 GiB each on Team and Enterprise Cloud) — past that, usage is metered per GB rather than sold in the old $5 data packs, which GitHub retired. A self-hosted LFS server has no separate quota at all.

What the free tier actually includes

PlanStorageBandwidth/month
Free / Pro10 GiB10 GiB
Team / Enterprise Cloud250 GiB250 GiB

Past the included quota, GitHub bills metered usage per GB for storage and bandwidth — unless the account's LFS budget is set to $0, in which case LFS access is blocked for the rest of the billing cycle instead of generating a bill.

What hits the quota fast

Binary assets checked into LFS — design files, trained model weights, datasets, game assets — can still burn through even a 10-250 GiB quota quickly at scale. A team repeatedly cloning or CI repeatedly checking out a repo with large LFS objects is the most common way bandwidth gets exhausted mid-cycle.

Fix it now

  1. Check current usage: Settings > Billing > Git LFS data.
  2. Set or raise the account's LFS budget if staying on GitHub and metered billing is acceptable.
  3. Prune LFS objects no longer referenced by any branch: git lfs prune.

Self-hosted: no quota, no per-GB billing

Gitea's built-in LFS support — the engine Rithub runs on — stores LFS objects on your own server's disk. Storage is whatever the server has, not a billed quota, and there's no separate bandwidth meter for pulls. See private git hosting, free for the rest of what that includes.

Sign up freeImport from GitHub