Announcing Git Large File Storage (LFS)
Distributed version control systems like Git have enabled new and powerful workflows, but they haven’t always been practical for versioning large files. We’re excited to announce Git Large File Storage…
Distributed version control systems like Git have enabled new and powerful workflows, but they haven’t always been practical for versioning large files. We’re excited to announce Git Large File Storage (LFS) as an improved way to integrate large binary files such as audio samples, datasets, graphics, and videos into your Git workflow.
Git LFS is a new, open source extension that replaces large files with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
Git LFS is easy to download and configure, works on all major platforms, and is open sourced under the MIT license.
Early access to Git LFS support on GitHub.com
We’re ready to roll out Git LFS support to a select group of users. If you’d like to be one of the first to try it out on GitHub.com, sign up for early access using your GitHub account.
In the future, every repository on GitHub.com will support Git LFS by default.
Pricing
Every user and organization on GitHub.com with Git LFS enabled will begin with 1 GB of free file storage and a monthly bandwidth quota of 1 GB. If your workflow requires higher quotas, you can easily purchase more storage and bandwidth for your account.
Want to start working with large files on GitHub.com? Sign up for early access.
Written by
Related posts
Bringing more transparency to GitHub’s status page
Changes to the status page will provide more specific data, so you’ll have better insight into the overall health of the platform.
Developer policy update: Intermediary liability, copyright, and transparency
We’re sharing recent policy updates that developers should know about, updating our Transparency Center with the full year of 2025 data, and looking to what’s ahead.
GitHub availability report: March 2026
In March, we experienced four incidents that resulted in degraded performance across GitHub services.
