File naming convention for inSync Share

inSync Share file naming convention

The files and folders within the inSync Share folder are not case-sensitive. This means that you cannot have two files that have the same name, but different cases. You also cannot have two folders that have the same name but different cases. The following table lists different file and folder naming scenarios and their outcome.

Scenario

Outcome

You attempt to create a file using a file name that already exists, but you create the new file name using a different case

inSync prompts you to save the new file with a different name. For example, if ReadMe.txt exists inside a folder within inSync Share and you attempt to create readme.txt in the same folder, inSync prompts you to save the new file as readme(2).txt.

You attempt to create a folder using a folder name that already exists, but you create the folder name using a different case

inSync prompts you to merge the new folder with the existing folder that has the same name. For example, if a folder named Documentation exists in a folder within inSync Share and you attempt to create doCUmentation within the same folder, inSync prompts you to merge doCUmentation with Documentation.

You attempt to upload a file using a file name that already exists, but you upload the file name with a different case by using inSync Web

inSync overwrites the content of the existing file with the content in the new file. For example, if notes.txt exists in a folder and you attempt to upload NoTes.txt in the same folder, inSync overwrites the content of notes.txt with the content of NoTes.txt.

You create two files, one from inSync Share and the other from inSync Web

Both files are visible via inSync Web. However, only one file will be synced to your devices.

You restore a deleted file when a file with the same name exists

You cannot restore a deleted file if a file with the same name exists in the same directory. You must first change the name of the deleted file and then restore it.

You sync folders with the name ending with a space or a period

Windows OS does not support folder names that end with a space or a period. Such folders can be created on Mac OS or Linux OS. On Mac or Linux OS, during sync operation, inSync Share renames the folder to remove the space or period and then saves the folder. If a folder with the same name already exists, then the newly-added folder will get saved with a conflict tag appended to the file name in the <filename>(conflict).extension format.

For example, inSync Share renames the 'inSync.' folder to inSync and then syncs the folder. However, if a folder with the name inSync already exists, then the newly-synced folder is synced with the name inSync (Bad Conflict). If the inSync (Bad Conflict) folder already exists, then inSync renames the folder to inSync (Bad Conflict 1) and so on.

You sync folders that have the same name

inSync Share saves the newly-added folder with (1) appended to the file or folder name, in the <filename> <1>.extension format.

For example, if a folder with the name inSync already exists, then the newly-synced folder is renamed to inSync (1). If the inSync (1) folder already exists, then the newly-synced folder is renamed to inSync (1) (1) and so on.

Notes:

This behavior is seen only in your inSync Share account, and the folder names are not updated globally.

This scenario arises when you reactivate inSync on a device that already has an inSync Share folder with some contents in it.

To resolve this issue, you must manually change the folder names.

​​Note: On Linux laptops, if your create multiple files with the same name but different cases, all files other than the original will appear with the suffix conflict.

Usage of special characters

inSync Share does not sync files that contain specific special characters. The following table lists file and folder naming scenarios and their outcome.

If a file or folder name contains any of these special characters, those files or folders do not sync to the server. This is because some of the file systems do not allow these characters in the file or folder names.

Invalid prefix name list:'.~inSync$', '~$', '.~', '~inSync$'

If a file or folder name starts with any of these prefix names, those files or folders do not sync to the server. This is because inSync Share uses these names for temporary file names.

Invalid suffix name list:

'.tmp'

If a file or folder name ends with .tmp, those files or folders do not sync to the server. This is because these are usually temporary files created on the computer.

Invalid file/folder names:'desktop.ini', '.DS_Store', 'Icon\r'

If the file or folder is the same as any of these names, those files or folders do not sync to the server. This is because these are system-specific files.

Note: These special characters do not have any impact on backups. They only have an impact on inSync Share.