Troubleshooting “Zero byte” files that won’t delete

Attempting to delete a zero-byte (0 KB or 0 B) file in Google Drive often results in errors like “An error occurred while deleting,” “Item not found,” or the file appears to delete only to return immediately after refreshing the page. These stuck 0-byte files occur when an upload was interrupted mid-stream, leaving an incomplete metadata record on Google’s backend, or when a local operating system process holds a persistent lock on a temporary file synced through Google Drive for Desktop.

Quick Answer

Zero-byte files that refuse to delete are usually stuck sync locks or broken metadata pointers. To delete them, fully quit Google Drive for Desktop, open Google Drive in an Incognito browser window, move the file into a new temporary folder, and delete the entire folder. Alternatively, delete the item via the Drive API using its File ID.

---

Why 0-Byte Files Refuse to Delete

A 0-byte file contains a file name and metadata attributes, but zero bytes of binary data. These items become stuck in Google Drive due to three main causes:

1. Incomplete API Upload Handshakes: When an application or backup script begins a “resumable upload” to Google Drive, the API first generates a file resource record (the metadata entry). If the network drops before the actual data chunks are uploaded, Google’s database is left holding a hollow, zero-byte file pointer that can fail standard web interface validation checks.
2. Persistent Lock Files from Desktop Software: Applications like Microsoft Office and Adobe create hidden temporary lock files (e.g., ~$Document.docx or .tmp files) that register as 0 bytes. If Google Drive for Desktop syncs this temporary pointer to the cloud while the desktop program is still open, the operating system locks the file, blocking delete requests.
3. Local Cache Database Desynchronization: Google Drive for Desktop maintains a local SQLite database that mirrors your cloud files. If this local cache database becomes corrupted, File Explorer or Finder will continuously attempt to re-sync a phantom 0-byte file that no longer exists on Google’s servers.

---

Step 1: Break the Local Sync Lock

If you use Google Drive for Desktop, local application handles are the most common reason zero-byte files cannot be deleted.

1. Locate the Google Drive icon in your Windows system tray or macOS menu bar.
2. Click the Settings gear and select Quit (or Exit).
3. Close all running desktop programs (especially Microsoft Word, Excel, PowerPoint, and Adobe apps).
4. Re-open File Explorer or Finder, navigate to the local drive directory where the 0-byte file was located, and attempt to delete it.
5. If the file deletes cleanly while Drive for Desktop is closed, the issue was an active OS process lock. Restart Drive for Desktop; it will sync the deletion to the cloud without error.

If your local desktop client throws permissions errors during this process, review Fixing “Can’t sync [Filename]: Access denied” local errors.

---

Step 2: Delete via Web Browser in Incognito Mode

If the 0-byte file reappears every time you refresh your browser, your local browser cache is likely serving stale session data.

1. Open Google Chrome and launch a new Incognito Window (or private browsing session).
2. Go to drive.google.com and log into your Google account.
3. Locate the zero-byte file.
4. Select the file, press the Delete key (or click the Trash icon).
5. Immediately navigate to the Trash in the left sidebar and click Empty trash.
6. Refresh the page. If the file does not return, your standard browser cache was displaying a ghost listing. Clear your browser cookies and site data to resolve it in your standard window.

---

Step 3: The “Parent Folder Move” Bypass

When Google Drive’s database returns an error trying to delete a single damaged metadata record, you can often bypass the item-level lock by performing a recursive folder deletion:

1. In the Google Drive web interface, create a new folder named Temporary_Purge.
2. Drag or move the stubborn 0-byte file into Temporary_Purge.
3. Right-click the Temporary_Purge folder and select Move to trash.
4. Go to Trash and click Empty trash.

Google Drive uses a different backend deletion routine when purging parent directories than it does when modifying single items. This method successfully forces Google’s storage database to remove broken metadata child pointers.

---

Step 4: Clear Corrupted Local DriveFS Cache Files

If the zero-byte file is completely gone from the Google Drive web interface, but refuses to disappear from your computer’s local File Explorer or Finder, your local DriveFS database is corrupted.

To resolve this:

1. Quit Google Drive for Desktop.
2. Follow the detailed steps in How to Clear Google Drive Local Cached Files Safely to clear out the temporary content cache directory without losing unsynced edits.
3. Relaunch Google Drive for Desktop. The client will pull a clean metadata mirror directly from Google’s cloud servers, eliminating the phantom 0-byte listing.

---

Step 5: Force Deletion via the Drive API / GAM

If you are an administrator and a zero-byte file cannot be moved, renamed, or deleted via the web interface, you can delete the item directly using its unique File ID through the Google Drive API.

1. Open the stuck file in Google Drive (or preview its details).
2. Look at the browser URL bar:
   https://drive.google.com/file/d/1A2B3C4D5E6F7G8H9I0J/view
3. Copy the alphanumeric string between /d/ and /view. This is the File ID.
4. Open your command line and run a purge command using GAM (Google Apps Manager):(The purge parameter instructs Google to permanently destroy the metadata record immediately, bypassing the trash bin). gam user user@yourdomain.com delete drivefile id <FileID> purge

gam user user@yourdomain.com delete drivefile id <FileID> purge

If you suspect other phantom files are lingering across your account and affecting your total storage balance, consult How to Find “Ghost Files” taking up space in Drive and Drive says “Storage Full” but I deleted everything.