The future of large files in Git is Git
created: Aug. 15, 2025, 8:07 p.m. | updated: Aug. 16, 2025, 12:41 p.m.
Large files bloat Git’s storage, slow down git clone , and wreak havoc on Git forges.
What you can do today: replace Git LFS with Git partial cloneGit LFS works by storing large files outside your repo.
By default, if I git clone a repo with many revisions of a noisome 25 MB PNG file, then cloning is slow and the checkout is obnoxiously large:$ time git clone https://github.com/thcipriani/noise-over-git time git clone https://github.com/thcipriani/noise-over-git Cloning into '/tmp/noise-over-git' ... into... ...
But a partial clone side-steps these problems:$ git config --global alias.pclone 'clone --filter=blob:limit=100k' git configalias.pclone $ time git pclone https://github.com/thcipriani/noise-over-git time git pclone https://github.com/thcipriani/noise-over-git Cloning into '/tmp/noise-over-git' ... into... ...
So, commands like git diff , git blame , and git checkout will require a trip to your Git host to run.
16 hours, 37 minutes ago: Hacker News