How Drive Confirms a File Was Actually Deleted (and an Upload Never Silently Lost)
Drive now runs a reconciliation check between its file index and the actual stored bytes — and it deliberately reports drift instead of auto-fixing it.
Two of the most common fears people bring to any cloud storage tool are opposite sides of the same coin: did the file I deleted actually get erased, and did the file I uploaded actually get saved? Both questions come down to whether the system that shows you a list of files agrees with the system that actually holds the bytes. Drive now runs a dedicated check to answer exactly that question — and how it answers matters as much as the fact that it checks.
What it checks
Drive keeps a file index (which file belongs where, who owns it, when it changed) separate from the storage layer that holds the actual bytes. Under normal operation those two systems agree. The new reconciliation process compares them directly and reports four specific kinds of drift: an index entry with no matching stored object, a stored object with no matching index entry, a size mismatch between the two, and folders that have gone empty. Each of these maps to a real-world worry — a delete that didn't fully complete, an upload that got interrupted, a file that was quietly truncated somewhere along the way.
Why it reports instead of auto-repairing
This is the actual news, not the existence of a checker: when Drive finds drift, it does not delete, restore, or otherwise "fix" anything on its own. It reports. That's a deliberate choice, because the two systems can legitimately disagree for a moment without anything being wrong — an upload still in flight, or a listing that was read mid-write. Auto-fixing on a snapshot of a system that hasn't settled yet risks doing the wrong thing with more confidence than the evidence supports.
The stored bytes are treated as the source of truth for what actually exists. An index row pointing at a missing object gets dropped rather than silently kept. An object found in storage with no matching index row gets adopted into the index rather than being flagged as junk and removed. Nothing is ever silently erased in either direction.
If you've ever wondered whether "deleted" really means deleted, or whether an upload that seemed to hang actually made it through, this is the mechanism built to answer that — honestly, and without guessing on your behalf.