Uploading files to Google Drive through your browser or the desktop client is generally smooth, but encountering an alert stating “Upload incomplete”—or discovering that an uploaded video, ZIP archive, or document shows a file size of 0 bytes (empty file)—is an alarming roadblock. Opening the file yields an error stating “No preview available”, while downloading it results in a blank, corrupted document. When Google Drive flags uploads as incomplete or writes zero-byte placeholders, it does not mean your original local file is damaged; rather, it indicates network packet timeouts, browser chunking interruptions, or third-party web filtering blocks.
Disable Chrome Hardware Acceleration and Background Throttling
Google Drive’s web interface uses HTML5 File API chunking to upload large files in small 8 MB or 16 MB binary blocks. If your browser freezes or aggressively suspends background tabs to conserve battery, the upload socket terminates mid-transfer, leaving an empty zero-byte stub on the server.
- In Google Chrome, click the three vertical dots in the upper-right corner and select Settings.
- In the left-hand column, click on Performance.
- Under the Memory Saver section, locate the heading Always keep these sites active.
- Click Add, enter
https://drive.google.com, and click Add. - This ensures Chrome never suspends or throttles the Google Drive browser tab even if you switch away to another application while uploading.
Preventing background tab throttling guarantees that data streams continue transferring until final checksum confirmation.
Clear Chrome Socket Pools via Internal Flags
If your internet connection experienced a momentary Wi-Fi stutter during an upload, Chrome can hold onto stale TCP sockets that continuously reject subsequent data packets, producing incomplete uploads.
- Open a new tab in Google Chrome.
- Type
chrome://net-internals/#socketsinto the address bar and press Enter. - Click the button labelled Flush socket pools.
- Close the tab, return to Google Drive, delete the broken 0-byte file from your cloud folder, and re-upload the file.
Flushing socket pools purges hung socket connections and opens clean, high-speed TCP streams for file transfers.
Upload in an Incognito Window to Avoid Extension Interference
Antivirus browser shields, ad blockers, and VPN web extensions inspect outgoing encrypted traffic. When transferring large files, these extensions can time out while inspecting binary streams, severing the upload payload before completion.
- Press Ctrl + Shift + N (or Command + Shift + N on Mac) to launch an Incognito window.
- Log into your Google Account and open Google Drive.
- Drag and drop your file into the destination folder.
- If the upload completes cleanly with its full, accurate megabyte size, a third-party extension in your normal browser profile was interrupting outgoing packets.
Incognito mode isolates the upload pipeline from external script modifications, ensuring intact file transmission.
Switch from Desktop Sync to Direct Web Upload (or Vice Versa)
If you encounter zero-byte files while using Google Drive for Desktop, local file-locking mechanisms (such as Windows antivirus actively scanning the file while Drive attempts to upload) can cause the desktop client to sync an empty shell.
- Open your web browser and navigate directly to
drive.google.com. - Click the + New button in the upper-left corner and choose File upload.
- Select your file directly from your local drive.
- Alternatively, if large files fail repeatedly in the browser due to bandwidth limits, use the official Google Drive for Desktop client, which supports automatic block-level resume capabilities.
Switching transfer methods bypasses software-specific upload bottlenecks and completes your cloud backup reliably.