Large File Detector
Large file detector online. Find files too big for Git. Get Git LFS recommendations—detect large files before pushing.
📋 Copy a Command, Run It, Paste the Output Below
Find large files (shows size + path)
du -ah . 2>/dev/null | sort -rh | head -20 More commands...
All files with sizes
du -ah . | awk '$1 ~ /[0-9]+[MGK]/ {print}' Find files over threshold
find . -type f -size +100k -exec ls -lh {} \; Paste Output
Supports both formats: filename 2.5M or 2.5M filename
⚙️ Size Threshold
= 100.0 KB
Features
- Detect files exceeding Git limits (100MB)
- Scan directory structure (simulated or drag-drop)
- Git LFS recommendations
- Size formatting
Common Use Cases
- Pre-commit check for large assets (videos, datasets)
- Cleaning up a repository
- Deciding which files to ignore
Large Files in Git
Git is not designed for large binary files. GitHub blocks files larger than 100MB. For large assets, use Git LFS (Large File Storage), which stores pointers in the repo and the actual data elsewhere.
Examples
Invalid - Video.mp4 (200MB)
Suggests: Git LFS Valid - Script.js (5KB)
OKFrequently Asked Questions
What is Git LFS?
An extension that replaces large files with text pointers inside Git, while storing the file contents on a remote server.
Can I remove a large file from history?
Yes, but it is effectively rewriting history. Tools like `git-filter-repo` or BFG Repo-Cleaner are simpler than standard git commands.
💡 Tips
- Don't commit `node_modules` or build artifacts. That is the #1 cause of bloat.