The Git LFS client uses an HTTPS server to coordinate fetching and storing large binary objects separately from a Git server. The basic process the client goes through looks like this:

1. Discover the LFS Server to use.
2. Apply Authentication.
3. Make the request. See the Batch and File Locking API sections.

The Batch API is used to request the ability to transfer LFS objects with the LFS server.

API Specification:

• Batch API

Current transfer adapters include:

• Basic

Experimental transfer adapters include:

• Tus.io (upload only)
• Custom

The File Locking API is used to create, list, and delete locks, as well as verify that locks are respected in Git pushes.

API Specification:

• File Locking API