April 14, 2026
Backup or backstab?
Backblaze has stopped backing up your data
“Unlimited backup” hype? Users say Backblaze just hit delete on trust
TLDR: Backblaze stopped backing up OneDrive/Dropbox folders and some hidden data, despite its “we back up everything” image. Users exploded—some call it enshittification and a bait‑and‑switch, others blame technical quirks but slam the silence—reviving the mantra that sync isn’t backup and trust is what’s really lost.
Backblaze, the “we back up everything” darling, just sparked a comment-section riot after users found it quietly stopped backing up OneDrive and Dropbox folders—and even hidden coding history folders like .git. Long-time fans felt blindsided: they trusted this for years, and now key folders are simply off the list with little warning. The mood? Betrayal meets buyer’s remorse.
The hottest take: this is classic bait-and-switch. One commenter raged that services love fast progress bars and “unlimited” promises, then quietly carve out exceptions. Another called the stealthy .git exclusion “scandalous,” while a fresh-faced shopper summed it up with one word: enshittification—the slow decay from great service to gotchas.
Not everyone sees malice. A calmer voice said OneDrive folders can be chaotic—metadata churn, weird loops—so excluding them might be a practical fix. But even the reasonable crowd torched the communication: if you’re pulling files from coverage, say it loudly, not in dusty release notes.
Humor flew, painfully: “Unlimited* (*until it isn’t),” “Sync ≠ Backup,” and “Backblaze? More like Backbail.” Veterans reminded everyone that syncing apps aren’t safes—deleted files may vanish after a month, while backups hold versions for longer. The final vibe: if your safety net has secret holes, is it still a safety net?
Key Points
- •The author reports Backblaze no longer backs up certain sync service folders, discovering their OneDrive folder missing and citing a thread about Dropbox folders.
- •Backblaze was also found to ignore .git directories, preventing restoration of repository history after a GitHub forced push.
- •These exclusions were not shown or configurable in Backblaze’s preferences according to the author.
- •The author had previously validated Backblaze with a successful full restore via a shipped hard drive and used the service since 2015.
- •The article argues that sync services (OneDrive/Dropbox) have limited retention, while Backblaze offers longer retention, making sync an inadequate backup substitute.