Fix · GitHub and Git

Push blocked: file larger than 100 MB

Blocks your work

What you may see

The push fails and mentions a large file or the size limit
I uploaded a huge video or file and now every push fails
I added a video, a zip or a database export by mistake

Most likely cause

One saved version (commit) contains a file over the limit, and deleting the file now does not remove it from the earlier commit.

Check first (about two minutes)

Read the error: it names the file and the size.
Run git log --oneline origin/main..HEAD to see how many unpushed commits there are.

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a patient senior engineer who knows Git and GitHub very well and explains them to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

THE PROBLEM
Push blocked: file larger than 100 MB

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
One saved version (commit) contains a file over the limit, and deleting the file now does not remove it from the earlier commit.

DO THESE STEPS, IN THIS ORDER
1. Find the file named in the error and tell me what it is and whether the project needs it.
2. Make a safety copy: git branch backup-before-cleanup.
3. If the big file is only in the last commit(s) that were not pushed: remove it from tracking (git rm --cached <file>), add it to .gitignore, and rewrite those local commits (git reset --soft or git commit --amend), after showing me the exact plan.
4. If the file is deep in older history, explain the options (git filter-repo, or Git LFS for files that must stay) and ask me before rewriting history.
5. Suggest a better home for the big file (a storage service or a video host) and how to link to it.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- git push succeeds and the repository is not much bigger (check the size on the GitHub page).
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not delete the original big file from my computer.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Find the file named in the error and tell me what it is and whether the project needs it.
Make a safety copy: git branch backup-before-cleanup.
If the big file is only in the last commit(s) that were not pushed: remove it from tracking (git rm --cached <file>), add it to .gitignore, and rewrite those local commits (git reset --soft or git commit --amend), after showing me the exact plan.
If the file is deep in older history, explain the options (git filter-repo, or Git LFS for files that must stay) and ask me before rewriting history.
Suggest a better home for the big file (a storage service or a video host) and how to link to it.

Do not do this

Do not force push over a shared branch without asking the team.
Do not just delete the file and commit again: the old commit still carries it.
Do not delete the original big file from my computer.

Try another entry