Hardware failure gets the attention, and accidental deletion causes more loss. A folder dragged into another folder. A sync client "cleaning up." A bulk selection that included one more item than intended. A well-meaning family member freeing up space.
What makes deletion worse than hardware failure is that it's silent. A dead drive announces itself. A deleted folder looks exactly like a folder you moved somewhere sensible, and you find out months later, after every recovery window has closed.
The seven ways files actually disappear
1. The accidental drag. Folders get dropped into adjacent folders during scrolling. The file isn't deleted, it's displaced, and it's effectively lost because you'll never think to look there.
2. Select-all overreach. You select a group to delete and one extra item is included. Bulk operations are where single mistakes become large ones.
3. Freeing up space. Someone deletes to make room — often on a synced folder, which removes it everywhere. This is the most common cause of family photo loss.
4. Cleanup tools. Utilities that remove "unnecessary" files, using criteria that don't match yours.
5. Sync misconfiguration. Pointing a sync tool at the wrong folder, or setting up one-way sync in the wrong direction, can mirror an empty folder over a full one.
6. Someone else. A shared drive with edit access is a drive anyone can empty. Contractors, colleagues, family members, all acting reasonably.
7. Application behaviour. Uninstalling software that removes its data folder, an import that moves rather than copies, a migration that cleans up after itself.
Note how few of these are careless. Most are ordinary actions with an unintended scope.
Structural protection: make it hard to touch the wrong thing
Separate active from archived. Finished work moves to an archive folder, and that folder is set read-only. You can't accidentally delete what you can't write to.
On any operating system, you can set a folder to read-only for your normal user account. On a shared drive, set archived material to view-only for everyone who doesn't need to change it.
Keep the irreplaceable somewhere separate from the disposable. Photos and financial records shouldn't share a parent folder with downloads and temporary exports. Bulk operations in a folder of junk shouldn't be able to catch anything important.
Don't nest important folders inside high-churn ones. A folder inside Downloads will eventually be cleaned up by someone clearing Downloads.
Use consistent, obvious names. A folder called Final next to a folder called Old invites a mistaken deletion. 2024 CLIENT WORK — KEEP does not.
Permissions: the strongest protection on shared drives
If more than one person has access, permissions do more than habits.
Give view access by default, edit access deliberately. Most people need to read most things and change few of them.
Turn off deletion rights where the platform allows it. Some systems distinguish between editing and deleting.
Restrict the top level. Only one or two people should be able to create, rename, or remove top-level folders.
Set archives read-only for everyone.
For business drives, check whether your platform has a retention or holds policy — some prevent permanent deletion for a defined period regardless of what a user does. This is the strongest available protection and it's often available on plans people are already paying for.
The safety nets, and their limits
Trash and recycle bins. The first line, and time-limited. Cloud services purge after a retention period; local bins get emptied. Don't empty a trash without looking at it.
Version history. Recovers overwritten and damaged files, and sometimes deleted ones. Retention varies.
Snapshots. Some file systems and network drives take periodic read-only snapshots you can browse and restore from. Excellent when available — a snapshot from yesterday morning contains yesterday morning's folder.
Backups with history. The real protection, because retention is measured in months or years rather than days, and because it's outside the account.
Offline copies. Immune to anything happening on the live system.
The pattern: each net catches a shorter or longer window. Trash catches days, version history catches weeks, backups catch months. The only one that catches "I noticed in November that it went missing in March" is a backup with long retention.
Noticing faster, which matters most
Every recovery route is time-boxed, so the variable that determines outcomes isn't which safety net you have — it's how quickly you notice.
Check folder sizes periodically. Your photo folder should get bigger. If it's smaller than last quarter, something happened. This takes seconds and it's the single most effective detection method.
Watch for surprises in the trash. If you open your cloud trash and there's something in it you don't remember deleting, that's information.
Keep a manifest of important folders. A text file listing what should be there:
PHOTOS — should contain year folders 1998 through 2025
plus SCANNED-FAMILY and VIDEO
Approx 340 GB as of 2025-04-08Ten seconds to check against, and it catches a missing year folder that browsing wouldn't.
Enable notifications on shared drives. Most platforms can alert you to bulk deletions or changes in shared folders.
Look at your backup's reported size. A backup that suddenly got much smaller is telling you something was deleted from the source.
Behavioural habits that prevent it
Never delete during cleanup — move to a staging folder first. Create _TO DELETE, move things there, and empty it in a month. This converts an irreversible action into a reversible one, and it costs nothing.
Pause before bulk operations. Before deleting a selection, look at the count. "Delete 1,247 items" when you expected 12 is the moment to stop.
Don't clean up when tired or rushed. Nearly every large accidental deletion happens during a hurried tidy-up.
Disable "delete immediately" shortcuts where possible, so deletions go to the bin.
Never point a sync tool at a folder without checking the direction. Read the confirmation dialog, especially any that mention removing files at the destination.
Copy, then verify, then delete. When moving files between drives, copy first, confirm the destination is complete and openable, and only then remove the source. Move operations that fail partway are how folders end up half-missing.
For shared and family situations
Explain the sync behaviour. The person deleting photos from a phone to free up space usually doesn't know it deletes them from the cloud and from everyone else's devices. Saying it once prevents it.
Keep a family archive that syncs one-way. The curated collection lives in a folder that receives copies but isn't the working library, so deletions in the working library don't reach it.
Give family members their own space rather than everyone working in one shared area.
Keep one copy that nobody but you can write to.
If it just happened
- Stop. Don't do anything else in that folder.
- Check the trash on the cloud service and locally.
- Check whether it was moved rather than deleted — search by name.
- Check other devices, especially any that have been offline. Disconnect one from the network if you find a copy, and copy the files out before letting it sync.
- Check version history and snapshots.
- Check your backup, and the off-site copy.
- On a work account, ask an administrator — their recovery options exceed yours.
Speed matters at every step.
The realistic minimum
If you do three things:
- A backup with long retention, so a loss discovered in six months is still recoverable.
- Read-only archives, so finished work can't be touched.
- A quarterly size check on your important folders, so you notice within months rather than years.
The third one is free and it's the one nobody does. Every recovery method in this article works fine — as long as somebody notices in time.
Next in this series: A Complete Backup Audit Checklist for Home and Business