How to fix error: Sparse checkout leaves no file in the working directory in Git

GitINTERMEDIATEMEDIUM

The 'Sparse checkout leaves no file in the working directory' error occurs when Git's sparse-checkout patterns don't match any files in the repository. This is commonly caused by incorrect path specifications, file encoding issues on Windows, or attempting to checkout non-existent directories.

What this error means

This error indicates that after applying your sparse-checkout configuration, Git cannot find any files that match the specified patterns. When using sparse checkout, Git limits the working tree to only include files that match certain patterns or directories. If none of your patterns match actual content in the repository, Git refuses to proceed because you would end up with an empty working directory. Sparse checkout is a powerful feature for working with monorepos or large repositories where you only need a subset of the files. In **cone mode** (the default in Git 2.25+), you specify directories to include, and Git automatically includes all parent directories and files. In **non-cone mode**, you use gitignore-style patterns for more granular control. The error typically occurs in these scenarios: 1. The sparse-checkout file contains paths that don't exist in the repository 2. The sparse-checkout file has encoding issues (especially on Windows) 3. You cloned with `--no-checkout` and the index is empty when sparse patterns are applied 4. There's a mismatch between what you think exists in the repo and what actually exists

How to fix "error: Sparse checkout leaves no file in the working directory"

1Verify the directory exists in the repository

First, confirm that the path you're trying to sparse-checkout actually exists in the repository.

bash

# List all directories in the repository at the root
git ls-tree --name-only -d HEAD

# List directories at a specific path
git ls-tree --name-only -d HEAD path/to/

# Search for a specific directory name
git ls-tree -r --name-only HEAD | grep -i "your-directory-name"

# Check repository structure without full checkout
git ls-tree --name-only HEAD

Important: The folder structure shown in GitHub/GitLab web interface might not match the actual repository structure. Always verify paths using git ls-tree.

2Fix file encoding issues (Windows)

On Windows, PowerShell and CMD create files with UCS-2 LE BOM encoding, which Git cannot parse. The sparse-checkout file must be in UTF-8 or ASCII encoding.

Option 1: Use Git Bash instead of PowerShell/CMD

bash

# In Git Bash, not PowerShell
git sparse-checkout set path/to/directory

Option 2: Force ASCII encoding in PowerShell

powershell

# Instead of echo, use Set-Content with ASCII encoding
Set-Content .git/info/sparse-checkout "path/to/directory" -Encoding Ascii

# Or use Out-File with explicit encoding
echo "path/to/directory" | Out-File -Encoding ASCII .git/info/sparse-checkout

Option 3: Manually create the file in a text editor
Open Notepad or VS Code, add your paths (one per line), and save as UTF-8 without BOM.

3Use correct path format

Ensure your sparse-checkout paths follow the correct format:

bash

# Correct format: forward slashes, no trailing slash, no leading slash
git sparse-checkout set path/to/directory

# In cone mode, specify directories only (no glob patterns)
git sparse-checkout set apps/my-app libs/shared

# Check current sparse-checkout configuration
git sparse-checkout list

Path rules:
- Use forward slashes (/) even on Windows
- No leading slash (use path/to/dir not /path/to/dir)
- No trailing slash or spaces
- Case must match the repository exactly on Linux/macOS

4Handle --no-checkout clone properly

If you cloned with --no-checkout, the index is empty. You need to populate it before sparse checkout patterns can be applied.

bash

# After clone --no-checkout, initialize sparse-checkout first
git sparse-checkout init --cone

# Then set your directories
git sparse-checkout set path/to/directory

# Or if that doesn't work, reset and checkout
git reset --hard HEAD
# Then re-apply sparse checkout
git sparse-checkout reapply

For Git 2.25+, the recommended modern workflow is:

bash

git clone <URL> --no-checkout <directory>
cd <directory>
git sparse-checkout init --cone
git sparse-checkout set apps/my-app libs/my-lib
git checkout main

5Disable and reconfigure sparse checkout

If your sparse checkout is in a broken state, disable it completely and start fresh:

bash

# Disable sparse checkout and restore all files
git sparse-checkout disable

# Verify all files are restored
git status

# Start over with sparse checkout
git sparse-checkout init --cone
git sparse-checkout set your/actual/path

If disable doesn't work, manually reset:

bash

# Remove sparse checkout config
git config --unset core.sparseCheckout
git config --unset core.sparseCheckoutCone

# Remove sparse-checkout file
rm .git/info/sparse-checkout

# Reset to get all files back
git read-tree -mu HEAD

6Verify sparse-checkout file content directly

Inspect the actual content and encoding of your sparse-checkout configuration:

bash

# View sparse-checkout file content
cat .git/info/sparse-checkout

# Check file encoding (Linux/macOS)
file .git/info/sparse-checkout

# On Windows Git Bash, check for hidden characters
cat -A .git/info/sparse-checkout

# Compare against what git shows
git sparse-checkout list

The file should look like:

bash

/*
!/*/
/path/to/directory/

In cone mode, Git automatically adds the patterns. The /* keeps root files, !/*/ excludes all directories, and then specific paths are included.

How to fix error: Sparse checkout leaves no file in the working directory in Git

What this error means

Typical symptoms

Common causes

How to fix "error: Sparse checkout leaves no file in the working directory"

Advanced notes

Related errors

Official resources & further reading