Enable long file paths (aka "File Name Too Long" problem when syncing)
As a developer, I have deeply nested file structures with sometimes arduously long file names. I am unable to use OneDrive as it stands now because of this. I would like to suggest that this limitation be removed. I understand that it's probably a fundamental infrastructure issue but it's severely hampering Onedrive when compared to other competitors out there right now, despite all the other cool features.
We’ve enabled significantly longer paths for your personal OneDrive in our latest Windows and Mac releases (available from http://onedrive.com/download). You should be able to use paths up to 430 characters from the root of your local OneDrive sync folder. Our telemetry tells us this covers the vast majority of customers who have hit max path issues in the past. Note that if you have over 90 characters in your local OneDrive path (that is, from drive letter to OneDrive\) you will see characters over 90 cut into the budget of 430 characters (93 character local path will mean 427 characters available for path in the OneDrive folder).
Gerald Brickson commented
Exactly, I came to face this issue also. Then some recommended me Long Path Tool software and I am grateful to that person
the same issue, it is not solved with newer version of onedrive, the file show up on sync folder but just couldn't open it, i have to rename it online to open it in sync folder. this is not what we expected.
is there a way to shorten the file path and still refer to the correct URL?
This is one of the stupidest thing of onedrive.
Why the path length is limiting to 256.
It just means, we cannot keep internal structures with meaningful names.
I just did an automation project. And now when i try to copy the project folder for sharing, this error happens. How am i going to rename all those project folders? Amazing..
Now i need to use my local folder.
Fred Davis commented
Use Long Path Tool, Long Path Tool can simplify and
probably end your problems in unlocking, managing and
renaming files that appear to have a long filename
Jason Robertson commented
Its still a Problem AWS Cloudberry is much better at this please lift your game. This is extremely annoying.
I cannot copy or clone the Microsoft SPFx library due to this file limit restriction - https://github.com/SharePoint/sp-dev-docs
I had to download and shorten the zip path of the file repository. There was still one file that could not be copied.
I really believe that it is essential to solve this somehow.
In the years of my degree, I had a path pattern like
In the meanwhile, I have been working around various companies, including two startups of mine.
I tried to explain that path isn't not only a technical matter. If it was, we all would have chosen iPad. A IT because of the mindset maybe can think the better pattern of paths or use tweaks, scripts and tools. For an accountant or lawyer it is essentials to understand optical/visually where is a file and sometimes he needs filenames like Client-Second-Answers-to-The-Authority-Ver2.docx
So 420 characters maybe it's enough for a tweet, perhaps the 420 is the favourite number of Snoop Doog, but it is not enough of an organizing system.
Not done at all, still get this error in Onedrive for Business on Windows 10.
Have you tried 'long path tool'?
it's very helpful for me.
Long Path Tool will let you easily delete, copy or rename long path files.
I have just returned from a support task. The customer wanted to switch over to OneDrive from Google's cloud backup that I set up months ago to avoid paying for two online accounts. Google's backups had run perfectly. OneDrive failed like a beta program when confronted with long paths - and it was not a user-friendly job getting OneDrive to include folders outside the default settings.
Microsoft - If a file and its path fit on the NTFS system you chose for Windows you should have designed your backup facility to cope with it. Even my customer - a bookkeeper, not an IT professional commented that the backup should continue and then present a list of files that failed - it shouldn't just stop.
And people wonder why I always criticise Microsoft.
Blane Kemp commented
Hey "BOOM! IT'S DONE" Jason -- where are you? Can you enlighten us on what we need to do to make it work? Is is supposed to work in OneDrive for Business on Windows 10?
Please come back to us...as you can see from the 1000+ comments, nobody is seeing the boom.
Having the same issue since IT insisted we start using onedrive. Gonna talk to my IT people about it but i'm sure its nothing they can control
And why doesnt OneDrive just report/skip the only file/folder that is too long? It is not syncing the rest of my files.
Is this by design?
Copying a complete path (folder path and filename) with 282 characters into my latest version of OneDrive using windows explorer on windows 10 build 17763 still results in the error "The file name(s) would be too long for the destination folder."
It still does not work. I am trying to save a file with one character ("h"), and still can not save to One Drive Business.
It just makes using OneDrive meaningless.
Baingyn Tuulai commented
+1 for this.
Not saying I'm all right with the current setup—of course having a file path even greater than the "400 characters" that they claim would be amazing—but at least this should shed some light as to why file names not even reaching the 100-character count, will result in the same error.
I like and suggest you to try LongPathTool program. It is very helpful for copying/deleting or renaming long path files.
Boom, This is not done.