Git Large File Storage
git-lfs.com
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
What Git Large File Storage is
Git Large File Storage (Git LFS) is an open-source Git extension that keeps large file contents on a remote server and places text pointers in their stead inside Git. It is intended for files such as audio samples, videos, datasets, and graphics, and the project says it can version files as large as a couple of gigabytes. Keeping file contents external helps keep repositories manageable, while downloading less data can make cloning and fetching faster. The project says Git LFS fits into the usual Git workflow without separate storage systems or extra toolsets. When paired with a remote host such as GitHub, large files use the repository’s existing access controls and permissions. Listed integrations include GitHub, GitHub Enterprise, GitLab, Azure DevOps, Bitbucket Cloud, and Bitbucket Server. Client binaries are listed for macOS, Windows, Linux, and FreeBSD; the project also provides a reference server implementation. The client is free. One migration caveat: tracking rules do not convert files already in history, and rewriting history changes Git object IDs.
Who it suits
Git LFS suits people working with Git repositories that contain large assets, such as graphics, datasets, audio, or video. It may be useful when keeping repository size manageable and using a familiar Git workflow are priorities.
Good to know, and what to watch
- Keeps large file contents outside the Git repository.
- Supports files as large as a couple of gigabytes.
- Can reduce data downloaded during cloning and fetching.
- Uses repository permissions with remote hosts such as GitHub.
- Client binaries are listed for four operating systems.
- Tracking rules do not convert files already in history.
- History migration changes Git object IDs.
- File contents require a remote server.
Plans
Every plan and priceGit LFS client
Free plan
The verdict
Git LFS offers a free way to manage large files alongside Git while keeping their contents on a remote server. Account for the migration caveat before applying tracking to files already in repository history.
What the maker publishes
- Access controls
- When used with a remote host such as GitHub, large files use the same access controls and permissions as the rest of the Git repository. source
- File size
- The site says Git LFS can version files as large as a couple of gigabytes. source
- File types
- The site names audio samples, videos, datasets, and graphics as examples of files managed by Git LFS. source
- Hosting
- Git LFS stores file contents on a remote server such as GitHub.com or GitHub Enterprise; the project also provides a reference server implementation. source
- Installation
- The project README lists precompiled client binaries for macOS, Windows, Linux, and FreeBSD. source
- Integrations
- The project wiki lists Git LFS support for GitHub, GitHub Enterprise, GitLab, Azure DevOps, Bitbucket Cloud, and Bitbucket Server. source
- Migration limit
- Selecting file types with git lfs track does not retroactively convert existing files; migrating history rewrites it and changes Git object IDs. source
- Performance
- Git LFS downloads less data for repositories that deal with large files, enabling faster cloning and fetching. source
- Purpose
- Git LFS replaces large files in Git with text pointers and stores their contents on a remote server. source
- Repository size
- External file storage helps keep Git repositories at a manageable size. source
- Security
- The project says releases are signed with an OpenPGP key of a core team member and provides signed hashes for verification. source
- Security reporting
- The security policy directs client vulnerability reports to core team members by email and API service vulnerability reports to the relevant hosting company. source
- Support
- The README points users to official documentation, a FAQ, GitHub discussions, and issues, where a core team member will respond to opened issues. source
- Workflow
- The site says users can keep their usual Git workflow without additional commands, secondary storage systems, or toolsets. source
Checked against the maker's pages on 30 Sept 2026.