Cloud storage not syncing usually traces to a paused client, a different signed-in account, a folder excluded from this device, a full cloud quota or local disk, or one file that is open, blocked by permissions, or given an unsupported name. Before testing those causes, protect the only complete copy of every important file. Then determine whether the failure affects all files or one item, uploads or downloads, one device or several, and the web app or only a local sync client; those distinctions usually reveal the failing layer without a destructive reset.

Do not delete files in bulk, move the sync root, or unlink an account until you have compared the web copy and every relevant local copy. A deletion can itself synchronize, and an online-only placeholder is not a backup.

Key Takeaways

Separate upload, download, and two-way synchronization before changing settings.

Confirm the account, sync switch, pause state, storage quota, and selected folders.

Check whether the affected item is a placeholder, open file, permission problem, or unsupported name or path.

Preserve both sides of a version conflict until the correct contents are known.

Relinking the account is a last step because it can remove local placeholders or create a large resync.

Use the device and app troubleshooting guide if several unrelated apps also cannot save, open, or transfer files.

Step 1: Diagnose cloud storage not syncing by direction

Create one small, non-sensitive test file with a distinctive name in a folder that is supposed to synchronize. Do not use a confidential document or the only copy of anything valuable. Observe it from the local file manager and the provider's official web app.

Use the result to classify the problem:

Observation	Likely scope to investigate
Local file never appears on the web	Upload, local client, file eligibility, or account quota
Web-created file never appears locally	Download, selected-folder, placeholder, or local-space issue
One existing file stays old on one device	Open-file lock, conflict, permission, or stale client state
Every file is stale on one device	Wrong account, paused client, signed-out session, or device policy
Files are stale on every device and the web	Provider service, account, quota, or upstream application

Also note whether synchronization is merely queued or has stopped with an error. A large folder added moments ago can take time to scan, upload, and index. Record the exact status text, icon, affected path, time of the last known good update, and whether the device was asleep or offline. Avoid repeatedly editing the test file while observing it; that creates new versions and confuses the direction test.

The web app is useful as an account-side observation point, but it is not automatically the newest or correct copy. Compare modification times and actual contents. Time-zone display differences can make identical moments look different, so use the file contents and provider version history when available.

Step 2: Verify the account, sync controls, and selected folders

Open the official sync client and verify the signed-in account. Personal, work, school, and shared-drive accounts may expose similar folder names. Confirm the full account identity without posting it in a support ticket. If the client reports that authentication expired, sign in through the provider's official flow rather than a link in an unexpected email.

Check whether synchronization is paused because of a manual command, battery-saving mode, metered connection, scheduled policy, or organization control. Resume it once and watch the next status. Do not disable a work or school policy to force a transfer; ask the administrator which folders and file types are permitted.

Review the provider's selected-folder or backup settings. A folder visible on the web may intentionally be excluded from this computer, and a local folder may sit outside the configured sync root. Do not move the entire sync root merely to test this. Instead, compare the displayed configured path with the affected item's path and use the small test file inside a known synchronized folder.

Some services distinguish a mirrored local folder from streamed or files-on-demand content. Apple's current iCloud Drive setup guidance says to update each device, sign in to the same Apple Account, and turn on iCloud Drive synchronization for that device.［1］ The menu names differ by platform, so use the provider's current documentation for the exact client rather than copying a path from another operating system.

Step 3: Check whether cloud or local storage is preventing progress

Check the cloud account's total quota, including trash, backups, photos, email, and shared content when the provider counts them. A nearly full account may still download existing files while refusing new uploads, which looks like a one-way synchronization problem. Emptying trash is a deletion, so inspect it first and confirm retention requirements.

Check free local storage as well. A streamed file still needs working space to download, and a client may need temporary space for databases, partial transfers, or conflict copies. If the startup disk is nearly full, follow the Mac storage guide or the relevant platform's storage process before forcing a resync.

Do not use a cleanup utility against a live sync folder unless the provider explicitly supports it. Duplicate finders, bulk organizers, and “cloud cleaners” can turn a local reorganization into synchronized deletions. If space is urgently needed, move unrelated, verified files outside the sync root or use the provider's documented online-only feature after confirming the web copy opens correctly.

For shared folders, distinguish your personal quota from the owner's quota and the organization's storage limit. Verify that you still have membership and write access. A folder can remain visible after permission changes while uploads fail or appear under another account.

Step 4: Inspect the first file blocked by local state, permissions, name, or path

If most files synchronize, focus on the first failing item. Open it in the appropriate application while online. If it must download first, let that finish before testing an upload or moving it to another application.

Close applications that are actively writing the file, especially databases, virtual-machine images, archives, and large media projects. Some formats are not safe to synchronize while open. Follow the application's supported collaboration or backup workflow instead of treating a live database as an ordinary document.

Check the file and its parent folder permissions. The sync client needs to read an upload source and write a download destination. Do not make an entire home folder world-writable or grant broad disk access without understanding the request. On a managed device, provide the exact permission message to IT.

Google's Drive for desktop troubleshooting guidance includes checking the internet connection, restarting the application, disconnecting and reconnecting only after considering unsynced files, and reviewing storage and folder permissions.［2］ Treat the client's exact error as stronger evidence than a generic spinning icon.

Review the provider's restrictions for unsupported characters, reserved names, path length, file size, symbolic links, packages, and temporary files. Microsoft documents that OneDrive can block a particular file while another application is using it or when OneDrive lacks read and write permission.［3］ Close the relevant application or correct only the affected item's permission after preserving its original.

