How do you handle large binary files in Git?

Short answer: Large binary files (like images, videos, or data models) bloat Git repositories since Git stores every version.

Explain a bit more

To handle them efficiently, I use Git LFS (Large File Storage). Setup: git lfs install git lfs track "*.psd" git add .gitattributes git commit -m "Track Photoshop files with Git LFS" Explanation: Git LFS replaces large files with lightweight text pointers inside Git, while the actual binary files are stored on a separate LFS server. Example: If a game project has large texture files, Git LFS prevents the repo from becoming gigabytes in size, improving clone and fetch performance.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.