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

From MCP to multi-agents: The top 10 new open source AI projects on GitHub right now and why they matter
Get insights on the latest trends from GitHub experts while catching up on these exciting new projects.

Racing into 2025 with new GitHub Innovation Graph data
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through December 2024.

GitHub Availability Report: March 2025
In March, we experienced one incident that resulted in degraded performance across GitHub services.