What is the .git/index.lock file for?

When Git modifies the index (the staging area), it writes the new version to index.lock first, then atomically renames it to index. The lock guarantees only one process changes the staging area at a time, preventing corruption. It normally exists for a fraction of a second.

Is it safe to delete .git/index.lock?

Yes, as long as no Git process is actually running. The file contains a temporary copy of the index, not your work. Your commits, branches, and working files are untouched. Only delete it after checking nothing Git-related is active, otherwise you could interrupt a real operation.

Why does this keep happening with my IDE?

IDEs and Git GUIs (VS Code, IntelliJ, SourceTree, GitKraken) run Git in the background for status refreshes, auto-fetch, and staging. If you run a command in the terminal at the same moment, the two collide. Disable aggressive auto-refresh/auto-fetch, or let one tool finish before using the other.

The lock file comes back immediately after I delete it. What now?

Something is actively recreating it: usually an IDE, a file watcher, or a hook running Git in a loop. Close the IDE and background tools, delete the lock once more, and run your command. On network drives or cloud-synced folders (Dropbox, OneDrive), move the repository to a local disk: sync tools are a classic cause.

Download

fatal: Unable to create '.git/index.lock': File exists

This error means another Git process holds the lock on your staging area, or a crashed process left the lock file behind. Nothing is corrupted and no work is lost. Here is how to clear it safely.

Learn Git hands-on See the fix

gitquest — enquête

Error explained

What this error means

Whenever Git updates the index (your staging area), it creates .git/index.lock as an exclusive lock, makes its changes, then removes it. If the file already exists when a command starts, Git refuses to run: either another process is genuinely working, or a previous process died before cleaning up.

gitquest terminal: index.lock exists

$git commit -m "Add login screen"

fatal: Unable to create '/Users/you/project/.git/index.lock': File exists.

Another git process seems to be running in this repository, e.g.

an editor opened by 'git commit'. Please make sure all processes

are terminated then try again. If it still fails, a git process

may have crashed in this repository earlier:

remove the file manually to continue.

Root causes

Why this happens

Two Git processes at once

You ran a command while another was still working: a commit waiting for its message editor, a big rebase, or a second terminal on the same repository.

IDE or GUI in the background

VS Code, IntelliJ, SourceTree and friends run Git constantly for refreshes and auto-fetch. Their background operations can collide with your terminal commands.

A crashed process

Git was killed mid-operation (crash, closed terminal, reboot, out of disk space) and never removed its lock. The file stays behind and blocks everything.

Step-by-step fix

How to fix it

First rule: never delete the lock while Git is actually running. Check first, then remove.

Check for running processes

An editor waiting for a commit message or an IDE mid-operation is the most common culprit. Finish or close them first.

gitquest terminal: check processes

# 1. Check whether a Git process is still running

$ps aux | grep git

# Also check: is an editor waiting for a commit message?

# Is your IDE (VS Code, IntelliJ) doing a git operation?

# If yes: finish or close it, then retry your command

Remove the stale lock

If nothing is running, the lock is a leftover. Deleting it is safe and loses nothing.

gitquest terminal: remove and retry

# 2. No Git process running? The lock is stale. Remove it.

$rm .git/index.lock

# On Windows (cmd): del .git\index.lock

# 3. Retry your command

$git commit -m "Add login screen"

[main f2e9a1b] Add login screen

Best practices

How to prevent it

One Git operation at a time

Let each command finish before starting the next, especially between your terminal and your IDE's Git integration.

Keep repositories on a local disk

Repositories inside Dropbox, OneDrive, or network shares are a classic source of lock conflicts: the sync tool touches files while Git works. Sync your code with Git remotes instead.

Do not kill Git mid-operation

Avoid closing the terminal or pressing Ctrl+C during commits, rebases, or merges. If a command seems stuck, check whether it opened an editor and is simply waiting for you.

Related commands

git commit

Record your staged changes

git add

Stage changes into the index

git status

Inspect the state of your repository

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

Questions about index.lock

Understand what Git does under the hood

Index, staging area, lock files: GitQuest makes Git internals click through hands-on investigations in a safe terminal simulator.

Start practicing