Judge local availability from the provider's status icon or offline-availability label, not from logical file size. Microsoft explains that Files On-Demand can display an online-only file without downloading its contents; opening it downloads the file and changes its availability state.［4］

In Windows File Explorer, the availability details or the provider's own label may show a state such as “Excluded” or “Not synced” for one item. Treat that as a file-level result: check whether the provider or your organization excludes that file type, name, or location, then read the client's error for that item instead of re-uploading the whole folder.

Step 5: Resolve a version conflict or wait for a service-side interruption

A conflict means two locations changed the same logical file without a clean common version. Do not immediately delete the copy marked “conflicted,” “computer name,” or a timestamp. Open both copies safely, compare the contents, and preserve the needed material under clearly different names outside the live sync folder while deciding which version should become authoritative.

For collaborative documents, use the provider's version history when available. Confirm the account, timestamp, author, and contents before restoring. Restoring an older version can overwrite newer work for everyone. Exporting a safety copy first is usually reversible; replacing the shared version is not.

Check the provider's official service-status page when several files, users, or devices fail at the same time. A status page that shows no incident does not prove the local client is healthy, but a confirmed incident is a reason to stop resets and wait. Record the incident time and preserve the local files.

If only a third-party app fails to update its cloud-backed data while ordinary files synchronize, the problem may belong to that app's account, database, or export workflow. Do not manipulate its internal data folder unless the app vendor documents that operation.

Step 6: Restart, sign in again, or relink only after safer checks

After recording evidence and protecting unsynced work, quit and reopen the sync client. A normal application restart can clear a stalled process without changing the account relationship. Reboot the device only if the client, filesystem integration, or update process remains stuck; save all work first.

Signing out has a larger effect. Read the confirmation dialog carefully and identify which items are fully local, online-only, or unsynced. Copy irreplaceable local work to a separate, nonsynchronized location. Verify that the copy opens before continuing.

Relinking or resetting the client is the last step, not the first. It can rebuild the local database, redownload placeholders, duplicate folders, or remove offline availability. Follow instructions for the exact provider, client version, account type, and operating system. Do not reuse a command intended for another platform or point a new account at an old sync folder without the provider's documented migration path.

Stop if the web and local contents disagree and you cannot identify the correct version. Preserve both, capture the folder paths and status messages, and ask the provider or organization administrator how the service will reconcile them.

Step 7: Collect evidence before escalation

Prepare a privacy-conscious report with the account type, provider and client version, operating system, affected direction, one file or all files, exact error, first failing time, available cloud and local space, and results of the small test file. Include sanitized paths and filenames rather than private documents.

Do not upload client databases, access tokens, raw diagnostic archives, or confidential files to a public forum. Use the provider's official support channel and its documented diagnostic collection only after reviewing what the bundle contains. For a work account, let IT collect managed-device logs.

Cloud synchronization is not a substitute for backup. If a mistaken deletion or corruption can propagate, maintain an independent, restorable copy. The NAS backup guide explains why a separate recovery copy and a tested restore matter.

Summary

When cloud storage is not syncing, protect unique local work and identify the failed direction before changing the account. Verify the correct account, pause state, quota, selected folders, local space, placeholders, permissions, names, and exact error. Preserve both sides of conflicts and check the official service status. Restarting is low risk; signing out, resetting, or relinking belongs at the end, after the web and local copies have been compared.

FAQ

Why are cloud files not syncing to my computer when they are visible online?

The computer may be signed into another account, exclude that folder, lack local space, be paused, or use online-only placeholders. Check the official client's account and folder settings before relinking it.

Why does one cloud file not sync while the others do?

The item may be open, unreadable, too large, use an unsupported name or path, or have a permission problem. Preserve it and use the client's exact file-level error.

Does a sync icon mean the file is backed up?

No. It may mean queued, transferring, online-only, or complete, depending on the provider. Confirm the file opens from an independent recovery location before treating it as a backup.

Should I delete and re-add the account?

Only after safer checks and after protecting unsynced local files. Relinking can rebuild folders, remove offline copies, or create conflicts.

Why are files not updating across devices in both directions?

Upload and download can fail for different reasons. Quota or read permission can block uploads, while selected-folder settings or local space can block downloads.

What should I do with a conflicted copy?

Keep both versions, compare their contents and history, and merge or rename them outside the live sync folder before choosing an authoritative version.

Can I move the whole sync folder to fix the problem?

Not as an initial test. Moving the root can trigger a rescan, duplication, or synchronized deletion. Use the provider's documented relocation procedure only after a verified backup.

Is cloud synchronization the same as backup?

No. Synchronization can propagate deletion, corruption, or an unwanted edit. Keep an independent recovery copy and test that it can be restored.

Sources

Apple Support - Set up iCloud Drive — https://support.apple.com/en-us/118443
Google Drive Help - Fix problems in Drive for desktop — https://support.google.com/drive/answer/2565956?co=GENIE.Platform%3DDesktop&hl=en-en
Microsoft Support - Troubleshoot OneDrive error: This file can't be synced — https://support.microsoft.com/en-US/onedrive/troubleshoot-onedrive-error-this-file-can-t-be-synced
Microsoft Support - Save disk space with OneDrive Files On-Demand for Windows — https://support.microsoft.com/en-US/onedrive/save-disk-space-with-onedrive-files-on-demand-for-windows

Sources checked 4 October 2026.

This article provides general troubleshooting information. Follow the current instructions for your provider, device, and organization before changing or removing synchronized data.

Cloud Storage Not Syncing: What to Check