Renaming a file modifies its metadata (information about the file, like its name) rather than changing the file's actual content data. Backup and sync systems track both content changes and metadata changes. They need to maintain an accurate mirror of your source filesystem, including all the files present and their correct names. Simply changing the name is a significant event to these systems because it alters which file path points to the existing content on both the source and the destination.

For example, cloud sync services like Dropbox or Google Drive detect a rename operation to ensure the renamed file correctly appears at the new name across all your linked devices and in the cloud version. Similarly, a version control system like Git will see a file rename as a tracked change that needs to be committed, preserving the history of when the name changed relative to other modifications.

This behavior ensures system integrity, preserving historical records and ensuring files remain findable under their new name everywhere. However, it can cause unintended large uploads/downloads if systems misinterpret renames as deletions plus creations. Smart systems minimize this by efficiently handling metadata-only changes, making the process seamless for users while maintaining reliability across devices and services.