How Do Google Drive and iCloud Stay in Sync? Cloud Storage and Conflict Copies

A photo you take on your phone quietly appears on your laptop, and a document you edited at the office is already updated on your home computer. That is sync, the everyday magic of cloud storage services like Google Drive, iCloud, and Dropbox. It feels effortless, but under the hood it is a surprisingly diligent piece of machinery. In this post we will look at how that machinery actually runs, why a mysterious “conflicted copy” file sometimes shows up in your folders, and why “I synced it but my files are gone” accidents happen — all without code.

The basic loop — watch, compare, transfer #

A sync app repeats three steps, over and over.

1. Watch — It keeps an eye on the designated folders and notices when a file is created or changed. It relies on the operating system telling it “something changed in this folder,” so it is not endlessly rummaging through every file.
2. Compare — It checks the state of your device against the state of the server and finds the files that differ. For each file it computes a fingerprint from the contents (a short code that comes out identical for identical contents), so two files with the same name but different contents get caught.
3. Transfer — It uploads or downloads whichever side changed, until both sides match.

There is one clever economy built into this. When you modify only part of a large file, instead of re-uploading the whole thing, the app splits the file into chunks and uploads only the changed chunks. If you fixed just the title metadata of a 1 GB video, re-uploading the full 1 GB would be a waste. This economy is also why only your few new photos upload quickly even when the folder holds hundreds, and why copying the same file into another folder uploads almost instantly — the server already has a chunk with that fingerprint.

Conflicts — when two devices edit at once #

The trickiest moment in sync is when the same file is changed separately in two places. You edit a report on your laptop during a flight, and at the same time a family member edits the same file on the PC at home. When you land and sync, the server receives two different “latest versions.”

Which one should win? The machine has no way to judge the value of either edit. Silently overwriting one side means someone’s work vanishes without a trace. So most services refuse to choose and keep both. One file stays under the original name, and the other is preserved as something like “Report (conflicted copy).docx” or “Report (2).docx.” That puzzling file you occasionally find in a folder is not an error — it is a safety mechanism that refuses to erase anyone’s work. When you run into one, the right move is to open both files and check whose edits should survive before deleting anything.

Tools like Google Docs and Notion, where many people can edit at once without conflicts, work differently. Instead of shipping whole files back and forth, they exchange fine-grained changes in real time — “insert this sentence into the third paragraph” — and merge them. File sync and real-time collaborative editing look similar but are different technologies.

Sync is not backup #

The most common misunderstanding about cloud storage is “it is in the cloud, so it is backed up.” Sync’s whole job is to make every device identical, and that faithfulness applies to deletions too. Delete a folder on your laptop, and sync dutifully propagates the deletion to every device and to the server. If ransomware encrypts your files, the encrypted versions get dutifully synced as well.

Fortunately, most services come with two layers of safety net.

• Trash — Deleted files are kept for a limited period (typically around 30 days). This is your first recovery point after a “sync accident.”
• Version history — Past versions of a file are kept for a while. This is the way back from an overwrite or a bad edit.

Both, however, expire after their retention period, so they are not enough insurance for data you truly cannot afford to lose. The conclusion meets the 3-2-1 rule from the backup post: sync is a convenience mechanism, and a backup is a separate copy that lives outside the sync loop.

Keeping it from eating your disk — selective sync and streaming #

“My laptop has 256 GB but my cloud holds 2 TB — what then?” Two mechanisms answer that question.

• Selective sync — You decide, folder by folder, “do not download this folder to this device.”
• Streaming (on-demand) files — Only the file list lives on your device, and the actual contents are downloaded the moment you open the file. The files with a little cloud icon in Finder or File Explorer are in this state. They take up almost no space day to day, and a double-click triggers a brief download before the file opens.

The trap with streaming files is being offline. If the file you tried to open on the plane had a cloud icon, its contents were never on your device. Once you understand this structure, the habit of marking files “available offline” before a trip becomes second nature.

Wrapping up #

Take apart the magic between your phone and your laptop and it looks like this. Sync is a diligent loop of watching, comparing, and transferring, and large files travel only as their changed chunks. When the same file changes in two places, the machine keeps both as a conflicted copy instead of guessing. And because sync faithfully replicates deletions too, it is no substitute for backup — the trash and version history are safety nets with expiration dates. A cloud icon means the file is not on your device yet, so give it a quick check before you board the plane.