Git extension for versioning large files
Go Shell Other
Latest commit 18c02f5 Feb 24, 2017 @sschuberth sschuberth committed on GitHub Merge pull request #1982 from git-lfs/sschuberth-mailmap
Add myself to .mailmap
Failed to load latest commit information.
commands line up 'locks' output columns Feb 23, 2017
config drop lfs.batch support, its always true now Feb 13, 2017
debian unused. Nov 22, 2016
docker run against gitlfs packages from docker hub Aug 2, 2016
docs docs/man: fix spelling error Feb 22, 2017
errors Early return instead of nesting (code style) Jan 9, 2017
filepathfilter filepathfilter: remove `*bench` subpackage Dec 27, 2016
git Merge branch 'master' into track-patterns Feb 13, 2017
lfs merge master Feb 17, 2017
lfsapi lfsapi: update test to new strings.QuoteFields semantics Feb 21, 2017
localstorage fix problems running 'install' in a root dir Nov 30, 2016
locking locking/client: reutrn a 'NotImplementedError' for HTTP 501s Feb 16, 2017
progress progress: remove 'var _' decls Feb 18, 2017
rpm rpm: build Git LFS in the right directory Nov 17, 2016
script Revert "bootstrap/cibuild: Print the Go version for easier debugging" Feb 24, 2017
subprocess Fix for #1874 Jan 19, 2017
test commands: remove 'matched query' msg Feb 23, 2017
tools tools/str_test: use `` to make reading escaped-quotes easier Feb 21, 2017
tq tq/verify: log errors in tracerx Feb 22, 2017
vendor/ vendor: Update gojsonschema pkg with new IO loaders Feb 13, 2017
.gitattributes Enable autocrlf Aug 23, 2015
.gitignore Use goversioninfo instead of windres to embed Windows resources Dec 15, 2016
.mailmap Add myself to .mailmap Feb 24, 2017
.travis.yml all: build using Go 1.8 Feb 16, 2017 release: 1.5.0 Nov 17, 2016 embed the open code of conduct since the link is bad now May 6, 2016 config: bump version to '2.0-pre' so it's clear you're not on an offi… Feb 9, 2017 update other github/git-lfs references Nov 15, 2016 Add copyright date to license Nov 23, 2016
Makefile update other github/git-lfs references Nov 15, 2016 README: Fix the build status table header order Feb 11, 2017 update other github/git-lfs references Nov 15, 2016
appveyor.yml AppVeyor: Use system Go 1.8 Feb 24, 2017
circle.yml CircleCI: Use XCode 8.2 to make brew happy Feb 24, 2017
git-lfs.go Use goversioninfo instead of windres to embed Windows resources Dec 15, 2016
glide.lock vendor: Update gojsonschema pkg with new IO loaders Feb 13, 2017
glide.yaml vendor: Update gojsonschema pkg with new IO loaders Feb 13, 2017
versioninfo.json Use goversioninfo instead of windres to embed Windows resources Dec 15, 2016

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 Git LFS website for an overview of features.

Getting Started

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

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

Once installed, you need to setup the global Git hooks for Git LFS. This only needs to be done once per machine.

$ git lfs install

Now, it's time to add some large files to a repository. The first step is to specify file patterns to store with Git LFS. These file patterns are stored in .gitattributes.

$ mkdir large-repo
$ cd large-repo
$ git init

# Add all zip files through Git LFS
$ git lfs track "*.zip"

Now you're ready to push some commits:

$ git add .gitattributes
$ git add
$ git commit -m "add zip"

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

$ git lfs ls-files

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

$ git push origin master
LFS: 12.58 MB / 12.58 MB  100.00 %
Counting objects: 2, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 548 bytes | 0 bytes/s, done.
Total 5 (delta 1), reused 0 (delta 0)
   67fcf6a..47b2002  master -> master

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 ask questions in the Git LFS chat room, or file a new issue. Be sure to include details about the problem so we can troubleshoot it.

  1. Include the output of git lfs env, which shows how your Git environment is setup.
  2. Include GIT_TRACE=1 in any bad Git commands to enable debug messages.
  3. If the output includes a message like Errors logged to /path/to/.git/lfs/objects/logs/*.log, throw the contents in the issue, or as a link to a Gist or paste site.


See for info on working on Git LFS and sending patches. Related projects are listed on the Implementations wiki page. You can also join the project's chat room.

Using LFS from other Go code

At the moment git-lfs is only focussed on the stability of its command line interface, and the server APIs. The contents of the source packages is subject to change. We therefore currently discourage other Go code from depending on the git-lfs packages directly; an API to be used by external Go code may be provided in future.

Core Team

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

In alphabetical order:

@andyneff @rubyist @sinbad @technoweenie @ttaylorr