Quick answer
GitHub documents regular git file size as 50 MiB warning; 100 MiB hard block; 25 MiB browser upload. Files beyond the hard block require Git LFS or an external release/storage path.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| regular Git file sizeFiles beyond the hard block require Git LFS or an external release/storage path. | 50 MiB warning; 100 MiB hard block; 25 MiB browser upload | Regular repositories | GitHubAug 22, 2026 |
Why does this limit matter?
A file can push successfully after the warning yet still degrade repository performance.
This value is scoped to Regular repositories; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Inspect staged object sizes before push and choose Git LFS for appropriate binary assets.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Git LFS has separate per-file, storage, and bandwidth limits.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related