Git LFS storage explained
Git LFS pointers and local payload storage
Git stores small pointer blobs in its object database. The optional large payload bytes live separately beneath .git/lfs/objects.
Pointer identity is not Git object identity
A Git pointer blob has a SHA-1 Git OID and names a distinct SHA-256 LFS object with a declared size. Multiple pointer blobs can refer to the same LFS object.
Local does not mean remote
A payload absent from local LFS storage may still exist on a remote server. GitSpire does not connect to LFS servers and makes no claim about remote availability.
Read-only, browser-local inspection
Payload inventory is requested only when you open the inspector. GitSpire reads canonical paths and file sizes, never payload contents, and performs no fetch, pull, prune, or migration.
Browser-local inspection
Inspect Git LFS storage locally.
GitSpire processes the repository you choose locally. Repository contents are not uploaded or changed.
Inspect Git LFS storage locally