Restricted Characters

---

The Files.com platform has few restrictions regarding characters that can be used in file and folder names. For both file names and folder names, the following characters cannot be used:

• / (forward slash)
• \ (backslash)

Additionally, the following cannot be used as folder or subfolder names:

• . (single period)
• .. (double period)

Any file or folder names containing the above characters cannot be stored on Files.com. Rename these files and folders, to remove or replace these characters, prior to uploading them to Files.com.

Operating systems such as Windows, Linux, and Mac each have their own specific restrictions for which characters can be used to name a file or folder. Additionally, 3rd party service providers can overlay their own restrictions. Cloud based object storage usually has fewer restricted characters than on-premise systems. It is not practical for Files.com to maintain a database of all restrictions that may apply.

When a character is restricted by a system then it cannot be used for file names nor for folder or directory names on that system.

When using a Remote Server integration on your Files.com site, be aware that the remote system will have a greater list of restricted characters than Files.com does. For better interoperability, we recommend avoiding the use of any possible restricted characters in file and folder names.

Some examples of restricted characters on other systems include:

• < (less than)
• > (greater than)
• : (colon)
• " (double quote)
• / (forward slash)
• \ (backslash)
• | (vertical bar or pipe)
• ? (question mark)
• * (asterisk)
• # (hash or pound)
• % (percent)
• & (ampersand)
• @ (at)
• ^ (caret)
• $ (dollar)
• ! (exclamation)

Most times, restricted characters in file names or folder names go unnoticed until attempts are made to transfer those items to other systems. When transferring to other systems, you may see error messages showing failures. It's impossible for us to know every error message for every system but messages that mention phrases such as "invalid", "permission denied", "cannot write", "cannot store", or "unknown entity" can indicate that an invalid character exists in a file or folder name.

When uploading items that contain invalid characters, some systems will automatically replace those characters with compatible alternatives. For example, a file named myfile<1>.txt might be renamed to myfile%3C1%3E.txt, myfileU+003C1U+003E.txt, or myfile&lt1&gt.txt. This new name is then retained going forward.

Systems that don't support automatic encoding or transcoding of these restricted characters will fail to upload the item and provide a failure message.

Files.com allows you to upload to various types of Remote Server so bear in mind that an upload that succeeds for one type of Remote Server may fail for another type due to each one having different character restrictions.

The type of client, or app, being used to upload can also have an effect. Web browsers usually encode restricted characters during an upload. Different FTP, SFTP, and WebDAV clients will handle encoding or transcoding restricted characters differently. An upload with one client, or app, may succeed but may fail when using another.

When downloading items that contain invalid characters, your local system will determine which characters are restricted. Windows, Mac, and Linux each have their own lists of restricted characters so a download that succeeds on one may fail on another.

The type of client, or app, being used to download can also have an effect. Web browsers usually encode restricted characters during a download. Different FTP, SFTP, and WebDAV clients will handle encoding or transcoding restricted characters differently. A download with one client, or app, may succeed but may fail when using another.

Files and folders should be renamed to remove or replace any restricted characters prior to downloading.

When a Remote Server Sync is used, the destination location may reject any file or folder that contains restricted characters in their names. Rejected files, which couldn't be stored by the remote system, will fail for this sync, and all following syncs, until the restricted character is removed or replaced in the file name. This happens when the source system and the destination system are of differing types. Check for error messages in the logs and rename any failed items to remove, or replace, any restricted characters.

When using an automation to move or copy items to a location that resides in a Remote Server Mount, the remote server may reject any file or folder that contains restricted characters in their names. Rejected files, which couldn't be stored by the remote system, will fail for this Automation, and all following runs of the Automation, until the restricted character is removed or replaced in the file name. Check for error messages in the logs and rename any failed items to remove, or replace, any restricted characters before re-running the automation again.

If you see issues with invalid file or folder names, we recommend you modify those names to remove the restricted characters. Once the restricted characters have been removed or replaced, retry the operation or action again.

If your workflow involves files and folders moving between different systems, or between different storage locations, then you should avoid the use of any possible restricted character in file and folder names.