Provider differences
Every cloud service and file protocol works a little differently. Most "why did this happen?" questions about syncing come down to one of the differences below. For the details of a single service, see its page under Accounts in the FAQ.
Why are files transferred again, or shown as changed?
FolderSync decides whether a file has changed by comparing size, modification time and, when the service provides one, a checksum. How reliable this is depends on the service:
- Modification time: some services keep the original modification time of uploaded files. Others set the time of the upload instead, so the remote file always looks newer than the local one. FolderSync takes this into account, but on the very first sync of a new folderPair it can only compare sizes for these services.
- Checksum: services that provide an MD5 or SHA1 checksum (for example Google Drive, OneDrive, Box and Immich) let FolderSync see that two files are identical even if their times differ.
The Supported services table shows which services keep modification times and which provide checksums. See also Sync issues for daylight saving time changes and conflicts.
Upper and lower case in names (Photo.jpg vs photo.jpg)
FolderSync matches files and folders by their exact name, including upper and lower case, so Photo.jpg and photo.jpg are two different files to FolderSync.
Many services and file systems treat them as the same name, for example:
- OneDrive, SharePoint, Dropbox and Box
- SMB shares on Windows and most NAS devices
- Windows and macOS computers (FolderSync Desktop)
Others treat them as different names, for example Amazon S3 and other S3-compatible storage, MinIO, Google Cloud Storage, and SFTP/FTP servers running Linux.
When only the case differs between the local and remote name, you can see errors such as a folder that can't be created because it "already exists", or files that are transferred again or appear twice. The fix is to rename the file or folder on one side so the names match exactly.
Duplicate names on Google Drive
Google Drive allows several files with exactly the same name in one folder. FolderSync can only sync one of them. Rename duplicates so every name in a folder is unique.
Which file and folder names are not allowed?
Each service has its own rules. When a name isn't allowed on the target, FolderSync skips the item and shows the reason in the sync log (see Skipped items).
| Service | Not allowed |
|---|---|
| OneDrive, SharePoint | Names ending with a dot, starting with .., or starting or ending with a space. SharePoint also blocks " * : < > ? / \ \|, names starting with ~$ or containing _vti_, and reserved names. See SharePoint |
| SMB (Windows, NAS) | \ / " : < > \| * ?, and on many servers names ending with a dot. See SMB |
| Windows computers (Desktop) | \ / : * ? " < > \|, names ending with a space or dot, and reserved names like CON, PRN, AUX, NUL, COM1 and LPT1 |
| SD cards formatted as FAT32 | < > : " / \ \| ? * |
| Box | Names longer than 255 characters, leading or trailing spaces, / or \, and the names . and .. |
| Most file systems | Names longer than 255 characters (or bytes) |
Some services also limit file size. For example, HiDrive allows at most 2 GB per file, and Box limits uploads according to your Box plan.
What happens to deleted files?
When a sync deletes a file, the service decides whether it can be restored:
| Moved to the service's trash or recycle bin | Deleted permanently |
|---|---|
| Google Drive (unless Use recycle bin is turned off on the account) | FTP and SFTP |
| MEGA (unless Use recycle bin is turned off on the account) | SMB |
| OneDrive and SharePoint | Amazon S3, S3-compatible storage, MinIO and Google Cloud Storage (unless versioning is enabled on the bucket) |
| Dropbox, Box, pCloud, Yandex Disk | Android device storage |
| kDrive, Proton Drive, Filen, Drime, Zoho WorkDrive | |
| Immich (see Immich) | |
| Desktop computers (system trash, where supported) |
For WebDAV, Nextcloud and ownCloud it depends on the server. Nextcloud and ownCloud move deleted files to their trash bin when the trash bin app is enabled.
Sync deletion
Deleting files is only done when deletion is enabled on the folderPair. FolderSync only deletes files it has synced before. Files in the target folder that FolderSync never synced are reported as conflicts instead of deleted (see Sync issues).
"Too many requests", "Rate limit" or "Quota exceeded" errors
Most cloud services limit how many requests an app can make in a short time. When the limit is hit, the service answers with errors like "429 Too Many Requests", "Rate limit exceeded" or "Quota exceeded". FolderSync automatically waits and retries these requests, but a sync can still fail if the limit is hit repeatedly.
To avoid this:
- Lower Simultaneous transfers in the app settings, so fewer files are transferred at the same time.
- Don't schedule syncs on the hour (for example 12:00). Many users do, so services are busiest then. Pick a random minute like 12:17.
- Spread large folderPairs over different times instead of running them all at once.
For Google Drive, see also "Quota exceeded" errors.