Maintenance

Manage Git LFS for Large Binary Assets

Track large binary files efficiently while planning storage, access, and migration behavior.

Git is optimized for text and source history. Large binary files such as design assets, media, and model files can make repositories slow and expensive when every version is stored directly.

Decide what belongs in Git

Keep source code and small, versioned assets in normal Git history. Consider Git LFS or an artifact store for large files that must be associated with source revisions. Frequently changing build outputs usually belong in a build or package system, not the repository.

Understand LFS pointers

Git LFS stores pointer files in Git while the binary content lives in LFS storage. Contributors and CI runners need access to that storage. A clone may succeed while LFS objects remain unavailable, so test the full checkout process.

Plan quotas and migration

Review storage and bandwidth limits, retention, backups, and access controls. Migrating existing binaries into LFS rewrites repository history and requires coordination with all contributors.

Checklist

  • Classify large files by purpose and change frequency.
  • Configure tracking patterns deliberately.
  • Verify LFS access in CI and deployment.
  • Monitor storage and bandwidth usage.
  • Coordinate history migration carefully.
Share this page Help other developers discover this resource.