Large & Binary File Guard
Keep your Git repository lean and fast. Paste a list of changed files to find large or binary files that should be tracked with Git LFS.
Scan Report
Scan results will appear here.
Frequently Asked Questions
Why should I avoid committing large files to Git?
Git is not designed to handle large binary files. Committing them directly to your repository can dramatically increase its size, making cloning and fetching very slow for all team members. Over time, this can make the repository unwieldy.
What is Git LFS and how does it help?
Git Large File Storage (LFS) is a Git extension that replaces large files with text pointers inside Git, while storing the file contents on a remote server. This keeps your repository size small and fast.
What kind of files should be tracked with Git LFS?
Common candidates for Git LFS include large assets like images (`.psd`, `.png`), videos, audio files, datasets, and compiled artifacts like `.zip` or `.jar` files. This tool helps you identify these files and suggests patterns for your `.gitattributes` file.
How does this tool detect large or binary files?
This demonstration tool uses a simple set of rules based on file extensions that are commonly associated with large or binary files (e.g., `.zip`, `.psd`, `.mp4`). A more advanced implementation would also check the actual file size against a configurable threshold.
What do I do with the suggested `.gitattributes` patterns?
You should add the suggested patterns (e.g., `*.psd filter=lfs diff=lfs merge=lfs -text`) to your `.gitattributes` file in the root of your repository. This tells Git to handle those file types using Git LFS.