Fixing Sync Slowdowns: Bandwidth Throttling Diagnostics

When Google Drive for Desktop experiences severe sync slowdowns, transfers can crawl to a near standstill, showing estimated completion times of hours or days for moderate workloads. This performance bottleneck usually points to misconfigured client-side bandwidth limits, Quality of Service (QoS) throttling on corporate firewalls, local antivirus deep packet inspection, or Google API concurrency rate-limiting during massive small-file uploads.

Fast Fix

Open Google Drive Settings (gear icon) > Preferences > inner Settings gear. Scroll down to Bandwidth settings and verify that both Download rate and Upload rate are set to Don’t limit. If limits are already off, restart the client to clear hung socket threads, or temporarily disable local antivirus web shield inspection.

Diagnostic Snapshot

Parameter	Specification
Affected Applications	Google Drive for Desktop (Windows & macOS)
Primary Symptom	Transfer speeds locked at very low KB/s rates; prolonged “Syncing X of Y items” with minimal network utilization
Root Conflict Layers	Client rate ceilings, network QoS / deep packet inspection (DPI), proxy latency, or Google Drive API per-user IOPS throttling
Admin Access Required	No for client-level bandwidth adjustments; Yes if modifying enterprise registry keys, proxy firewalls, or Google Admin policies

What This Means: System Mechanics

Google Drive for Desktop transfers data over encrypted HTTPS/TLS connections across ports 80 and 443. The sync engine handles transfers using two distinct mechanisms:

1. Chunked Block Streaming: Large files are sliced into binary blocks and uploaded using parallel data streams to Google Workspace storage nodes.
2. Metadata API Calls: Every new file, folder creation, timestamp modification, or permission change requires a distinct REST API transaction against Google servers.

When a sync operation involves thousands of tiny files (such as source code repositories, application caches, or web assets), total throughput drops significantly. Even on a gigabit connection, each file requires its own TLS handshake, metadata write, and database record update in %LOCALAPPDATA%\Google\DriveFS. If your network uses deep packet inspection or proxy filters that intercept every HTTPS payload, the overhead multiplies, causing the client to crawl.

Common Causes

• Explicit Bandwidth Caps: Hard rate limits accidentally enabled in the application settings or enforced silently across an organization through Windows Registry or Group Policy values.
• Antivirus File & Network Scanning: Endpoint security software intercepting every file chunk as it writes to the local cache directory.
• Small-File Metadata Congestion: Uploading large directory trees containing thousands of .tmp, .git, or cache files. To diagnose temporary file buildup
• Local Disk IOPS Saturation: Running sync operations on an overloaded mechanical hard drive or an encrypted volume with high I/O wait times. If storage alerts accompany the slowdown

Resolution Steps

Step 1: Remove Application Bandwidth Restrictions

1. Click the Google Drive icon in your taskbar or menu bar.
2. Click the Settings gear > Preferences.
3. Click the inner Settings gear (top-right corner).
4. Scroll down to Bandwidth settings.
5. Set both Download rate and Upload rate to Don’t limit.
6. Click Save and select Restart now.

Google Drive Preferences
└── Settings (Gear Icon)
    └── Bandwidth Settings
        ├── Download rate: [•] Don't limit
        └── Upload rate:   [•] Don't limit

Step 2: Configure Antivirus Scan Exclusions

Prevent local security suites from inspecting every active sync payload:

1. Open your endpoint protection console (e.g., Windows Defender, CrowdStrike, or SentinelOne).
2. Add a path exclusion for the local Drive cache:
   • Windows: %LOCALAPPDATA%\Google\DriveFS
   • macOS: ~/Library/Application Support/Google/DriveFS
3. Add a process exclusion for GoogleDriveFS.exe.
4. Ensure your firewall rules do not restrict Drive traffic

Step 3: Isolate Small-File Floods and Archive First

If you are syncing projects with massive directory structures (such as node_modules, build artifacts, or raw datasets):

1. Pause syncing from the Google Drive menu.
2. Compress the target folder into a .zip or .tar.gz archive.
3. Sync the single compressed archive rather than loose folders. A single 5 GB archive uploads at wire speed, whereas 50,000 loose files totaling 5 GB will crawl due to per-file API limits.

Step 4: Bypass Proxy and VPN Tunnels for Testing

1. Temporarily disconnect from third-party VPNs or enterprise split-tunnel connections.
2. If sync speeds jump immediately to normal line rates, add bypass rules for .google.com, .googleapis.com, and .gstatic.com in your VPN client or corporate PAC proxy script.

Hard Stops

• Corporate Network Policy Overrides: If your organization’s network operations team enforces upstream traffic shaping (such as router-level QoS prioritizing VoIP or video over cloud storage), do not attempt to bypass network controls with unauthorized proxy tunnels or third-party wrappers. Work directly with your network engineering team to classify Google Workspace endpoints under high-priority business traffic.