Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


When Dropbox sync in China stops, do not interpret a stale icon, missing file on one device, or incomplete website load as proof that data was deleted. Preserve local changes, compare dropbox.com with the desktop app and one other trusted device, then classify the failing direction and scope. Upload, download, selective sync, file locks, names, disk capacity, team policy, and the network path can produce similar symptoms.
Key Takeaways:
- Copy irreplaceable unsynchronized work to an approved location before unlinking or reinstalling.
- Compare the website, desktop sync status, and another trusted device without making simultaneous edits.
- Distinguish upload from download and one-file faults from account-wide faults.
- Verify recovery using content and timestamps, not only a green icon.
Public travel guidance describes restrictions on internet access in China, but a general observation cannot identify your Dropbox account, file, device, or route.[1] For a platform-neutral fault tree, see apps and websites not working in mainland China; this guide stays with Dropbox synchronization.
Record the last confirmed good version, device, path, account, network, and exact status. Pause editing the affected document while you compare it. Use a tiny non-sensitive file for testing only after protecting real work.
| Observation | Likely boundary to inspect first | What it does not prove |
|---|---|---|
| Website unavailable | Browser, DNS, TLS, service, or network path | Desktop copies are gone |
| Website current, desktop stale | Desktop process, account, selective sync, disk, or proxy | Cloud data is damaged |
| Desktop A current, device B stale | Device B client, download path, disk, or account | Upload from A failed |
| One upload fails | File lock, name, permissions, size, or local read error | All uploads fail |
| Folder absent locally | Selective sync, online-only state, team membership, or path | Folder was deleted globally |
| Sync status never settles | Queue, index, storage, file churn, or network instability | Data has already been lost |
Dropbox's official troubleshooting guide separates application state, network settings, file compatibility, selective sync, symbolic links, permissions, storage, and account issues.[2] Its status guide also explains that icon and menu wording differ by operating system and state.[3] Read the actual detail rather than relying on icon color alone.
Identify files edited since the last confirmed sync and save copies outside the Dropbox-managed folder in an encrypted, policy-approved location. Keep filenames, timestamps, and a short note about which version is authoritative. Do not upload company material to a personal cloud account as a backup.
Capture the desktop status, error text, affected path, account email in masked form, client version, and available disk space. If a file is open, save it and stop editing on other devices. Simultaneous recovery edits can create conflicted copies that hide the original sequence.
Make a private inventory of the local path, last edit time, expected cloud location, and preservation copy. Note whether the entry belongs to a personal space, team space, shared folder, or shortcut. Those ownership boundaries can look alike in the filesystem but behave differently when membership or policy changes.
Sign in only through the official Dropbox site or app and verify the intended account and team. Compare a known folder and the affected file's content, size, version time, and ownership. Another trusted device can show whether the cloud version reached a second client, but it should not be used to overwrite the disputed file.
Classify the scope: all content, one team space, one shared folder, one device, one account, one direction, or one file. If the website shows the current upload but another device does not, focus on that device's download path. If the website lacks the local edit, protect the edit and focus on upload.
Use Dropbox's documented status location for your operating system and record whether it says indexing, syncing, up to date, paused, offline, or names specific files.[3] Confirm the app is running under the intended operating-system user and Dropbox account. Resume only if you know why it paused.
Let a small, stable queue settle. Repeated quitting, pausing, resuming, and mass-renaming can force re-indexing and obscure the original fault. If CPU, disk, or file counts are high, note whether the status is progressing before treating it as stuck.
Check whether the missing folder is excluded by selective sync or represented as online-only. An entry that appears in the filesystem may still require a download before it is an offline copy. Confirm availability before travel or before disconnecting the account.
For a file-specific failure, close the editing application, verify read permission, and inspect the full name and path for unsupported characters, reserved names, trailing spaces, or excessive length. Check whether another sync, backup, antivirus, or filesystem tool holds the file. Preserve the original before attempting a simpler test name.
Verify local free disk space and Dropbox quota separately. Confirm that the account still has access to the shared folder and that the owner did not remove, move, or rename it. A team administrator can limit syncing, external sharing, devices, or applications; a successful personal account test does not override those controls.
Complete any official reauthentication or MFA prompt directly in Dropbox. Do not accept a shared verification code or install remote-control software offered by an unsolicited helper. If the account or team is suspended, routing changes will not restore permission.
Differentiate DNS, timeout, TLS, proxy-authentication, HTTP, and account errors. Review the Dropbox proxy setting, operating-system proxy, security software, and managed firewall with the administrator. Keep certificate verification enabled and do not whitelist broad domains or processes without the organization's approval.
When applicable law and policy permit, repeat the same tiny-file test on one controlled alternative path. A VPN can change the route, but it cannot recover a deleted version, free storage, unlock a file, restore team membership, or override an administrator. Keep the account, client, file, and time window fixed. To set up that second route, connect AethoVPN to a nearby location in its app on the same machine and resync the identical small file; open a 3-day AethoVPN trial while your connection is still unrestricted, so the comparison is ready when you need it.
Apply only the correction supported by evidence: resume a known pause, free approved space, close a locking process, include the intended folder in selective sync, correct a permitted proxy, refresh authentication, or ask the owner or administrator to restore access. Wait for the queue to settle before changing another variable.
Unlinking or reinstalling is a late step. First preserve local changes and follow Dropbox's current troubleshooting sequence.[2] After recovery, confirm the test file and several real files by content, size, and timestamp on dropbox.com and the desktop app; then observe another trusted device. Reconcile conflicted copies manually and keep the disputed versions until the owner confirms the result.
If Dropbox creates conflicted copies, do not choose the newest timestamp automatically. Compare content, editor, device, and revision history, then let the document owner decide what to merge. For team data, record the support or administrator case before deleting recovery evidence.
No. Online-only items may still need a download. Verify the intended file's offline state and open it before relying on it without connectivity.
Selective sync, online-only settings, local disk limits, team-space membership, or the desktop client can explain the difference. Check status and settings before restoring or copying it.
Not necessarily. Compare dropbox.com, version information, desktop status, and another trusted device. Avoid creating a new file with the same name until the state is clear.
Yes. Close the editor and inspect the named error. Preserve the local version before ending processes or renaming the only copy.
Only after protecting unsynced files and exhausting narrower documented steps. Unlinking changes local account state and can complicate version reconciliation.
The directions can have different file, disk, permission, selective-sync, device, and network constraints. Test and document each direction independently.
No. A route change cannot fix service incidents, file locks, quota, permissions, selective sync, account access, or team policy.
Disclaimer: This article provides general operational information, not legal, security, data-recovery, employer-policy, or Dropbox-specific support advice. Preserve important data and follow current official and administrator instructions.
Sources checked 12 September 2026.
Related reading:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.