How to Fix the “Path Too Long” Error When Extracting ZIP Files in Windows 10 and 11

The “Path too long” error usually appears when Windows tries to extract a ZIP file and one or more folders inside it create a file path that is longer than Windows can handle. It is common with deeply nested folders, project archives, game mods, and files downloaded from the internet.

The good news is that this problem is usually fixable without damaging the archive. In most cases, shortening the extraction path or enabling long file paths in Windows will solve it.

Why the “Path Too Long” Error Happens

Windows has historically had a limit on the maximum length of a file path. A file path includes the drive letter, every folder in the route, the filename, and the extension. If that total becomes too long during extraction, Windows File Explorer may stop and show an error.

• Long folder names inside the archive
• Extracting to a deep folder path, such as inside several nested folders
• A ZIP file with many layers of subfolders
• Windows long path support being turned off
• Using File Explorer instead of another extraction tool

1. Extract the ZIP File to a Shorter Folder Path

The simplest fix is often to extract the ZIP file to a folder with a very short path. For example, use something like C:\Temp or C:\ZIP instead of a folder buried several levels deep on the desktop or in Documents.

1. Create a new folder directly on your C: drive, such as C:\Temp.
2. Move the ZIP file into that folder if needed.
3. Right-click the ZIP file and choose Extract All, or use your extraction tool.
4. Choose the new short folder as the destination and try again.

2. Rename the ZIP File and Any Parent Folders

If the ZIP file itself has a long name, or if it is stored in a folder with a long name, shortening those names can make the extraction succeed.

1. Rename the ZIP file to something short and simple, such as files.zip.
2. Move it out of folders with long names.
3. If the archive is inside a deeply nested location, place it temporarily in a short path like C:\Temp.
4. Try extracting it again.

3. Enable Long Path Support in Windows 10 or Windows 11

Windows 10 and Windows 11 can support longer file paths, but the feature may not be enabled on your system. Turning it on can resolve the error for many users.

1. Press Windows + R, type gpedit.msc, and press Enter if you have Group Policy Editor available.
2. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem.
3. Open Enable Win32 long paths and set it to Enabled.
4. Click Apply and OK.
5. Restart Windows if needed, then try the extraction again.

4. Turn On Long Paths in the Registry

If Group Policy Editor is not available, you can enable long path support through the Registry. This changes the same Windows behavior but from a different location.

1. Press Windows + R, type regedit, and press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
3. Find LongPathsEnabled. If it does not exist, create a new DWORD (32-bit) Value with that name.
4. Set the value to 1.
5. Close Registry Editor and restart the computer if required.

After this setting is enabled, Windows applications that support long paths should be able to work with longer folder structures.

5. Use a Different Extraction Tool

File Explorer is not always the best tool for large or deeply nested ZIP archives. Third-party tools often handle long paths better and may give you more control over the extraction process.

• 7-Zip
• WinRAR
• PeaZip

After installing one of these tools, right-click the ZIP file and extract it using that program instead of File Explorer. Some tools also let you choose shorter destinations more easily.

6. Extract the Archive in Smaller Parts or Change the Folder Structure

If the ZIP file contains an unusually deep folder tree, the easiest fix may be to reduce the number of nested folders after extraction. In some cases, the archive itself may need to be reorganized or re-created by the person who made it.

1. Extract the archive to a short folder path.
2. Open the extracted folders and see whether one branch of the directory tree is especially deep.
3. Move the files you need closer to the root folder if appropriate.
4. If you created the ZIP file yourself, re-pack it with shorter folder names or a flatter folder structure.

This is especially useful for developers, modders, and anyone handling project folders that contain repeated subfolder names.

Which Fix Should You Try First?

• Start by extracting to a short path such as C:\Temp.
• If that fails, try a different tool like 7-Zip.
• If you regularly work with deep folder structures, enable long path support in Windows.
• If the archive is yours, consider shortening folder names before sharing it.

When the ZIP File Itself May Be the Problem

If none of the fixes work, the archive may be damaged or incomplete. That is more likely if the file will not open correctly in multiple extraction tools, or if the ZIP file was interrupted during download.

• The archive downloads again with the same error
• The file opens but fails at different points each time
• Multiple extraction tools report corruption or missing data

In that case, download the ZIP file again from the original source if possible. If you created the archive yourself, rebuild it from the original files.

A Practical Order to Try the Fixes

1. Extract the ZIP file to a short folder such as C:\Temp.
2. Rename the ZIP file and avoid long parent folder names.
3. Try 7-Zip, WinRAR, or another extraction tool.
4. Enable long path support in Windows.
5. If needed, use the Registry or Group Policy setting to keep the fix permanent.
6. Check whether the archive is corrupted and re-download it if necessary.

Conclusion

The Windows “Path too long” error is usually caused by a path-length limit, not by a serious system problem. In most cases, a shorter extraction folder or a different unzip tool will solve it quickly. If you deal with long folder structures often, enabling long path support in Windows is the most useful long-term fix.