Bitbucket Repository Over the Size Limit

How to fix it

Try these in order — the most common fix is first.

1. 1. Undo the last push

   Copy steps
   1. git branch <keeper>
   2. git reset --soft @{u}^ (or --hard if nothing to keep)
   3. git push --force
   4. git merge --ff-only <keeper>, then git branch -d <keeper>
   Did this fix it? Yes No

2. 2. Remove large files from history

   Copy steps
   1. Rewrite history with BFG or git filter-repo, or move files to Git LFS
   2. Force push, then ask collaborators to re-clone
   Did this fix it? Yes No

3. 3. Run garbage collection

   Copy steps
   1. Bitbucket runs GC after the undo and again if usage stays at 75% of the limit
   2. If still blocked, ask Atlassian Support to run GC; some users needed this even after cleanup
   Did this fix it? Yes No

4. 4. Prevent it

   Copy steps
   1. Keep 'Block pushes with files over 100 MB' enabled in Advanced settings
   2. Use .gitignore, Git LFS or an artifact registry
   Did this fix it? Yes No

Symptoms

remote: Repository is over the size limit (4 GB) and will not accept further additions. Warning appears at 2 GB.

Why it happens

• Large binaries committed to history
• Build artifacts or media in the repo
• Deleting files does not shrink git history

This guide also covers

• bitbucket repository size limit exceeded
• bitbucket repository is over the size limit 4gb
• bitbucket 1gb limit

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• GitHub Push Blocked: Repository Rule Violations (GH013 / Secret Detected) (GitHub)

Other Bitbucket errors

• Bitbucket Permission Denied (publickey)
• Bitbucket App Passwords Deprecated: Switch to API Tokens
• Bitbucket Authentication Failed on Git Push
• Bitbucket Pipelines Build Minutes Exceeded
• Bitbucket Pipeline Stuck or Queued
• Bitbucket Pipeline Exceeded Build Time Limit
• How to Cancel Bitbucket Subscription