Filename Requirements

To sync files or folders, they must comply with any filename restrictions on the destination folder and with the overall requirements for filenames on Files.com. For example, Files.com disallows spaces at the end of file and folder names.

If Files.com encounters files that would not be allowed on the Files.com side, the sync results in a Partial Failure. Failure details are available in the Sync Logs.

Case Sensitivity

Syncs use the Files.com case sensitivity rules.

Files.com applies a best-effort approach to make case conversions work intelligently. Perfectly modeling ideal behavior in this situation is not possible.

Because two names that differ only by case are the same name under those rules, a run omits folders that collide and records one of these messages in the Sync Logs:

Skipped due to multiple files/folders having the same case-insensitive name on the source.

Skipped due to multiple files/folders having the same case-insensitive name on the destination.

Source folders named MYSTUFF and mystuff both match a destination folder named MyStuff, and transferring both would merge their contents into it irreversibly, so the sync omits them instead. The destination message means the reverse: several destination folders match one source folder by case-insensitive name, and the sync cannot determine which one is the correct target.

Leave only a single copy of any folder name in the sync source and in the destination, regardless of case.