Git extension for versioning large files
Switch branches/tags
Clone or download
bk2204 Merge pull request #3277 from bk2204/windows-relpath
Canonicalize paths properly on Windows
Latest commit 7b4c366 Sep 21, 2018
Failed to load latest commit information.
.circleci all: use Go Modules instead of Glide Aug 29, 2018
commands commands: canonicalize paths properly on Windows Sep 21, 2018
config config/config.go: expand core.hooksPath Aug 30, 2018
debian debian/prerm: add --system flag Sep 20, 2018
docker docker: add debian_9 image to default images list May 8, 2017
docs docs: add note about closing release milestone Sep 20, 2018
errors errors/types.go: add a new UnprocessableEntityError Jul 31, 2018
filepathfilter filepathfilter: test correct set of global wildcards Feb 28, 2018
fs fs/fs.go: strings.HasPrefix typo Jul 16, 2018
git git/gitattr/attr{,_test}.go: parse implicitly 'true' attributes Sep 16, 2018
lfs Merge branch 'master' into lfshttp Sep 11, 2018
lfsapi lfsapi: pass stderr through when filling credentials Sep 18, 2018
lfshttp Merge branch 'master' into lfshttp Sep 14, 2018
locking lfsapi: extract new lfshttp package Sep 11, 2018
rpm all: use Go Modules instead of Glide Aug 29, 2018
script Update packagecloud.rb Aug 29, 2018
subprocess git: run 'config' from dir based on *Configuration Oct 26, 2017
t t: add an environment variable to dump test output Sep 18, 2018
tasklog tasklog: note alignemnt issue in *PercentageTask Feb 27, 2018
tools tools: add function to perform shell quoting Sep 4, 2018
tq lfsapi: extract new lfshttp package Sep 11, 2018
vendor go.mod: update gitobj to the latest master Sep 11, 2018
.gitattributes Enable autocrlf Aug 23, 2015
.gitignore t: store test_count{,.lock} in t, not t/remote Jul 11, 2018
.mailmap Add myself to .mailmap Feb 24, 2017
.travis.yml all: use Go Modules instead of Glide Aug 29, 2018 release: v2.5.0 Jul 26, 2018 embed the open code of conduct since the link is bad now May 6, 2016 CONTRIBUTING: update required go version Sep 6, 2018 update other github/git-lfs references Nov 15, 2016 Update Jul 30, 2018
Makefile t: make testsuite run under git rebase -x Sep 17, 2018 add @bk2204 to core Aug 31, 2018 update other github/git-lfs references Nov 15, 2016
appveyor.yml Makefile: force callers to have goversioninfo in $PATH Aug 29, 2018
git-lfs.go commands/run.go: teach Run() to return an exit code Apr 12, 2018
go.mod go.mod: update gitobj to the latest master Sep 11, 2018
go.sum go.mod: update gitobj to the latest master Sep 11, 2018
versioninfo.json release: v2.5.0 Jul 26, 2018

Git Large File Storage

Linux macOS Windows
Linux build status macOS build status Windows build status

Git LFS is a command line extension and specification for managing large files with Git.

The client is written in Go, with pre-compiled binaries available for Mac, Windows, Linux, and FreeBSD. Check out the website for an overview of features.

Getting Started


You can install the Git LFS client in several different ways, depending on your setup and preferences.

  • Linux users. Debian and RPM packages are available from PackageCloud.
  • macOS users. Homebrew bottles are distributed, and can be installed via brew install git-lfs.
  • Windows users. Git LFS is included in the distribution of Git for Windows. Alternatively, you can install a recent version of Git LFS from the Chocolatey package manager.
  • Binary packages. In addition, binary packages are available for Linux, macOS, Windows, and FreeBSD.
  • Building from source. This repository can also be built from source using the latest version of Go, and the available instructions in our Wiki.


From binary

The binary packages include a script which will:

  • Install Git LFS binaries onto the system $PATH
  • Run git lfs install to perform required global configuration changes.
$ ./

From source

  • Place the git-lfs binary on your system’s executable $PATH or equivalent.
  • Git LFS requires global configuration changes once per-machine. This can be done by running:
$ git lfs install

Example Usage

To begin using Git LFS within a Git repository that is not already configured for Git LFS, you can indicate which files you would like Git LFS to manage. This can be done by running the following from within a Git repository:

$ git lfs track "*.psd"

(Where *.psd is the pattern of filenames that you wish to track. You can read more about this pattern syntax here).

After any invocation of git-lfs-track(1) or git-lfs-untrack(1), you must commit changes to your .gitattributes file. This can be done by running:

$ git add .gitattributes
$ git commit -m "track *.psd files using Git LFS"

You can now interact with your Git repository as usual, and Git LFS will take care of managing your large files. For example, changing a file named my.psd (tracked above via *.psd):

$ git add my.psd
$ git commit -m "add psd"

Tip: if you have large files already in your repository's history, git lfs track will not track them retroactively. To migrate existing large files in your history to use Git LFS, use git lfs migrate. For example:

$ git lfs migrate import --include="*.psd"

For more information, read git-lfs-migrate(1).

You can confirm that Git LFS is managing your PSD file:

$ git lfs ls-files
3c2f7aedfb * my.psd

Once you've made your commits, push your files to the Git remote:

$ git push origin master
Uploading LFS objects: 100% (1/1), 810 B, 1.2 KB/s
# ...
   67fcf6a..47b2002  master -> master

Note: Git LFS requires Git v1.8.5 or higher.


Git LFS maintains a list of currently known limitations, which you can find and edit here.

Need Help?

You can get help on specific commands directly:

$ git lfs help <subcommand>

The official documentation has command references and specifications for the tool.

You can always open an issue, and one of the Core Team members will respond to you. Please be sure to include:

  1. The output of git lfs env, which displays helpful information about your Git repository useful in debugging.
  2. Any failed commands re-run with GIT_TRACE=1 in the environment, which displays additional information pertaining to why a command crashed.


See for info on working on Git LFS and sending patches. Related projects are listed on the Implementations wiki page.

Core Team

These are the humans that form the Git LFS core team, which runs the project.

In alphabetical order:

@bk2204 @larsxschneider @PastelMobileSuit @ttaylorr


These are the humans that have in the past formed the Git LFS core team, or have otherwise contributed a significant amount to the project. Git LFS would not be possible without them.

In alphabetical order:

@andyneff @rubyist @sinbad @technoweenie