If Google Drive sync in China stops, protect every unsynchronized local file before signing out, disconnecting the account, changing streaming or mirroring mode, clearing data, or reinstalling Drive for desktop. Then identify whether the failure affects the website, desktop process, uploads, downloads, one file, one account, or the current network path. These are different states and require different recovery steps.

Key Takeaways:

Copy irreplaceable local work to a normal, approved folder before destructive recovery.

Distinguish web access from Drive for desktop, and distinguish upload from download.

Read the client's activity and error detail before restarting, disconnecting, or reinstalling.

Verify recovery by comparing a controlled test file on two authorized surfaces.

Public travel guidance reports restrictions on internet access in China, but it cannot diagnose your specific Drive account, client, file, or route.［1］ The broader Google services in China guide covers product-family planning; this article focuses only on Drive synchronization and data preservation.

Which state do you see when Google Drive sync in China fails?

Classify the failure before recovery

Use a small, non-sensitive test file only after preserving real work. Record the last known successful sync, device, account, folder, network, client status, and exact error. Do not assume that a cloud icon means the file contents exist locally.

Observation	First boundary to check	Do not conclude yet
drive.google.com does not load	Browser, DNS, TLS, service, or network path	Desktop files are deleted
Website works but desktop pauses	Desktop process, account, policy, disk, or proxy	The network is fully healthy
Upload is stuck	Local file, permissions, quota, client, or outbound path	Download must also be broken
Download is stuck	Placeholder state, local disk, permissions, or inbound path	The cloud copy is missing
One file fails	Name, type, size, permissions, lock, or corruption	The whole account is unavailable
One account fails	Authentication, administrator policy, storage, or ownership	Every Google account is affected

Google's official Drive for desktop troubleshooting guide treats connection, account disconnection, the “Lost and found” folder, mirroring, streaming, unavailable folders, and reinstalling as distinct cases.［2］ Preserve the evidence needed to know which case applies.

1. Protect unsynchronized local files

Locate files you created or changed since the last confirmed sync. If they open locally, save copies outside the Drive-managed location in an encrypted, approved folder with clear names and timestamps. For shared or regulated data, follow organization policy rather than copying it to a personal device or service.

Streaming mode can leave some entries as online-only placeholders. Do not count a filename or Finder/Explorer entry as an offline copy; confirm that the file opens without fetching and that its size is plausible. Do not delete duplicate-looking files until their content, modification time, owner, and cloud state are understood.

Create a simple inventory with the local path, last edit time, expected cloud folder, and preservation-copy location. For collaborative documents, note whether the item is a native Google document, an uploaded file, or a shortcut: each represents different content and ownership. Keep the inventory private and avoid moving the originals while the queue state is unknown.

2. Is the website, the desktop client, or one sync direction failing?

Check the same authorized account in Drive on the web and in Drive for desktop. Note whether sign-in completes, the intended Shared drive or My Drive location appears, and the client process reports syncing, paused, offline, or an error. Do not use web access alone as proof that local changes uploaded.

Choose one tiny non-sensitive file and give it a unique timestamped name. If policy permits, create it on one surface and observe the other without repeatedly editing it. Record whether the failure is upload-only, download-only, both directions, or limited to a particular folder.

3. Read Drive for desktop activity before restarting

Open the client's activity and error view and capture the affected path and message without exposing private filenames. Confirm that synchronization is not manually paused, battery or metered-network policy is not delaying work, the expected Google account is active, and the client version and operating system remain supported.

If a restart is warranted, close Drive for desktop cleanly and reopen it once. Repeated force-quit cycles can make queues harder to interpret. Do not disconnect the account yet: Google's guidance warns that unsynced content can be moved into the “Lost and found” folder in some recovery paths.［2］

4. Is a file, folder, disk, or placeholder the problem?

Compare a failing file with the controlled test file. Check whether the source file is still open or locked, whether its name or path is unusually long, whether permissions permit reading, and whether antivirus, backup, or another sync client is holding it. Confirm free local disk space and Google storage availability separately.

