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)
  • DHenry commented  ·   ·  Flag as inappropriate

    Same here...I was just about to move the entire company (all 8 of us ;-) over to onedrive/sharepoint from dropbox but the "special character" issue is a deal killer. Guess I have to pay dropbox the $12.50/user for Business...and then Microsoft another $12.50/user for Exchange and Office....bummer. Good for Dropbox and Microsoft shareholders I guess.

  • mdingel commented  ·   ·  Flag as inappropriate

    I just loaded OneDrive to help myself integrate with Office365. I have been using Google Drive. I'm baffled by this error and just want to throw in my two cents that this should be fixed. OneDrive should support the same naming NTFS does. I will be un-installing OneDrive.

  • George commented  ·   ·  Flag as inappropriate

    File support should be the exact same as NTFS anything short of that just creates ISSUES!

  • JEsper commented  ·   ·  Flag as inappropriate

    god... is like 1990 all over again ... coooome on MS ... fix the **** problem !

  • Anonymous commented  ·   ·  Flag as inappropriate

    Same here! Every other application can handle these so-called "special characters". For me this is a big deal breaker. Indesign makes a .idlk file which has a tilde at the beginning of the file name. Because of that i can't open indesign-files within Onedrive - Sharepoint and i have too copy the file too my desktop and then re-save it again....

    Please make this work!

  • Anonymous commented  ·   ·  Flag as inappropriate

    Come on Microsoft these are not special characters, they are normal characters in file names on your operating systems all over the world.

  • Statick commented  ·   ·  Flag as inappropriate

    And as also pointed out elsewhere - it's not good enough to have a webpage somewhere that documents what is or isn't allowed, that you might find after googling the error message that certain files generate. Think harder. Much harder. Dropbox, GoogleDrive, even LiveDrive are wiping the floor with you guys simply because their software *works*

  • Statick commented  ·   ·  Flag as inappropriate

    this really needs to be sorted, it's wholly unacceptable that perfectly normal NTFS filenames cannot be synced in ODFB, and as plenty of other commenters have pointed out often software generates filenames that cannot be changed, if the filesystem accepts those names then ODFB needs to as well.

  • Jeremy commented  ·   ·  Flag as inappropriate

    This is a dealbreaker for me too - I must be able to sync files that contain # and % in the filename. It's ludicrous that a business-oriented cloud storage app like ODFB would not support this still in 2016. Even the personal OneDrive app does support such characters, and of course Google Drive, Dropbox etc does too. Please fix this with utmost urgency!

  • Roger commented  ·   ·  Flag as inappropriate

    The # character isn't that special... all legal ntfs characters should be legal here.

  • graeme kelly commented  ·   ·  Flag as inappropriate

    Using One Drive OS X client... a lot faster than BackBlaze but the character restriction is worrying.

    I have 199 file naming problems with my OneDrive and to change them and relink the files into my projects is too much.

    Please fix. The Cloud is meant to make things easier ?

  • Anonymous commented  ·   ·  Flag as inappropriate

    wow. i just subscribed and now we might reconsider. i have thousands of documents that have special characters in them and they won't be able to be saved in stupid is this???

  • Anonymous commented  ·   ·  Flag as inappropriate

    Think about it...harder. We want to move over from Dropbox, and are finding the workarounds a deal-breaker.

  • John commented  ·   ·  Flag as inappropriate

    I was about to subscribe to Office 365 and use OneDrive to back up all my Logic Pro X files, but it's refusing to back up folders/files as they have the wrong characters. What a wasted oppertunity. I get no problem with Google Drive.
    Is there no work around? As somebody else said, you can't change file names in Logic Pro X as it will corrupt the project.

  • Doron Friedlander commented  ·   ·  Flag as inappropriate

    Glen, the underscore isn't restricted. It's true that the groove based ODFB sync client does sometimes experience issues with the underscore. You can completely bypass that issue by using the NextGen Sync client(NGSC). The only draw back with the NGSC is that currently it cannot sync to SharePoint team sites, but this feature is being worked on and is expected to be released within the first quarter of this year.
    Here are some helpful links:

    OneDrive for Business Next Generation Sync Client is now available for deployment. See the following blog for more information:

    Restrictions and limitations when you sync OneDrive for Business libraries by using onedrive.exe -

    Deployment package for the new OneDrive sync client on Windows -

    Deployment package for the new OneDrive sync client on Mac -

    Get started with the OneDrive for Business Next Generation Sync Client in Windows/Landing Page -

    Get started with the OneDrive for Business Next Generation Sync Client in Windows -

    Get started with the OneDrive for Business Next Generation Sync Client on Mac OS X -

    Deploying the OneDrive for Business Next Generation Sync Client in an enterprise environment -

    Transition from the existing OneDrive for Business sync client -

    Deployment and administrative settings for the new OneDrive Sync Client (Mac) -

    OneDrive Administration Fast track page (links to all content) -

  • Doron Friedlander commented  ·   ·  Flag as inappropriate

    Erick, it is not 2 conventions for 1 for server and 1 for online! It's on convention required by windows and another required by SharePoint. What you will notice is that the more restrictive set of character limitations, on the right, applies to SharePoint Server. It's not a function of the Online service. The restricted characters are based on SharePoint limitation with some characters that SharePoint misinterprets. This applies to both SharePoint Server and any online service that leverages SharePoint Server. I am including the link for one of Microsoft's support documents on this topic. If you look at the bottom it clearly mentions SharePoint Server.

  • Erick Sodhi commented  ·   ·  Flag as inappropriate

    If a character is legal in a Windows filename it should be legal in a filename stored in SharePoint (including OneDrive for Business). I realize that this is a legacy issue because of the SharePoint/IIS platform, but it needs to be fixed. Users shouldn't have to deal with two file naming standards, especially when migrating from on-prem file servers and using processes in which characters that have previously been valid all of a sudden become invalid due to a migration to the cloud. It's obstacles like this that leave a sour taste in the mouths of users and result in a not-so-great attitude when it comes to talking about the cloud among their peers.

  • Glen O'Riley commented  ·   ·  Flag as inappropriate

    This is a ridiculous restriciton! I've removed percentages and may other wildcards but now I cannot even use a simple plain ordinary underscore in my file names lest it be marked invalid. WHY would you not realise an underscore is a fundamental part of many naming schemes now?

    Save a webpage in Internet exploder as well and there is a mywebsite_files folder is added and now is unable to be synced. Bloody hopeless when you cannot even support YOUR OWN naming conventions!!!

  • CIMA commented  ·   ·  Flag as inappropriate

    All legal characters for Windows filenames and directories should be allowed -- period.

  • Anonymous commented  ·   ·  Flag as inappropriate

    The point is not whether the restrictions are publicly known or not, it's whether they make sense. With the new sync client, people want to treat ODFB like a drive / filesystem. When I receive a document called RFP#2015-2323-3.docx, I want to be able to drag it to my ODFB and be done. I can; it just won't sync. I know enough to edit the file name to fix that, but most users don't. So it goes unloaded, unshared (if in a shared folder).

    Others have commented on the _files folder used with most "save as html" situations. Here, renaming the folder isn't an option at all as it breaks the html.

    Bottom line: ODFB is the *only* cloud storage service with such silly restrictions and inconveniences.

OneDrive Archive: OneDrive for Business

Feedback and Knowledge Base