Source-backed platform rule

GitHub repository push size limit

See the direct answer, scope, qualifiers, and current official evidence for GitHub repository push size limit.

RuleRoster is independent and is not affiliated with or endorsed by GitHub.

Direct answer

What is the rule?

GitHub enforces a maximum push size of 2 GB per push.

Scope: GitHub.com repository activity
Rule verified: September 23, 2026
Source checked: November 4, 2026

Published evidence

Rule details

Enforced limit

Enforced maximum: 2 GB per push. GitHub states that this ceiling is enforced. Specific enforcement action: not stated.

Applicability

Service: GitHub.com. Plans: Enterprise Cloud, Free, Pro, Team. Country: not stated. Device: not stated. Account class: not stated. Policy version: not stated.

Worked check

Why a small push can still contain a rejected file

Which GitHub size limit applies?
Measurement basis	Rule reference
Each file uploaded through the browser	Browser upload size
Each Git object	Single-object size
The complete Git push	This record
The repository on disk	Repository on-disk size

Use the matching record’s scope, units, and verification dates. Passing one size check does not establish that another is satisfied.

A proposed commit contains one 120 MiB binary file. Even though that file is smaller than the 2 GB total push ceiling, it exceeds the separate object and file ceilings. Checking the total push size alone misses the reason GitHub can reject it.

Performance recommendation: The repository guide recommends a maximum single object size of 1 MB. This recommendation is separate from an enforced ceiling.
Large-file warning: The file guide describes a warning above 50 MiB. A 60 MiB file crosses that warning threshold; the warning is not the 100 MiB rejection threshold.
Enforced object and file limits: The repository guide states 100 MB per object; the file guide blocks files larger than 100 MiB. Preserve each source’s units when checking a borderline value. The 120 MiB example exceeds both ceilings.
Enforced total push limit: The 2 GB push limit is an additional check. Passing one size check does not establish that a push will be accepted.

Find the object, then choose a remedy

Identify the large file and the commit you plan to push. This read-only command lists blob sizes in bytes for the latest commit; it does not inspect uncommitted files or prove the total push size.
For a binary that belongs in version control, evaluate Git LFS. For a distributed binary, evaluate GitHub Releases. Check their current limits and costs before choosing either route.
If the large file is already in earlier commits, deleting it from the working tree alone leaves that history. Review a separate history-repair plan with collaborators before rewriting it.

# Read-only: inspect blob sizes in the latest commit
git ls-tree -r --long HEAD

Worked guidance checked against GitHub documentation October 5, 2026. The rule’s verification and review dates are shown separately.

Evidence trail

Official sources

GitHub Docs repository limits
GitHub · verified September 23, 2026

Attribution and license

Source content: GitHub Docs by GitHub, licensed under CC BY 4.0: https://github.com/github/docs/blob/0a4d351cc1ff7134764f874808fb6829afbb73dd/LICENSE. Summarized and adapted by RuleRoster; verified 2026-09-23. No endorsement by GitHub is implied.

Interpretation and accountability

Before you act

Confirm that the scope matches your case.
Keep recommendations, enforced limits, exceptions, and unstated details distinct.
Open the official source before relying on the rule for a consequential decision.

Record dates

Published: September 23, 2026
Rule verified: September 23, 2026
Source checked: November 4, 2026
Review due: November 11, 2026

Challenge this record

If the source or summary appears wrong, submit precise evidence for human review.

Submit a correction