How to Fix the Fatal Not a Git Repository Error

You run a simple command like git status and instead of seeing your files, Git stops you with a scary red message: fatal: not a git repository (or any of the parent directories): .git. It feels like something is broken, but in most cases nothing is broken at all. Git is simply telling you that you are not standing inside a project that it knows about.

This guide explains what the message really means in plain English, why it happens, and how to fix it step by step. Whether you are in the wrong folder, you forgot to initialize a project, or your .git folder got deleted, you will find a clear fix below.

Quick Answer

The fatal: not a git repository error means you ran a Git command in a folder that is not a Git project and none of its parent folders are a Git project either. Fix it by moving into the correct project folder with cd, or by turning the current folder into a repository with git init. If the project was cloned before, re-clone it so the hidden .git folder is restored.

What Does This Error Actually Mean?

Every Git project has a hidden folder called .git at its root. That folder stores the entire history of the project, your commits, branches, and settings. When you type any Git command, Git looks for that folder in your current directory first.

If it does not find it there, Git walks up through every parent folder looking for it. Only when it reaches the top of your drive without finding a .git folder does it give up and show the fatal message. So the error is not about your files being damaged. It is about Git not knowing where its history lives.

Think of it like asking a library for a book while standing in a coffee shop: you are simply in the wrong building.

Why You Are Seeing This Error

There are a few very common reasons, and most beginners hit one of them in the first week of using Git.

• You are in the wrong folder. You opened your terminal in your home folder or in a parent folder, not inside the project itself.
• You never initialized the project. You created a new folder and files, but you never ran git init or cloned anything into it.
• You are one level too deep or too shallow. You might be inside a subfolder like src in a normal project this still works, but if the subfolder is a separate project or a downloaded zip, it will not.
• The .git folder was deleted or never arrived. This happens often when someone sends you a project as a zip file extracted without hidden files, or when the folder was copied without the hidden .git directory.
• You downloaded a ZIP from GitHub. A ZIP download gives you the files only. It does not include the Git history, so Git commands will fail until you initialize or clone properly.

How to Fix It Step by Step

Work through these steps in order. Most people fix the problem at step one or two, in under a minute.

Step 1: Check Where You Are

1. Run pwd on Mac or Linux, or cd without arguments on Windows, to see your current folder path.
2. Run ls on Mac or Linux, or dir on Windows, to list what is inside this folder.
3. Look for your project files. If you do not see them, you are definitely in the wrong place.

Knowing where your terminal is pointing is the single most useful habit in this whole fix. Terminals do not automatically open inside your project. They usually open in your home folder.

Step 2: Move Into the Correct Project Folder

1. Use cd path/to/your/project to move into the folder that contains your project.
2. For example: cd ~/projects/my-website or on Windows cd C:\Users\YourName\projects\my-website.
3. Run git status again. If you see branch information and file changes, you have fixed it.

A quick trick is to drag the project folder from your file explorer straight into the terminal window after typing cd with a space. This pastes the exact path and avoids typing mistakes. If you are just getting started, our guide on how to install Git on Windows 11 correctly also covers opening a terminal in the right folder from the right-click menu.

Step 3: If It Is a Brand New Project, Initialize Git

If this folder is a new project that has never used Git before, there is nothing to find because nothing was created yet. You need to create it.

1. Make sure you are inside the top-level folder of your new project with cd.
2. Run git init. Git will reply with a message about an initialized empty repository.
3. Run git status to confirm. You should now see your untracked files listed.
4. Add and save your first snapshot with git add . and git commit -m "Initial commit".

After git init, Git creates the hidden .git folder in that exact location. From that moment, every Git command run inside this folder or its subfolders will work as expected.

Step 4: If You Cloned Before, Check for the .git Folder

If this project worked yesterday and suddenly does not today, check whether the .git folder still exists.

1. On Mac or Linux, run ls -a to show hidden files and look for .git.
2. On Windows, run dir /a in Command Prompt, or turn on Hidden items in File Explorer and look manually.
3. If .git is missing, the folder is no longer a repository, even though all your normal files are still there.

If the folder is missing and you have a remote copy on GitHub, the cleanest repair is to clone a fresh copy into a new folder with git clone https://github.com/username/repository.git, then copy any unsaved local files across carefully. If there is no remote copy, you can run git init again to start a fresh history, but understand that the old commit history will not come back that way. It starts a brand new history from today.

Common Mistakes to Avoid

• Running git init everywhere until it works. This creates messy nested repositories. Only initialize the true root folder of a project, once.
• Running git init in your home folder. This makes Git try to track your entire computer. If you did this, remove the stray .git folder from the home directory carefully.
• Assuming your files are deleted. This error says nothing about your files. Your code is almost always still sitting safely in the folder.
• Deleting and recloning without checking for unsaved work. If you have local changes that were never committed or pushed, recloning into a new folder will not carry them over automatically. Copy them first.
• Ignoring case and spelling in paths. On Linux and Mac, Projects and projects are different folders. A tiny typo in cd leaves you in the wrong place.
• Using a ZIP download and expecting full Git features. Use git clone when you want history, branches, and push access. Use ZIP only when you want a simple copy of files.

Conclusion

The fatal: not a git repository error sounds serious, but it is one of the friendliest errors Git gives you. It almost always means one of three things: you are in the wrong folder, you have not initialized the project yet, or the hidden .git folder is missing. Check your location with pwd and ls, move into the right folder, or run git init for a genuinely new project, and you will be back to work in minutes. Build the habit of running git status as your first command in any new terminal. It instantly tells you whether Git can see a project and which branch you are on, saving you from this error again and again.

Frequently Asked Questions

Does this error mean my project is corrupted?

No, in almost every case your files are completely fine. The error only means Git cannot find a .git folder from where you are standing. Move into the correct folder, or restore the .git folder by recloning, and your project will work again without any damage to your code.

Can I fix it without losing my commit history?

Yes, if the original .git folder still exists somewhere. Simply moving into the correct folder preserves everything. History is only lost if the .git folder itself was deleted and you have no remote copy or backup to restore it from. That is one reason pushing regularly to GitHub is such a good safety habit.

Why does it work in one folder but not another on the same computer?

Because Git works per project, not per computer. Each project has its own .git folder. Being inside Project A tells Git nothing about Project B. Whenever you switch projects, you must also switch folders in your terminal using cd so Git looks in the right place.

What is the difference between git init and git clone?

git init starts a brand new, empty repository in a folder you already have. git clone downloads an existing repository, including its full history and its .git folder, from a remote host like GitHub. As the GitHub guide to cloning a repository explains, cloning is the right choice whenever the project already exists online.

I ran git init by accident in the wrong folder. How do I undo it?

Delete the hidden .git folder that was just created in that wrong location. On Mac or Linux you can use rm -rf .git from inside that folder, and on Windows you can show hidden files and delete the .git folder in File Explorer. Your normal files will not be affected, because git init only adds that one hidden folder.