Invalid Characters and Names for Files and Folders
The following table lists invalid characters and names based on access or sync type:
| Access or Sync Type | Invalid Characters | Invalid Filenames |
| Windows Network Folder | \, /, :, *, ?, ", <, >, I | CON, PRN, AUX, NUL, COM0-COM9, LPT0-LPT9 |
| OneDrive, OneDrive for Business on Office 365, and SharePoint Online | \, /, :, *, ?, ", <, >, I , # , % | .lock, CON, PRN, AUX, NUL, COM0 - COM9, LPT0 - LPT9, _vti_, desktop.ini Files may not start with ~ or $ |
| OneDrive for Business on SharePoint Server 2013 | \, /, :, *, ?, ", <, >, I, #, {, }, %, ~, & | |
| Archive to BackBlaze B2 | Control chars (ASCII < 32), DEL (ASCII 127), \, // | Files may not start or end with / |
| Archive to Wasabi | Some non-ASCII characters, 4-byte UTF-8 (like emojis, etc.), characters that cannot be reproduced in Unicode (xFFFD) | Files may not start or end with / |
| Morro Migrate, Duplicate, and Clone | \, /, :, *, ?, ", <, >, | |
For Windows network folders, due to limitations in Microsoft Windows, these characters are not allowed when creating, saving, or renaming files, folders, and shortcuts. They are supported in MacOS, but files and folders created with these characters may not be displayed or processed properly in Windows.
Avoid using these characters in file and folder names in cross-platform environments.
File and Folder Name Length
The maximum file and folder name length is 255 bytes. We save file and folder names with UTF-8 encoding, so each character may consume 1 to 5 bytes. For example, the English alphabet, numbers, etc., need a single byte. Greek, Cyrillic, etc., needs two bytes. Most of the CJK characters, Emoji, etc., requires 3 bytes.
Because of the differing byte lengths for different characters, file and folder maximum length may be fewer characters than expected. For example, if all of the characters in the file name are Japanese Hiragana, the maximum length is 85 characters.
Path Name Length Limitation
In addition to the file and folder name length limitations, the Windows operating system has a path length limitation, which is 260 characters (not bytes). However, Windows 10 version 1607 and later can override this restriction. Please refer Enable Long Paths in Windows 10.
Note that exceeding this path length limitation also requires support in the application. Notably, Windows File Explorer may still be limited to 260 characters. Some possible workarounds:
- Reduce folder name lengths or folder depth.
- Map the path as a drive letter in File Explorer or use subst.
- Use Powershell to access the path or use Robocopy to do recursive copies with deep paths.
For Archive shares, the path name length is also limited by the storage provider. The following table summarizes the limitations, but may not be up to date. For the latest and most accurate list of limitations, contact your storage provider.
| Provider / Service | Limitation | Note |
|---|---|---|
| AWS/S3 | 1024 Bytes | Unicode characters take more than one byte. |
| Wasabi/S3 | 1024 Bytes | Unicode characters take more than one bytes. 4 byte characters (such as Emoji) are not supported. |
| Backblaze/B2 | 1024 Bytes | Unicode characters take more than one byte. |
| Microsoft/Blob | 1024 Characters | Length is counted by characters, not bytes. |