Cross Domain · protocol · Git LFS project (open source; originated at GitHub)

Git Large File Storage (Git LFS) API

GitHub’s 2015 extension for storing large files outside a Git repository, with an HTTP Batch API that is the cleanest published version of the metadata-first upload — the client POSTs object IDs and sizes, the server replies per object with an upload or download action carrying a URL, the headers to send and an expiry, the client transfers bytes to that URL, and an optional verify step closes the loop. Implemented by GitHub, GitLab, Gitea, Bitbucket and Hugging Face.

Git LFS project (open source; originated at GitHub)Governing body
2015First published
Batch API v1; transfer adapters basic...Current version
0providers in the catalog

Also known as Git Large File Storage, Git LFS Batch API, LFS.

Providers that carry Git LFS 0

No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements Git LFS and says so in its APIs.json profile appears here on the next build. Add or correct a listing.

Read from the API Evangelist standards directory, facts verified 2026-10-07. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.