Destination Path Too Long Error When Moving/Copying a File


If you are receiving an error “Destination Path Too Long” when trying to copy or move a file to a folder, try the quick trick below. The reason you are receiving the error is because Windows Explorer will fail to copy/delete/rename any path-name longer than 256 characters. The instructions below apply to Windows XP, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, and Windows Server 2012.

Full Error: “The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location that has a shorter path.”

Screenshot of “Destination Path Too Long” error on Windows Server 2008

Screenshot of “Destination Path Too Long” error on Windows 8

Step 1

The quickest fix for this, especially if you are needing to simply migrate a lot of folders from one place to another is to map a drive to the drilled down folder.
What I would do is browse to the hidden share path and copy it to your clipboard.


Step 2

Then browse to “Computer” or “My Computer” and click on Map Network Drive. Depending on your OS it might appear under the tools menu.


Step 3

Then simply paste your long path and hit Finish.


Step 4

Now you will be able to copy the files/folders into this location without receiving that error.

Tip #1

There also is a great tool called “Long Path Tool” that works great to fix this: However it isn’t free, the method above is.

Tip #2

Thank you Colin Albright for the comment below. Yes, you can also use 7-zip or any zip utility to fix the problem. Sometimes on single files, this could be a better and faster solution. Just zip the folder up, and your good to go.

Incoming search terms:

  • destination path too long
  • file name too long for destination folder
  • destination path too long error
  • destination path too long windows 2008 r2
  • destination path too long windows 7
  1. Posted by Frank Zabelli
    • Posted by Brian Jackson
      • Posted by Frank Zabelli
        • Posted by Brian Jackson
  2. Posted by Colin Albright
    • Posted by Brian Jackson
  3. Posted by stevenManilov
  4. Posted by stevenManilov
    • Posted by Brian Jackson
  5. Posted by fernandosho
    • Posted by Brian Jackson
  6. Posted by Neng Silvi
    • Posted by Brian Jackson
  7. Posted by BackupChain
  8. Posted by Terri Smith
  9. Posted by andrewop

Add Your Comment