What does "pathspec did not match any file(s) known to git" mean?

It means Git cannot find the file, branch, or path you referenced in your command. The name you typed does not match anything in the Git index or in the list of branches. This is usually caused by a typo, a file that has not been tracked yet, or a case sensitivity mismatch.

Why do I get this error when checking out a branch?

Git uses the same pathspec error for branches and files. If you run "git checkout my-branch" and that branch does not exist locally or remotely, you will see this error. Run "git branch -a" to see all available branches, and "git fetch" to download remote branches first.

How is this related to case sensitivity?

Linux file systems are case-sensitive: "File.txt" and "file.txt" are two different files. macOS and Windows are case-insensitive by default. If a teammate on Linux committed "File.txt" and you try to checkout "file.txt" on Linux, Git will not find it.

Can this error happen with git add?

Yes. If you type "git add myfile.js" but the file is actually named "MyFile.js" or does not exist at all, you will get the same pathspec error. Double-check the filename and path.

How do I avoid this error in the future?

Use tab completion in your terminal to auto-complete file and branch names. Run "git status" before running commands to confirm which files are available. Establish naming conventions with your team to avoid case sensitivity issues across operating systems.

pathspec did not match any files — How to fix it

This Git error means the file or branch you referenced does not exist, is not tracked, or has a typo. Here is how to find and fix the problem.

Learn Git step by step

Common Error

What this error means

When Git says error: pathspec 'file' did not match any file(s) known to git, it means it looked through its index and branch list and could not find anything matching the name you provided.

A pathspec is simply the file path or branch name you pass to a Git command. If that name doesn't match a tracked file, an existing branch, or a valid path, Git gives up and shows this error.

The good news: this error never causes data loss. It's Git telling you "I can't find what you're looking for" before doing anything.

terminal — pathspec error

# You try to checkout a file or branch

$git checkout my-feature

error: pathspec 'my-feature' did not match any file(s) known to git

Why it happens

Typo in the filename or branch

The most common cause. You typed feture instead of feature, or forgot a directory in the path. Git matches names exactly — there is no fuzzy search.

File not tracked by Git

If you created a new file but never ran git add, Git does not know about it. Commands like git checkout or git stash cannot find untracked files.

Case sensitivity mismatch

Linux treats App.js and app.js as different files. macOS and Windows do not. Cross-platform teams often run into this when filenames were committed with different casing.

How to fix it

Follow these steps to find the mismatch and resolve the error.

1. Check with git status

terminal — diagnose

# Step 1: Check what Git actually sees

$git status

On branch main

Untracked files:

myFeature.js

# The file name is different from what you typed!

2. Add or fetch the target

terminal — fix

# Step 2: Add the file if it is untracked

$git add myFeature.js

# Or check available branches

$git branch -a

* main

remotes/origin/my-feature

# Fetch and switch to the remote branch

$git fetch origin

$git switch my-feature

branch 'my-feature' set up to track 'origin/my-feature'

3. Fix case sensitivity

terminal — casing

# Step 3: Check for case sensitivity issues

$git ls-files

README.md

src/App.js

src/utils/helper.js

# On Linux, App.js and app.js are different files

$git checkout src/App.js

Updated 1 path from the index

How to prevent it

Use tab completion

Type the first few characters of a file or branch name and press Tab. Your shell will auto-complete the name or show you the available options. This eliminates typos.

Run git status first

Before running destructive or complex commands, run git status to see exactly which files are tracked, modified, and untracked. It takes one second and saves debugging time.

Agree on naming conventions

Use lowercase filenames and kebab-case branch names across your team. This avoids case sensitivity surprises when collaborators work on different operating systems.

Related commands

git add

Stage files so Git starts tracking them

git status

See which files are tracked, modified, or untracked

git rm

Remove files from the Git index

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

FAQ — pathspec did not match

Stop guessing, start understanding Git

GitQuest teaches you Git through hands-on practice so error messages make sense.

Start learning Git