Git LFS

Also Known As

TL;DR

Explanation

Git LFS stores large files (images, videos, audio, design files, compiled binaries, datasets) outside the git object store. In the repository: a 134-byte text pointer file. On the LFS server: the actual binary content. Benefits: fast clone (no large binaries by default), full history accessible, file locking for exclusive edits. Commands: git lfs install, git lfs track '*.psd', commit .gitattributes. Providers: GitHub (1GB free), GitLab, Bitbucket all support LFS. Past commits with large files are unchanged — LFS only affects future commits.

Common Misconception

Why It Matters

Common Mistakes

• Installing LFS after large files are already committed — past commits unchanged
• Not committing .gitattributes — LFS tracking rules lost for other contributors
• LFS without bandwidth budget planning — LFS downloads count against provider quotas
• Tracking too many file types — small icons are fine in regular git

Code Examples

# Large files in regular git:
git add design-mockups/hero-video.mp4  # 250MB
git add design-mockups/assets.psd       # 180MB
git commit -m 'Add design assets'
# Every clone now downloads 430MB for these files alone

# Git LFS setup:
git lfs install
git lfs track '*.mp4' '*.psd' '*.ai' '*.sketch'
git add .gitattributes
git add design-mockups/hero-video.mp4  # LFS pointer: 134 bytes
git commit -m 'Add design assets (via LFS)'
# Clone: fast — pointer files only
# git lfs pull: downloads actual binaries when needed

References

• ↗ https://git-lfs.com/

Tags

Related Terms