Why large files can be a problem
Git stores repository objects in its history. Large binary files can make clones and history operations expensive, especially when files change frequently.
Git LFS stores pointers in Git
Git Large File Storage replaces selected large files in normal Git history with small pointer files while the actual content is stored through an LFS server. The workflow still feels like Git to the developer.
Choose files carefully
Large media, design assets and frequently changing binary artifacts may be good candidates. LFS requires hosting and team support, so confirm that the remote platform and deployment environment support it.
ADVERTISEMENT