Git repository storage explained
How Git stores repository data locally
A working tree contains checked-out files. The .git directory contains object data, refs, indexes, and supporting metadata. GitSpire measures these local representations without uploading them.
Loose objects and pack files
Git objects may be stored individually as compressed loose-object files or together in pack files. Pack indexes support object lookup but are not object payload storage themselves.
Logical bytes and stored bytes differ
Logical object size is the inflated Git payload. Stored object bytes are the lengths of local pack and loose-object files. They are different measurement domains and are not added together.
Git LFS is separate
Git LFS pointer blobs live in the Git object database, while optional local payloads live beneath .git/lfs/objects. GitSpire inspects that payload inventory only on request.
File length is not disk allocation
Browser file sizes report exact file lengths, not filesystem blocks, sparse-file allocation, or reclaimable storage. Reflogs and hooks are excluded from this view.
Browser-local inspection
Inspect Git storage locally.
GitSpire processes the repository you choose locally. Repository contents are not uploaded or changed.
Inspect Git storage locally