Github url


by git-lfs

git-lfs /git-lfs

Git extension for versioning large files

8.4K Stars 1.6K Forks Last release: 3 months ago (v2.11.0) Other 7.7K Commits 83 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Git Large File Storage

CI status

Git LFS is a command line extension andspecification 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 websitefor 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 fromPackageCloud.
  • macOS users. Homebrew bottles are distributed, and can be installed via
    brew install git-lfs
  • Windows users. Git LFS is included in the distribution ofGit 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 ourWiki.


From binary

The binary packages include a script which will:

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

From source

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

Verifying releases

Releases are signed with the OpenPGP key of one of the core team members. To get these keys, you can run the following command, which will print them to standard output:

$ curl -L | tar -Ozxf -

Once you have the keys, you can download the


file and verify the file you want like so:

$ gpg -d sha256sums.asc | grep git-lfs-linux-amd64-v2.10.0.tar.gz | shasum -a 256 -c

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"



is the pattern of filenames that you wish to track. You can read more about this pattern syntaxhere).

Note: the quotation marks surrounding the pattern are important to prevent the glob pattern from being expanded by the shell.

After any invocation of




, you _must commit changes to your


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


(tracked above via



$ 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" --everything

For more information, read [



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 # ... To 67fcf6a..47b2002 master -\> master

Note: Git LFS requires at least Git 1.8.2 on Linux or 1.8.5 on macOS.


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
    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 | @chrisd8088 | @larsxschneider | |---|---|---| | | | |


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 | @PastelMobileSuit | @rubyist | @sinbad | @technoweenie | @ttaylorr | |---|---|---|---|---|---| | | | | | | |

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.