Ctrl+Z Therapy
CasesQuick answersGuides10-minute checklistHow we testCartoonSend it in

GitHub rejects files over 100 MiB? What to do with big files

Ship ItChecked against the official source

Source checked 8 Oct 2026 · Published 23 Oct 2026 · Last reviewed 23 Oct 2026 · By Ctrl+Z Therapy (how we test)

The short answer

GitHub blocks files larger than 100 MiB (about 105 MB) and warns you from 50 MiB. A file added through the browser can be no larger than 25 MiB. The usual culprits are a database dump, a video or a folder of dependencies.

What to do

  1. Don't need the file in your project? Add it to .gitignore. If it's already checked in, you must untrack it first.
  2. Added it in an earlier commit? Deleting it now isn't enough: it has to be removed from the repository's history. Make a backup first, because GitHub warns that this permanently removes files.
  3. Really need big files versioned? Use Git Large File Storage (Git LFS).
  4. Ask your AI tool: "Find every file in this project over 50 MB and tell me if it should be in Git. After I make a backup, help me remove the big ones from the history."

Good to know

  • Database dumps don't belong in Git. GitHub's docs: "Git is not designed to handle large SQL files".

Source

Checked on 8 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.