Feedback by UserVoice

I suggest you ...

Allow files that have special characters in the name to be uploaded

This makes it hard to convert users in our company.

1,314 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Password icon
Signed in as (Sign out)
  • Paul Martell-Mead commented  ·   ·  Flag as inappropriate

    The problem here is not the files and folders that Windows doesn't like but the ones which are perfectly legal on a Windows file system. Specficially, # in filenames and _files folders.

    Lots of people save HTML pages to disk. Often its a order they placed. When you save from e.g. Chrome you end up with an HTML file called something like "Order #21292.html" and an associated _files folder containing the assets from that HTML file. Onedrive can't handle either. If I script a rename, then the HTML file breaks. Now I have to script editing the HTML links inside the html file.

    Too hard!

  • Viktor commented  ·   ·  Flag as inappropriate

    Character limitation is a real deal breaker for my business. We share Logic Pro projects and as Miguel said, Logic uses some of these "invalid" characters in filenames that cannot be changed without ruining the project. It's a shame because in many other ways OneDrive is superior to Google Drive. OneDrive uses lot less CPU power, and the iOS app i better too, Googles iOS app is very laggy.

  • David commented  ·   ·  Flag as inappropriate

    Doing some proof of concept testing right now and running into the # and % limitation.

    Windows NTFS already has a restricted character set vs the other supported desktop platform of MacOS. Adding additional character limits will likely be a deal breaker for my users.

  • Jacob commented  ·   ·  Flag as inappropriate

    Mr. Krippner, if you think having a list on some site naming all of the invalid file names is enough, then you're dead wrong. First, OneDrive needs to throw that link in the user's face when a Sync failure takes place, instead of having to just *know* that it exists and search for it on their own.

    Second, why would you not provide a file renaming tool that works with Windows directories so that users can quickly fix all of their naming issues?

    It's almost like you WANT companies to choose other products.

  • S Roose commented  ·   ·  Flag as inappropriate

    I was looking to move files across for the various users in our company - but not being able to sync # and % prevents this.. We will continue with Dropbox I am afraid

  • Jorge commented  ·   ·  Flag as inappropriate

    The limitations should match the limitations of windows 10 whatever they are. It doesn't make sense otherwise.

  • Bas Conijn commented  ·   ·  Flag as inappropriate

    Visual Studio will create a "Visual C#" folder in my documents (OneDrive for Business). This will cause a sync problem because the name is invalid.

  • Miguel commented  ·   ·  Flag as inappropriate

    As a multi-platform user, this is extremely disturbing. I am user of a Mac OSX, Windows 7 and Android OS's and I synchronize files between the first two. So, because in Mac I use HFS+, I get very often a message from the OneDrive app telling to me that a high number of files have invalid characters.

    I can change some of them, but other are impossible to change without making them unusable. Files like the ones that Logic Pro creates inside the project folder that if you change the name you corrupt the project.

    I would appreciate any change in this regard.


  • Anonymous commented  ·   ·  Flag as inappropriate

    Agree with this. OneDrive Business needs to allow for # and %. How are we supposed to promote a business application still hampered with these restrictions? These characters are NOT restricted in Windows, so we have a lot of users who have added these characters to file folder structure over the years. It would be a nightmare to move them to OneDrive Business with these limitations still in place. Hoping you can resolve this, especially since these restrictions are not there with OneDrive Personal.

  • Jason commented  ·   ·  Flag as inappropriate

    Nice that you don't support your own applications. Visual studio creates multiple folders 'Visual C#' that are not synced because of the # symbol.

  • Bill the Nerd commented  ·   ·  Flag as inappropriate

    Even a dialog box that list the files with bad names, and let you rename them easily individually or in bulk, or even renamed them automatically for you would be a massive improvement

  • Jose123 commented  ·   ·  Flag as inappropriate

    Currently I am using a Ahsay software for backup.Ahsay Backup software is a robust cross-platform backup solution which allows businesses and managed backup service provider to backup virtual machines, databases and servers to local/mapped network drive, locally hosted backup server, or online backup server hosted in datacentre. I would like to suggest you to try this software, because its reThanks

  • Glenn Barker commented  ·   ·  Flag as inappropriate

    Agreed. I still run into issues with # and %. Since we have a lot of financial documents, you can imagine how often both of those pop up.

  • Rob Franco [MSFT] commented  ·   ·  Flag as inappropriate

    Hi Boian, we are progressively removing these character restrictions. We announced the beginning of the process in the summer of 2013 and the multiple dots restriction was lifted earlier this summer. Are you still seeing restrictions on files with multiple dots?

  • Boian Soloviov commented  ·   ·  Flag as inappropriate

    Astinishingly quiet for such a serious issue here. NTFS special characters were not enough, then come the HTTP limitation set. But even this is not enough, on top of that even multiple dots are forbidden. Try to save Ellipses...docx or Invoice from Company Inc..pdf and see what happens.

1 2 5 6 7 9 Next →

OneDrive Archive: OneDrive for Business

Feedback and Knowledge Base