How to Undo a Git Add: Unstaging Files Before You Commit

Running git add is one of the most routine actions in a Git workflow — but it's also one of the easiest to do too early, too broadly, or on the wrong files. The good news: staging a file doesn't lock you in. Git gives you clear, reliable ways to reverse a git add before the changes ever land in a commit.

What "Git Add" Actually Does

When you run git add, you're not saving your work permanently — you're moving changes from your working directory into the staging area (also called the index). Think of the staging area as a draft queue: files sit there waiting until you run git commit, at which point they become part of your project's permanent history.

Until that commit happens, the staging area is entirely reversible. Undoing a git add simply means moving a file back out of that queue — your actual file contents aren't touched.

The Main Commands for Unstaging Files

git restore --staged (Git 2.23 and later)

This is the current recommended approach for most users. It's explicit, readable, and purpose-built for this exact task.