Why is my repository large?
See where Git is storing data and which historical content dominates it.
Local · read-only · deterministic
Understand what's really inside your Git repository.
Find large historical files, understand what Git still keeps, and inspect storage and Git LFS—locally, without uploading or changing your repository.
Open Local Repository Local · Read-only · No repository upload
Browser compatibility: Local repository analysis currently requires a Chromium-based desktop browser such as Chrome or Edge.
Why is this old file still here?
Trace historical paths, commits, and current references.
What is Git still keeping?
See what current Git references use, what they do not, and whether Git LFS is involved.
Git storage guides
Understand the repository before changing it.
- Why is my Git repository so large?
Learn why deleted files can remain in Git history, how blobs affect repository size, and how packed size differs from logical object size.
- What are unreachable Git objects?
Understand Git object reachability, current refs, detached HEAD behavior, and why unreachable objects are not automatically safe to remove.
- Git LFS pointers and local payload storage
Learn how Git LFS pointer blobs differ from local payload files, why SHA-1 and SHA-256 identities differ, and what missing local payloads mean.
- How Git stores repository data locally
Understand loose Git objects, pack files, indexes, logical object size, stored bytes, and how Git LFS storage remains separate.
Local by architecture
Your repository stays local.
Your repository is processed locally in your browser. GitSpire does not upload your repository and does not change it.
GitSpire reads repository data directly from the local directory you choose.
✓ Strictly read-only