Git Large File Storage (LFS) is a plugin that manages large binary files outside the Git repository, tracking only pointers to these files to improve performance. While recommended for managing large files, Git LFS presents challenges such as installation complexity, limited visibility, additional maintenance steps, and command-line reliance, making it less suitable for non-coders and artists. Alternatives to Git LFS include tools like git-annex and git-bigfiles, which also face integration and usability issues.

1. What is Git LFS (Large File Storage)? An Overview
Git Large File Storage (LFS) Overview
Large binary files can be effectively managed with the help of the open-source LFS Git plugin.
Git cannot track changes to binary files like text files, causing slowing of Git operations like
clone, fetch, or pull. LFS stores large binary files outside of the Git repository, leaving only a
small text-based pointer for Git to manage.
● When adding a file to Git LFS, GitLab adds the file to the project’s configured object
storage.
● The pointer contains information about the file, including version, hashing method, and
size.
● Project statistics, such as storage capacity and LFS object storage, are recalculated via a
work queue.
Should I Use Git LFS?
Git LFS is recommended for managing large or binary files in Git due to its decentralized nature.
Developers have full change history on their computers, which can cause Git repositories to
grow by file size, slowing down retrieval and cloning. Git LFS was created to address these
issues, but it has its own set of problems.For designers and artists that need to version big binary
art files, it might not be appropriate
Problems with Git LFS
● Time-Consuming: Installing Git LFS on every user's server and workstation is time-
consuming and burdensome.
● Lack of Visibility and Control: Once installed, there's little control over the system.
● Extra Steps: Maintaining Git LFS requires extra steps for every Git repo, making it
challenging for non-Git users.

2. ● Not Designed for Artists: It doesn't integrate with popular art and design programs, and
non-coders still face performance penalties.
● Command Line-Driven: Users must learn commands to access or commit assets, which
can be challenging for artists.
● Difficulty Finding the Right Version: The tool's command-line-driven nature makes it
difficult for artists to iterate on specific assets.
Alternatives to Git Large File Storage: The following are open-source or third-party solutions for
managing large files in Git.
● Git-annex
● Git-bigfiles
● git-fat, git-media
● Git-bigstore
● git-sym
These tools are command line-driven, lack integration with art or design tools, require file
retrieval and sending, and finding recent file versions can be challenging.