How do I add a file type to Git LFS tracking?

What is Git LFS?

Git LFS (Large File Storage) keeps big files — PLC projects, images, videos, binaries — out of the normal Git history. In your repo, they're replaced by tiny pointer files, and the real content lives on the LFS server. Result: faster clones, smaller history, same versioning.

You can find more information about Git LFS in our Documentation. 

The .gitattributes pattern

Your .gitattributes file uses this style:

### *.zip

*.[zZ][iI][pP] filter=lfs binary

The ### line is a comment header. The bracketed letters ([zZ], [iI], [pP]) make the match case-insensitive, so file.zip, FILE.ZIP, and File.Zip are all caught.

Copy this pattern for any new extension (examples):

Getting Started

You have three options. Pick based on your goal:

Option A — Track going forward (safest)

Best for: Adding to LFS prior to repo size being an issue

1. Switch to the shared branch (e.g. main), pull latest.
2. Add the new entry to .gitattributes.
3. Commit and push. Message: Track *.psd files with Git LFS.
4. Let everyone else know to Pull a fresh copy of the repo

Done. New .psd files go to LFS; older versions stay where they are.

Option B — Rewrite all history (coordinated)

Best for: When you genuinely need to reduce repo size on disk.

Before you start:

• 📦 Back up the repo: git clone --mirror <repo-url> backup.git
• 📅 Schedule a maintenance window
• 📢 All collaborators must push their work and stop pushing during the migration
• 🔓 Be ready to temporarily disable branch protection rules

Steps:

1. Make a fresh clone in a separate folder (don't use your daily workspace):

   1. git clone <repo-url> repo-lfs-migrationcd repo-lfs-migrationgit fetch --all

2. Add the new entry to .gitattributes on the default branch, commit.
3. (Optional) Preview impact:

   1. git lfs migrate info --include="*.psd" --everything

4. Run the migration across all branches and tags:

   1. git lfs migrate import --include="*.psd" --everything

5. Review .gitattributes and remove any duplicate line.
6. Force-push everything:

   1. git push --force-with-lease --allgit push --force-with-lease --tags

7. Tell everyone to re-clone the repo. Old clones will be very hard to reconcile.

⚠️ Open PRs and code reviews referencing old commit hashes may break. Give reviewers a heads-up.

Option C — Archive old repo, start fresh (cleanest break)

Best for: When you don't need full Git history in the active repo and want to avoid force-pushes.

Before you start:

• Ask the team to merge or close any open PRs they care about
• List everything pointing at the current repo URL: CI/CD, deployments, docs, dependent repos, dashboards, bookmarks. You'll update all of them.

Steps:

1. On your Git host, create the new (empty) repo. Use a suffix like -v2 or -lfs, or a fresh name.
2. Clone the old repo into a clean folder, then drop its history:

   1. git clone <old-repo-url> new-repocd new-reporm -rf .git

3. Initialize fresh:

   1. git initgit lfs install

4. Confirm .gitattributes came over correctly. Add any new entries.
5. Stage, commit, push:

   1. git add .git commit -m "Initial commit (migrated from <old-repo-name>)"git remote add origin <new-repo-url>git push -u origin main

6. Match the new repo's settings to the old one: branch protection, reviewers, webhooks, deploy keys, secrets, integrations.
7. Archive the old repo. Most Git hosts offer this as a one-click setting — it makes the old repo read-only. Old PRs, issues, and commit links remain accessible.
8. Update everything pointing at the old URL.
9. Tell everyone to clone the new repo.

⚠️ Open PRs don't carry over to the new repo. Recreate any in-progress work as branches in the new repo before archiving. Some Git hosts can transfer issues — check before archiving if you want them moved.

Verifying it worked

• Web App: look for an "LFS" badge next to the file in the repo
• Local command, list everything in LFS:
  • git lfs ls-files

• Open .gitattributes locally and confirm your entry is there in the right style.

Troubleshooting

Command reference

Used in Scenario 2 and Scenario 3 Options B and C. Everything else is desktop-client only.