You should use Git LFS if you have large files or binary files to store in Git repositories. ... And if you do, it will be difficult to version and merge the binaries. So, every time the files grow, the Git repository grows. And when Git users need to retrieve and clone a repository, this creates problems.

Is git LFS necessary?

So, when you have large files in your repository and/or a lot of binaries, then it is advisable to use Git LFS. ... This means that your local repository will be limited in size, but the remote repository of course will contain all the actual files and differences.

Is git LFS bad?

Something missing from the list of problems: Git LFS is a http(s) protocol so is problematic at best when you are using Git over ssh[1]. ... git supports large files, it just can't track changes in binary files efficiently and if they're large you check in a new blob every modification.