Managing Git LFS objects in archives of your repository

You can choose whether Git Large File Storage (Git LFS) objects are included in source code archives, such as ZIP files and tarballs, GitHub Enterprise Cloud creates for your repository.

People with admin permissions for a repository can manage whether Git LFS objects are included in archives of the repository.

About Git LFS objects in archives

GitHub Enterprise Cloud creates source code archives of your repository in the form of ZIP files and tarballs. People can download these archives on the main page of your repository or as release assets. By default, Git LFS objects are not included in these archives, only the pointer files to these objects. To improve the usability of archives for your repository, you can choose to include the Git LFS objects instead.

If you choose to include Git LFS objects in archives of your repository, every download of those archives will count towards bandwidth usage for your account. Each account receives 1 GB per month of bandwidth for free, and you can pay for additional usage. For more information, see "About storage and bandwidth usage" and "Managing billing for Git Large File Storage."

If you use an external LFS server (configured in your .lfsconfig), those LFS files will not be included in archives of the repository. The archive will only contain files that have been committed to GitHub Enterprise Cloud.

Managing Git LFS objects in archives

  1. On, navigate to the main page of the repository.
  2. Under your repository name, click Settings. Repository settings button
  3. Under "Archives", select or deselect Include Git LFS objects in archives. Checkbox to include Git LFS objects in archives

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.