Conditions for large files
GitHub Enterprise will warn you when pushing files larger than 50 MB. You will not be allowed to push files larger than 100 MB.
In this article
Tip: If you regularly push large files to your GitHub Enterprise Server instance, consider introducing Git Large File Storage (Git LFS) as part of your workflow. Git LFS works well with the GitHub Flow and can be used with any large file, regardless of its type. For more information, see "Versioning large files."
50 MB push warning
When pushing to your GitHub Enterprise Server instance, you'll receive a warning or error message if you either add a new file or update an existing file that is larger than 50 MB.
The warning will tell you which files are too large:
> remote: warning: Large files detected. > remote: warning: File big_file is 55.00 MB; this is larger than GitHub's recommended maximum file size of 50 MB
The push with
big_file is received and saved into the repository on your GitHub Enterprise Server instance, but you should consider removing the file and the commit entirely.
100 MB push limit
If you push a file larger than 100 MB to your GitHub Enterprise Server instance, Git will reject the push and tell you which file is too large:
> remote: warning: Large files detected. > remote: error: File giant_file is 123.00 MB; this exceeds GitHub's file size limit of 100 MB
This push was rejected because of
giant_file. The commits will not be saved into the repository on GitHub Enterprise.
If you need to push files larger than 100 MB, your GitHub Enterprise site administrator can configure your instance to accept larger pushes. For more information, see "Setting Git push limits".