For streaming mode, verify whether the item was intentionally made available offline. For mirroring mode, confirm that the selected local folder still exists on the expected volume and that an external disk has not been renamed or detached. Do not move the Drive cache or mirrored folder manually while the client is running.

5. Verify account, ownership, and administrator policy

Confirm the account shown in the client is the one that owns or may edit the target. A file can remain visible while edit rights, shared-drive membership, storage capacity, or organizational policy changes. Complete MFA or reauthentication through the official Google flow and never provide a verification code to a third party.

For work or school accounts, ask the administrator whether Drive for desktop is permitted, whether external sharing or offline access changed, and whether the device must meet management requirements. A personal-account result does not override a Workspace policy.

6. Compare the network path without changing the data state

Read errors precisely: name resolution, timeout, TLS, proxy authentication, HTTP response, and account rejection point to different layers. Inspect operating-system and Drive proxy settings without disabling certificate validation or installing an unverified certificate. A captive portal can allow some pages while blocking background synchronization.

If allowed by local law and organization policy, repeat the same tiny-file observation on one controlled alternative path. A VPN can change the route, but it cannot restore a Google incident, add storage, repair a file, grant Shared drive membership, or override Workspace controls. Keep the file, account, client, and time window constant. For that comparison, connect AethoVPN to a nearby location from its in-app list on the same computer, upload the tiny file again and watch whether the sync status moves; start the 3-day AethoVPN trial before you travel so the first run happens on a network you control.

7. Recover progressively and verify convergence

Use the least destructive step supported by the evidence: resume sync, free approved storage, close the locking application, restore a missing mirrored folder, refresh authentication, correct an approved proxy, or ask the administrator to restore policy or membership. Let the queue settle and confirm the original files, not only the test file.

Disconnect or reinstall only after local copies and client evidence are secured and after reading Google's current recovery instructions.［2］ Following recovery, compare the test file's content and modification time on desktop and web, then verify several real files in both upload and download directions. Retain the “Lost and found” folder until every item is reconciled.

If two versions now exist, compare them manually before choosing an authoritative copy. Preserve revision history where available, record who owns the decision, and avoid a bulk overwrite. For a business account, ask the administrator or data owner to approve deletion of recovery copies after the cloud and local inventories agree.

Summary

Preserve unsynchronized local content before changing account or client state.
Separate Drive web access, desktop process, upload, download, and file-specific errors.
Check disk, storage, placeholders, permissions, account, and administrator policy.
Compare one controlled route only after the non-network layers are documented.
Recover progressively and verify content on two authorized surfaces.

FAQ

Does a visible Drive filename prove the file is stored locally?

No. In streaming mode it may be an online-only placeholder. Confirm offline availability and open the file before relying on it as a local backup.

Should I disconnect my Google account immediately?

No. First preserve unsynced work and read the client error. Disconnection can complicate reconciliation and may place content in a recovery folder.

Why does Drive work in a browser but not on desktop?

The desktop client has its own process, cache, proxy, disk, folder, account, and administrator-policy dependencies. Diagnose its activity view separately.

Can low disk space stop only downloads?

Yes. Downloads and offline files require local capacity, while uploads also depend on readable local content and available Google storage. Check both capacities.

What should I do with a stuck local file?

Preserve a copy, close applications that may lock it, inspect its path and permissions, and compare a small test file. Do not repeatedly rename or delete the only copy.

Does reinstalling Drive for desktop delete files?

The outcome depends on streaming or mirroring state and whether changes synchronized. Preserve local work and follow Google's current recovery guidance before reinstalling.

Does a VPN guarantee that Google Drive will sync?

No. Routing is only one layer; service status, account access, storage, file state, desktop health, and administrator policy still govern synchronization.

Disclaimer: This article provides general operational information, not legal, security, data-recovery, employer-policy, or Google-specific support advice. Preserve important data and follow current official and administrator instructions.

Sources

UK Government, China travel advice, internet access and security: https://www.gov.uk/foreign-travel-advice/china/safety-and-security
Google Drive Help, Fix problems in Drive for desktop: https://support.google.com/drive/answer/2565956?hl=en-GB

Sources checked 12 September 2026.

Related reading:

Google Drive Sync in China: What to Check