# DVC compared with GitLFS for storage and versioning only **URL:** \ **Category:** Questions\ **Created:** [October 5, 2019, 12:46am UTC](https://discuss.dvc.org/t/dvc-compared-with-gitlfs-for-storage-and-versioning-only/241 "2019-10-05T00:46:30Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![shcheklein](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.dvc.org/shcheklein/32/173_2.png) [@shcheklein](https://discuss.dvc.org/u/shcheklein)\ **Post date:** [October 5, 2019, 12:49am UTC](https://discuss.dvc.org/t/dvc-compared-with-gitlfs-for-storage-and-versioning-only/241/2 "2019-10-05T00:49:18Z")
Thanks @nickrsan! More context here [https://discordapp.com/channels/485586884165107732/563406153334128681/629825409097138186](https://discordapp.com/channels/485586884165107732/563406153334128681/629825409097138186) The obvious one - Github still has 2GB limit of the file size with Git LFS - [https://help.github.com/en/articles/about-git-large-file-storage](https://help.github.com/en/articles/about-git-large-file-storage) Second, yes - caching and better/explicit data management, like pull/push data partially Third, advanced data management - utilize reflinks, hardlinks, etc to do checkout in a very fast manner, push/pull are using parallelism to save/download data (Iā€™m not sure about LFS), ability to use a shared cache to save space if multiple projects use the same data and/or multiple people use the same machine Fourth, features like `dvc import` / `dvc get` and `dvc.api` python interface - a really great way to reuse data or model files. Use cases like data registry for example via a Github repo with all the history, etc Or with `dvc get` and `dvc.api` - model deployment And those differences are only about data management šŸ™‚ no touching pipelines, mertics part (which I actually also consider a part of the data management layer). --- _[View the full topic](https://discuss.dvc.org/t/dvc-compared-with-gitlfs-for-storage-and-versioning-only/241)._