How to increase GIT LFS

[MonirNiazi]

Select Topic Area

Question

Body

Hello,

I need QUICK help, so I really hope someone can help me fast!
I have a git project, and it says the that the LFS bandwith is 10 GB, which is the MAX for a free account.

I did not have set my payment details before, but I just added my payment details.

How can I increase the max LFS for this project.

PLEASE HELP!

[gnix0]

In you profile configurations, under Billing and licensing -> Budgets and alerts, go to the Git LFS budget you'll have and click the three dots, then edit. Since you have added your payment details, now you should be able to set a budget amount greater than the default of 0, which is what defines the limits you are facing now. I believe by setting this number to some higher amount will lead you to be able to continue using the service provided, only now you will be charged for the extra usage amount within the range of the budget you set for a monthly basis.

[Stephlovesone]

Good 👍

[currentsuspect]

Hey 👋 I ran into the same thing recently, here’s what works:

Adding payment info doesn’t auto-increase the quota.
You still need to buy extra Git LFS data packs.

How to upgrade:

Go to Settings → Billing → Plans and usage → Git LFS

Click Manage Budgets → Add storage or bandwidth pack

Each pack gives 50 GB storage + 50 GB bandwidth for $5 USD/month.

Applies immediately — as soon as you add the pack, pushes and pulls will resume; no need to wait for the monthly reset.

Optional tip:
If you just need to unblock yourself temporarily, you can:

Push assets to a separate repo or release storage outside LFS (for example GitHub Releases).

Wait for the monthly reset (shown on the usage page).

[MonirNiazi]

Hello, I have a personal account.
Can you please tell me exactly where to buy this "add storage or bandwidth pack"?
When I go to Settings - Billing - (I only see Usage), and I cannot find "Git LFS".

And in overview I see the screenshot I uploaded in first message.

[currentsuspect]

Check here hope the docs help:

https://docs.github.com/en/billing/concepts/product-billing/git-lfs

[Stephlovesone]

I also learnt from some of the responses

[tarnos12]

Hey, can someone explain to me where I can find which repository is using 10GB(total) of LFS storage?(not bandwidth)
I'd like to clear it or increase the limit but I am honestly confused about it, the UI for it is terrible and I can't find anything that would explain where those 10GB went to.

[orelvis15]

I've run into this as well. Git LFS is a good solution for storing a handful of large files, but once an AI project starts accumulating hundreds of checkpoints or multiple dataset revisions, it becomes harder to treat Git as both a source control system and an artifact repository.

One approach that has worked well for us is keeping Git focused on source code while moving large immutable artifacts (models, checkpoints, datasets, embeddings, etc.) into a dedicated artifact layer. That keeps repositories much smaller, reduces unnecessary transfers, and makes versioning easier to manage as experiments grow.

We're currently building CAVS Node around this idea. It uses content-addressable storage and deduplication so identical content doesn't need to be stored repeatedly across artifact versions. It's not intended to replace Git or Git LFS for code—it complements them by handling the artifact side of AI workflows.

Curious if anyone else here has reached the point where Git LFS started becoming more of an artifact management problem than a source control problem.