Google Drive, Dropbox, and iCloud are sync services. They mirror what's on your Mac to a server. Delete a file on your Mac, and the sync engine deletes it in the cloud. Overwrite a project folder, and the overwrite propagates. That's the opposite of what backup does.
Backup keeps independent copies that don't change when you change the original. Cloud storage keeps one copy that changes with you. The distinction sounds academic until you lose a year of work because you trusted a sync folder.
TL;DR: Sync propagates changes and deletions. Backup keeps independent copies. Five real cases below show what happens when creators treat Google Drive, Dropbox, or iCloud as their only safety net. Use cloud as one layer in a 3-2-1 setup, not the whole system.
Sync vs Backup: What's the Actual Difference?
Sync (Google Drive, Dropbox, iCloud Drive, OneDrive): one copy in two places that stay identical. Change locally, change in the cloud. Delete locally, delete in the cloud. A ransomware attack that encrypts your files can encrypt the synced cloud copy too, depending on timing.
Backup (Backblaze, Arq, Time Machine, Tusk to multiple destinations): independent copies at a point in time. Change or delete the original, the backup copy from yesterday still exists. Restore means pulling back an older version, not hoping the sync didn't propagate the damage.
Both are useful. Sync is for access and collaboration. Backup is for recovery. The problem is treating one as the other.
The 3-2-1 backup rule puts cloud in its place: one offsite layer alongside local copies, not the whole system. The best cloud backup guide covers services that actually back up (Backblaze, iDrive, Arq), not sync folders. This article covers what goes wrong when you skip them and treat Drive or Dropbox as your only safety net.
Case 1: Google Account Suspension Locks Out Everything
What happened: Google disables an entire account for a Terms of Service violation. Gmail, Google Drive, Google Photos, YouTube, and every other Google service become inaccessible simultaneously.
Why it matters for creators: Your Google account is not just email. If you store client deliverables in Drive, portfolio images in Photos, and contracts in Gmail, a single suspension takes all of it at once. Google's account recovery process makes clear that reinstatement isn't guaranteed: if an appeal is denied, access can be lost permanently.
A documented case: In 2021, a stay-at-home dad in San Francisco (identified in reporting only as Mark) lost his entire Google account after Google's automated systems flagged a medical photo of his toddler, taken at a doctor's request, as child sexual abuse material. As The Verge reported, he lost more than a decade of Gmail, his Google Photos library, Drive files, and his Google Fi phone number. Police investigated and cleared him of any wrongdoing, but Google still refused to reinstate the account, even after the error was clear. The trigger was an automated content flag, not a billing or login issue, which is exactly why putting everything behind one account is so risky.
The lesson: A Google account is a single point of failure. If Drive is your only copy of client work, an account issue is a business-ending event. Keep independent copies on local drives that don't require a Google login to access.
Case 2: Dropbox Sync Propagates a Deletion You Didn't Mean
What happened: A user deletes a folder locally, thinking Dropbox keeps a cloud copy. Dropbox syncs the deletion. The folder is gone from the cloud too. Dropbox keeps deleted files for 30 days (180 days on some business plans), but after that window, recovery is impossible.
Why this is common: The mental model is "my files are in Dropbox, so they're safe." But Dropbox is a mirror, not an archive. The Dropbox help center confirms: deleting locally removes the file from all synced devices and from dropbox.com. Recovery is only available within the retention window.
Documented pattern on r/DataHoarder and r/photography: Posts appear regularly from users who deleted a local copy to free up Mac storage, assuming Dropbox was their backup. They discover weeks later that the "backup" was a sync mirror and the deletion propagated. For large video project folders (100GB+), the 30-day recovery window becomes a ticking clock they don't know is running.
The lesson: Before you delete local files to free up space, verify you have an independent backup copy on separate media. Not a sync folder. A real backup. Tools that run a preflight check (verifying each file exists on every backup destination) exist specifically because this mistake is so common.
Case 3: iCloud Drive Silently Removes Local Copies
What happened: macOS iCloud Drive's "Optimize Mac Storage" feature removes local copies of files when disk space is low, keeping only the iCloud version. If something goes wrong with the iCloud copy (account issue, sync bug, accidental deletion from another device), the local copy is already gone.
Apple's own documentation: Optimize Mac Storage uploads files to iCloud and removes the local copy when space is needed. The file shows in Finder with a cloud icon. It's not on your disk.
Why it matters for photographers: A Lightroom catalog or RAW folder that macOS offloads to iCloud is no longer on your local drive. If iCloud has a sync conflict, an account lockout, or you accidentally delete from iCloud.com, the files are gone. Lightroom shows missing files. The catalog points to paths that no longer resolve locally.
The lesson: Turn off "Optimize Mac Storage" for machines that hold active project files. Keep local copies on fast drives. Use iCloud for documents and small files, not for terabytes of RAW footage.
Case 4: Google Drive Desktop Sync Bug Deletes Months of Files
What happened: In November 2023, a bug in Google Drive for desktop (versions 84.0.0.0 through 84.0.4.0) caused files to disappear for a subset of users. According to The Verge one user lost all Drive data going back to May. Over 190 users flagged the same issue on Google's support forum.
Google's response: Google acknowledged a sync issue affecting "a limited subset" of desktop users and released a recovery tool in version 85.0.13.0. The fix was not a one-click update, and Google itself cautioned that the recovery tool would not work for everyone. Some users ran the full procedure and still couldn't get their files back.
Why it matters: This is a sync service deleting files on both sides. A proper backup would still have yesterday's copy on an external drive. Users who treated Drive as their backup had no fallback when the recovery tool failed.
Case 5: Ransomware Encrypts the Synced Copy Too
What happened: Ransomware encrypts files on a user's Mac. Dropbox or Google Drive syncs the encrypted versions to the cloud, overwriting the good copies. The user now has encrypted files locally and in the cloud.
Why this is worse than no cloud: Without cloud sync, ransomware only hits the local copy. Your external backup drive (if disconnected) is safe. With cloud sync running, the ransomware damage uploads before you notice.
Documented pattern: Security researchers and backup vendors document this regularly. Sync-based cloud storage is vulnerable to ransomware in a way that disconnected backup drives and point-in-time backup services (Backblaze, Arq with version history) are not.
The lesson: Backup destinations should not be continuously synced mirrors of your working files. At least one copy should be on media that isn't actively mirroring changes. A NAS snapshot helps. A disconnected external drive helps more. A cloud backup service with version history helps most.
What to Do Instead
The 3-2-1 backup rule hasn't changed:
- Three copies of your data
- Two different media types (SSD + HDD, or local + cloud)
- One offsite (cloud backup service or a drive at another location)
Cloud storage (Drive, Dropbox, iCloud) can be one of the three copies if you treat it as sync for access, not as your safety net. Your safety net is a backup service (Backblaze, iDrive, Arq) or a verified copy on an external drive that doesn't mirror deletions.
For creative project workflows on Mac:
- Working copy: local SSD
- Backup copy 1: external drive with verified transfers
- Backup copy 2: cloud backup service (not cloud sync)
- Optional: cloud sync for collaboration and remote access (treat it as a working mirror, not a backup)
The best external drives guide covers local hardware. The cloud backup comparison covers offsite services.
Tusk sits in the local backup layer: it watches your project folders, verifies every transfer with BLAKE3 checksums, tracks files across multiple drives (even disconnected ones), and won't let you delete local copies until every backup destination confirms the file is safe. It's not a cloud service. It's the tool that makes your local copies trustworthy enough to rely on.
FAQ
No. Google Drive is a sync service. It mirrors files between your Mac and Google's servers. Delete a file locally and it deletes in Drive. Overwrite a folder and the overwrite syncs. Google's own account recovery documentation warns that suspended accounts may be permanently deleted along with all Drive data. For backup, use a service that keeps independent point-in-time copies (Backblaze, iDrive, Arq) alongside Drive for sync and collaboration.
Cloud storage (Google Drive, Dropbox, iCloud, OneDrive) syncs files between your device and the cloud. One copy in two places that stay identical. Cloud backup (Backblaze, iDrive, Arq) creates independent copies that don't change when you change the original. Delete a file locally and a sync service deletes it in the cloud. A backup service keeps the old copy available for restore. Both are useful for different purposes. The mistake is using sync as backup.
Yes, within a retention window. Dropbox keeps deleted files for 30 days on free and Plus plans, and up to 180 days on Business plans. After that window, deletion is permanent. This is file recovery within a sync service, not backup. If you need long-term retention of every version of every file, use a backup service with version history (Arq keeps all versions) or maintain independent copies on external drives.
Yes, if your Mac holds active project files (Lightroom catalogs, RAW folders, video projects). Optimize Mac Storage removes local copies when disk space is low, keeping only the iCloud version. If the iCloud copy has a problem, your local copy is already gone. Keep project files on local SSDs with independent backup. iCloud is fine for documents, small files, and non-critical data.
Don't make Google your only copy. Maintain independent backups on local external drives and a non-Google cloud backup service (Backblaze, iDrive). Use Google Takeout (takeout.google.com) to export data periodically, and deliver exports to non-Google destinations (Dropbox, OneDrive, local drives). If your Google account is suspended, Takeout access may also be blocked depending on the violation type. Independent copies you control are the only reliable protection.