🔗 files.link
Get started

Bitbucket & GitHub LFS Alternative

Git LFS Alternatives: Store Large Repo Binaries Without Bandwidth Quotas

Store large files for Git repositories with simple integration and global CDN delivery.

Get started

Git LFS was meant to stop multi-gigabyte binaries from bloating your .git history, but it traded that problem for a billing one. GitHub bundles 10 GB of LFS storage and 10 GB of monthly bandwidth, then sells data packs once a designer checks in a few large PSDs. GitLab counts LFS against a shared namespace storage quota, and Bitbucket LFS ships 1 GB on the Free plan and 5 GB on Standard, then sells extra space in $10-per-100 GB packs.

The pain is rarely storage itself — it's the bandwidth meter, because every clone and every CI runner that pulls LFS objects burns quota, and a busy pipeline can exhaust a month's allowance in days. files.link takes a different shape: instead of speaking the LFS protocol, you push binaries to a REST API once, get a permanent CDN URL back, and reference that URL from a small manifest committed to the repo.

Clones stay tiny because the blobs never enter Git at all, and pulling an asset is an ordinary CDN download with no per-repo bandwidth cap behind it. To be explicit: files.link does not implement git lfs push/git lfs pull, so this is a deliberate migration off LFS, not a transparent backend swap. The migration is mechanical: git lfs ls-files to enumerate tracked blobs, git lfs pull to materialize them, upload each with the three-call flow (POST /v1/files/{folderId} → PUT presigned URL → POST /v1/files/confirm-upload), then record the returned URL in an assets.json manifest.

Untrack the paths (git lfs untrack '*.bin', drop the .gitattributes lines) and add a make fetch-assets step that reads the manifest and curls each file into place. Versioning becomes a one-line JSON diff instead of a giant blob in history, and because every upload keeps its own permanent URL, old commits still resolve the exact asset they shipped with. Game studios, ML teams shipping model weights, and anyone tired of "LFS bandwidth this month is over the quota" emails get predictable prepaid pricing with no per-repo limits and no bandwidth packs to buy.

For the wider landscape — DVC, git-annex, and direct S3 — see Git LFS alternatives.

Benefits With No Complexity

Global CDN delivery

Your files are served from 450+ edge locations worldwide.

Edge-cached worldwide

Files are cached close to your users for fast delivery.

Signed-URL security

Private files stay protected with time-limited access.

What You Get

Unlimited files

Upload as many files as you need.

Unlimited storage

There is no storage limit.

Public + Private storage

Private files are fully secured.

CDN ready links

Upload directly to 450+ edge locations worldwide.

Prepaid credits

No subscription. Pay only for the storage and bandwidth you use.

More coming soon

We have plenty of features coming!

How files.link Works

1. Upload

Create a project and upload your first file.

2. Copy

Copy the CDN link.

3. Use Anywhere

Paste and enjoy the blazing speed.

Why Developers Choose files.link

A Better Way to Store & Deliver Files

GitHub Git LFSGitLab LFSBitbucket LFSfiles.link
Git LFS protocol (push/pull)
Per-repo storage caps
Monthly bandwidth quota on pulls
Global CDN delivery included
Permanent URL per asset version
Plain REST API (curl-friendly)
Tiny clones (blobs never in Git)
Prepaid pricing, no data packs

Calculate Your Needs

Storage

0GB

Egress

0GB

CDN Bandwidth

0GB
Total: $0.000/month

Start Using Git LFS Alternative

  • Global CDN delivery
  • Edge-cached worldwide
  • Signed-URL security
  • Unlimited files
  • Unlimited storage
  • Public + Private storage
  • No subscription — prepaid credits keep spend predictable
Start Using Git LFS Alternative

Frequently Asked Questions

Does files.link work with git lfs push and pull?
No — it does not implement the Git LFS protocol. You upload binaries through the REST API, store the returned CDN URL in a manifest in your repo, and a fetch script pulls them on checkout. This is an intentional move off LFS, not a drop-in backend.
How is this cheaper than Git LFS?
LFS bills storage per-namespace and meters bandwidth on every clone and CI pull, so data packs stack up fast. files.link uses prepaid credits with no per-repo cap and no bandwidth quota — CDN delivery is included — so you pay only for what you actually store and transfer.
Does Git LFS cost money, or is it free?
The Git LFS client is free and open source, but the hosted storage and bandwidth behind it usually aren't. GitHub includes 10 GB of storage and 10 GB of monthly bandwidth, then charges for data packs; GitLab counts LFS against your namespace storage quota; Bitbucket LFS gives 1 GB on Free and 5 GB on Standard, with more sold in $10-per-100 GB packs. files.link replaces that model with prepaid credits and no separate bandwidth quota — you pay only for what you store and transfer, and CDN delivery is included.
How do I version large files without LFS?
Keep an assets.json mapping logical names to permanent URLs. Each new version is a new upload with its own URL, so bumping a version is a one-line JSON diff. Old URLs keep working, so previous commits still resolve their assets.
What's the migration path from Git LFS?
Run git lfs ls-files and git lfs pull to materialize tracked blobs, upload each via the REST API, record the URLs in a manifest, then git lfs untrack the paths and remove the .gitattributes entries. Add a make fetch-assets step and your repo no longer needs an LFS client or bandwidth quota.
General Questions
Is there a subscription?
No. files.link uses prepaid credits, so storage, bandwidth, and API usage are deducted from your balance as you go. The app explains the payment step before uploads are enabled — no monthly subscription and no per-user fees.
What is files.link?
files.link is a developer-first file platform that makes it simple to store, secure, and deliver files globally. It provides signed URLs, public/private access, and an API-first design so you can integrate file delivery into any app without the usual complexity.
How does billing work?
files.link uses prepaid credits. As you use storage, bandwidth, and API requests, credits are deducted daily. When your balance runs low, we automatically recharge it using your saved card. If an auto-recharge doesn't go through, your files and links stay put — you simply update your payment method or top up manually to keep going. No monthly subscriptions — just simple usage-based pricing.
How secure is my data?
All files are encrypted at rest and in transit. You can use signed URLs for private files, control access with permissions, and rely on enterprise-grade infrastructure for data protection.

Related

CI CD artifact storageZIP hostingGame asset hostingCold storage archiveNo egress fees storageFile upload curlS3 alternativeKubernetes backup storage
files.link
Copyright © 2026
All rights reserved
ContactGuidesGlossaryStatusLegal