Git LFS storage you own.
Host your own Git LFS server. Store large files on your infrastructure, with your rules, at your cost.
$ git lfs push origin main
Uploading LFS objects: 100% (3/3), 1.4 GB
To https://your.lfs-bucket.com
Trusted by 500+ developers
Why developers choose LFS Harbor
No subscription
Pay once, use forever. No monthly bill, no usage tiers, no surprise charges.
Your data, your infrastructure
Files transfer directly from your git client to your own bucket — they never touch our servers.
Pay only for what you use
Storage on Cloudflare R2 costs $0.015/GB month vs GitHub $0.07/GB month.
Multi-repo support
One bucket, any number of repositories. Each repo gets its own credentials.
Savings calculator
A website repo with 2 GB of video and image assets — well under both free tiers. CI builds preview branches ~80 times a month and pulls ~1 GB each time.
GitHub LFS (Free plan)
Pay-as-you-go overage
$6.13 / mo
LFS Harbor + Cloudflare R2
+ $30.00 one-time
$0.00 / mo
Break-even
5 months
3-year savings
$190.50
Up and running in 10 minutes — follow our setup guide
Pricing
Solo
- 1 user
- Multiple repositories in one bucket
- Additional repos available as separate purchases
- Access token for hosted LFS server
- Bring your own bucket (GCS, S3, or S3-compatible)
- 30-day money-back guarantee
Team
Coming soon- Up to 5 users
- Read-only access tokens
- Support for locking API
- Multiple repositories in one bucket
- Additional repos available as separate purchases
- Access token for hosted LFS server
- Bring your own bucket (GCS, S3, or S3-compatible)
- 30-day money-back guarantee
Enterprise
- Unlimited users
- Read-only access tokens
- Support for locking API
- Unlimited repositories
- Fine-grained access control
- SSO
- Dedicated support
What developers say
Alex Rivera
Indie game developer
Finally, no more bloated repos
I was dreading every git clone on my game project — 4GB of textures and audio that had to download in full before I could do anything. LFS Harbor took 15 minutes to set up and now clones are instant. My GCS bill last month was $0.80.
Priya Nair
iOS developer
One-time price sealed the deal
I was already using Git LFS through GitHub but the data pack pricing was getting out of hand for storing ML models and compiled frameworks. Switched to LFS Harbor, pointed it at my existing S3 bucket, and haven't thought about it since.
Tom Callahan
Freelance web developer
My clients' repos are so much cleaner
Every client project ends up with a pile of raw video and uncompressed images that nobody wants to delete. LFS Harbor keeps those out of the repo history without any extra workflow for my clients. Setup guide was genuinely straightforward.
What is Git LFS?
Git wasn't designed for large binary files. Every time you clone a repository, Git pulls the full history of every file — including every version of every large asset you've ever committed. On a big project, that can mean gigabytes of data just to get started.
Git LFS (Large File Storage) solves this by replacing large files with lightweight pointers in your repository. The actual file content lives separately and is only downloaded when you need it — keeping clones fast and your repo lean.
👾 Game developer
Game repos balloon fast. Textures, audio files, and 3D models change constantly — without Git LFS, every clone pulls gigabytes of asset history.
Textures, audio clips, 3D models, level assets
📱 Native & app developer
Binaries don't diff — Git stores every version in full. ML models, compiled SDKs, and large test fixtures quietly bloat your repo over time.
ML models, compiled binaries, SDKs, large test fixtures
💻 Web developer
Raw images and video updated regularly are some of the worst offenders. A few rounds of uncompressed assets can make a simple site repo painful to clone.
High-res images, raw video, design exports