Why Won’t My External Hard Drive Sync to the Cloud? The Five Services Support Different Workflows

Short answer: an external hard drive can be used with cloud storage, but the word sync hides several different jobs. OneDrive may let you relocate the OneDrive sync root onto a qualifying non-ejectable external drive, but it does not let you add an arbitrary USB folder to normal OneDrive sync. Google Drive can back up detachable USB devices and then expose those backups as streamable cloud content. Dropbox has a dedicated external-drive Backup workflow. pCloud can upload directly from USB/external drives, and its Sync/Backup troubleshooting explicitly covers disconnected external drives. Apple documents iCloud Drive as its own cloud file location and treats external storage mainly as a separate copy/backup destination rather than a generic continuously synced iCloud source.

If your external SSD is not appearing in a cloud app, do not start by moving folders, changing drive letters, formatting the disk, or unlinking your account. First identify which of these jobs you actually need:

1. Cloud-root relocation — put the provider's normal synced folder on the external disk.
2. Two-way sync — changes on the external drive and cloud reflect each other.
3. Continuous backup — keep the external drive as the source and copy changes to the cloud.
4. One-way ingestion — upload an archive from the drive without turning it into a live sync relationship.

Those four workflows have different failure modes. Most "my USB drive won't sync" problems are really a workflow mismatch, not a broken drive.

First, classify the job before touching the disk

External-drive cloud problems become much easier once you stop treating every cloud transfer as synchronization.

This distinction matters because a provider can support one column and reject another.

A common example is OneDrive. Microsoft explicitly says folders outside OneDrive — including an external USB-drive folder — cannot simply be checked in Choose folders and added to sync. But Microsoft separately documents moving the entire OneDrive location to an external storage source when the drive is eligible. Those sound similar in a marketing sentence; operationally they are completely different.

The same pattern appears with Google. Drive for desktop can detect detachable USB devices and prompt you to back them up. Those backed-up devices then appear under the computer/device area in Drive and can be streamed. That does not mean Google turns every removable folder into another My Drive mirror root.

If your actual problem is broader — for example, you are still deciding whether the external drive should remain part of the architecture at all — use our Cloud Storage vs External Hard Drive decision guide before changing the sync design.

The fastest diagnostic: ask what happens when the drive is unplugged

This one test separates three very different architectures.

If unplugging the drive only pauses future backup

You are probably using a backup or upload source. The cloud copy may remain available even though the source drive is offline.

If unplugging the drive makes your normal cloud working folder disappear

You may have placed the provider's sync root or cache on that external disk. The application now depends on the drive being mounted at the expected path.

If unplugging the drive causes a sync error for one configured folder

You may have created a folder-level Sync/Backup relationship to the external location. The right fix is usually to reconnect the same mount path, not to rebuild the entire account.

This is especially important on Windows, where a removable disk can return with a different drive letter. pCloud's current troubleshooting guidance explicitly lists disconnected external/network drives and changed drive letters as reasons Sync or Backup jobs can fail. The correct first action is to reconnect the expected location and confirm the configured folder is reachable.

Do not treat a missing mount as database corruption.

OneDrive: root relocation is possible, arbitrary removable-folder sync is not

OneDrive has two rules that are easy to mix up.

Rule 1: you cannot simply add a random USB folder to normal OneDrive sync

Microsoft's Choose folders documentation says you can only select folders already inside OneDrive. Folders that are not in OneDrive, such as an external USB-drive folder, cannot be added to sync from that dialog.

That means this layout is not a supported ordinary OneDrive-folder selection:

E:\ClientArchive\2026\ → add directly to OneDrive sync

If the folder must remain in that location, the usual OneDrive model is not "attach any folder anywhere." You would need to move/copy it into OneDrive, use a different backup mechanism, or redesign the storage layer.

Rule 2: the OneDrive sync root itself can live on some external drives

Microsoft separately documents installing/moving OneDrive to an external drive. On Windows, the drive must satisfy OneDrive's filesystem/location requirements; removable USB flash drives are explicitly not supported for this role. Microsoft describes the supported external source as effectively non-ejectable and requires NTFS on Windows. On Mac, APFS is required for the external OneDrive location.

This is sync-root relocation, not arbitrary external-folder sync.

If you move the OneDrive root to an external disk, that disk becomes part of OneDrive's normal working path. Disconnect it at the wrong time and OneDrive no longer has the expected local root.

What OneDrive is good at here

Choose OneDrive's external-root model when:

• you need the entire local OneDrive working set on a larger secondary disk;
• the external disk is effectively persistent rather than a drive you unplug every evening;
• Windows / Microsoft 365 integration is already central;
• Files On-Demand can reduce how much of that root actually remains hydrated.

What it is bad at here

Do not choose this model when:

• the drive is a casual USB shuttle disk;
• you expect to disconnect it frequently;
• you only want one folder from the external drive backed up while leaving the OneDrive root elsewhere;
• you are trying to create an offline archive that should not inherit sync deletion behaviour.

If your real complaint is that OneDrive keeps consuming local disk after you already used Files On-Demand, read why OneDrive files can re-download after Free up space. That is a hydration problem, not an external-drive problem.

Google Drive: detachable USB devices fit the backup model better than the My Drive mirror model

Google Drive for desktop separates My Drive, folders from your computer, and backed-up USB devices.

Google's current documentation says Drive for desktop can prompt when it detects a USB device such as a flash drive or camera. It also documents that backed-up USB devices remain visible alongside other computers and can be streamed.

That is useful for external media because the drive can remain the source while the cloud keeps another copy.

The important detail is that Google does not describe backed-up USB devices as ordinary mirrored My Drive folders. Its Stream/Mirror documentation explicitly separates them: My Drive can be streamed or mirrored; backed-up USB devices are exposed in the "other computers / backed-up devices" path and are streamable.

Why that matters

Suppose a photographer has a 4 TB SSD named FIELD-2026.

If the goal is:

"When I connect this disk, push its contents into my Google account so I have another cloud copy."

Google's USB backup flow can fit.

If the goal is:

"Treat this removable drive as another full two-way My Drive root and keep the exact same folder tree bidirectionally synced forever."

That is a different requirement. Do not infer it from the existence of USB backup.

Google is particularly strong when your archive is already part of a larger Drive / Workspace workflow. But the minute you start moving multi-terabyte media only because a detachable-device prompt exists, check whether you are solving backup, active collaboration, or archive storage. Those are not the same job.

For the broader arbitrary-folder question, see Can cloud storage back up folders outside the sync folder?. It explains why a folder can be protected without becoming part of the provider's normal cloud drive.

Dropbox: the clearest dedicated external-drive Backup workflow of the five

Dropbox is unusually explicit about external-drive backup.

Dropbox Backup supports external hard drives, and Dropbox documents supported filesystems on Windows and macOS. It also distinguishes Backup from normal cloud storage: Backup creates an up-to-date copy of selected external-drive content, but it does not magically free space on that source drive.

Dropbox also documents an important boundary:

The Dropbox folder cannot be located on the same external hard drive that you are trying to back up.

That rule reveals the architecture. Dropbox Backup treats the external drive as a source device. The Dropbox storage/sync area and the backup source are separate roles.

A useful Dropbox edge case

Dropbox says external-drive files can only be deleted directly from the external hard drive in the Backup workflow. That is a meaningful operational distinction from ordinary two-way sync.

However, backup changes still have consequences. Dropbox's current Backup FAQ says deletion on the source and backup are linked in the backup lifecycle, and recovery depends on plan retention. Do not call this an immutable archive.

Dropbox is the stronger fit when

• external-drive backup is a first-class requirement;
• you want mature backup/recovery tooling around that drive;
• your team already uses Dropbox sync/sharing;
• you do not need the drive to become your ordinary Dropbox sync root.

Dropbox is less compelling when

• you only want to ingest an old archive once;
• you do not want another continuing backup relationship;
• long-term storage cost matters more than Dropbox's workflow maturity.

If the drive contains client deliverables and external sharing is the next step, pair this with our large-file sharing without recipient accounts comparison.

iCloud Drive: treat the external disk as a separate location, not an arbitrary sync source

Apple's public documentation frames iCloud Drive as its own file location available in Finder and the Files app. Apple separately documents external USB / external storage as a destination for manual copies and backup workflows.

What Apple does not document for ordinary consumer iCloud Drive is a generic "select any folder on an attached external disk and continuously sync it into iCloud Drive" control comparable to dedicated backup tools.

That difference matters for Mac users because Finder makes both locations easy to see. Visibility in Finder does not mean the two locations participate in the same synchronization relationship.

The safe Apple workflow

If an external SSD contains a library you want in iCloud Drive:

1. keep the source copy intact;
2. copy the intended files into iCloud Drive;
3. wait until Finder/iCloud reports the cloud upload has completed;
4. verify the files from another device or iCloud.com;
5. only then decide whether the original external copy is still needed.

Do not drag the only copy out of the external disk and assume the cloud transfer has completed merely because the files appeared in Finder.

Apple itself recommends keeping additional copies of important iCloud information and separately describes copying files to USB/external storage as a backup method. That is a useful reminder: iCloud Drive sync is not a reason to throw away your independent external copy.

If the problem is actually that iCloud Optimize Storage is not releasing Mac disk space, use our iCloud Optimize Storage diagnosis instead. External-drive sync will not fix a local iCloud hydration issue.

pCloud: external devices are supported in more than one way — choose the right one

pCloud's current desktop documentation exposes three useful paths for external-storage users:

1. Uploads — one-way upload from any location, explicitly including USB drives, external hard drives and CDs.
2. Sync / Backup — folder relationships that can reference external locations; pCloud troubleshooting explicitly covers disconnected external or network drives.
3. pCloud Drive — the virtual cloud drive, which remains a separate remote storage layer and still uses local cache for active transfer/access.

That separation is the main pCloud advantage in this specific problem.

It means you do not have to force every external-drive job into one sync model.

Use Uploads for cold archive ingestion

If you have a 2 TB SSD of completed video projects and you mainly want to get them into the cloud, Uploads is usually cleaner than creating a permanent two-way Sync relationship.

pCloud explicitly says Uploads can take files/folders from external devices. The external device must remain connected during the upload.

Operationally, this is useful because you can finish the upload, verify the cloud copy, then disconnect the drive without leaving behind a live sync relationship that will later interpret deletions or edits as state changes.

That is a strong fit for:

• old camera-card dumps;
• completed RAW libraries;
• exported video masters;
• archived client projects;
• drives you only connect occasionally.

Use Sync only when you actually want two-way state

pCloud defines Sync as bidirectional synchronization. That means changes propagate.

If the external drive is your active working drive and you genuinely want the cloud side to track edits, Sync can make sense. But that architecture requires discipline:

• the external drive should mount consistently;
• on Windows, do not casually change drive letters;
• if the drive disappears, resolve the missing-path error instead of deleting/recreating the job blindly;
• remember that Sync is not the same as a disconnected backup.

pCloud's current troubleshooting guide specifically lists unavailable external/network drives as Sync/Backup error conditions. That is useful because it proves the app expects such configured paths — but it also proves the dependency: if the path disappears, the job cannot continue.

Use Backup when the external folder is a protection source

If your goal is "keep this folder protected in the cloud" rather than "make both sides identical working copies," the Backup model is conceptually safer.

Still, do not mistake it for immutable backup. pCloud's documented Backup behaviour reflects changes, and deleted items rely on Trash / revisions / Rewind according to the plan and retention model.

If recovery depth matters, read how long cloud services keep deleted files before deciding that any backup checkbox is sufficient.

Five-provider comparison: what "external drive support" actually means

This table is intentionally conservative. A provider may expose additional enterprise tooling, OS-specific capabilities, APIs or third-party integrations. The question here is the normal desktop workflow a user sees when they plug in a USB HDD or SSD.

The biggest mistake: using two-way sync for a drive you intend to unplug and forget

A removable archive drive and a live sync root have opposite assumptions.

A removable archive assumes:

• it may be offline for weeks;
• it should still contain a stable historical copy;
• disconnecting it is normal;
• deleting cloud data should not automatically rewrite the offline archive.

A two-way sync relationship assumes:

• both endpoints represent the same changing working set;
• edits and deletions should propagate;
• the source path will return consistently;
• conflicts are something to reconcile, not a permanent archival boundary.

If you find yourself repeatedly connecting a cold archive only so a sync client can "catch up," ask whether the job should be a one-way upload/backup instead.

This is where many users quietly create risk: they think "more synchronization" means "more backup." It often means the opposite — more ways for a bad state to propagate.

Our ransomware and cloud sync comparison explains the same principle under a more severe failure mode.

Safe migration sequence for a multi-terabyte external drive

Do not move 4 TB on day one. Prove the workflow with a representative subset.

Step 1 — Stabilize the drive identity

Before configuring anything:

• confirm the drive filesystem;
• confirm free space and SMART/health if your OS exposes it;
• on Windows, note the drive letter;
• on macOS, note the mounted volume name;
• avoid renaming or reformatting during the test.

Do not reformat the drive merely to satisfy a cloud app until you have another verified copy of the data. Reformatting is destructive.

Step 2 — Pick a 20–50 GB test folder

The test should include the things that normally break migrations:

• large files;
• many small files;
• nested folders;
• long filenames;
• the file types you actually use.

Step 3 — Decide whether this is Sync, Backup or Upload

Write the expected outcome before clicking anything.

Example:

"After the test finishes, I should be able to unplug the SSD, delete nothing, and still download the verified cloud copy from another device. Future edits on the SSD do not need to propagate automatically."

That expectation describes one-way upload/backup, not two-way sync.

Step 4 — Verify from a second path

Do not verify using only the same desktop app that performed the upload.

Check from:

• provider web interface;
• another computer;
• mobile app;
• a clean download of several representative files.

For important media, compare file size and, where practical, cryptographic hashes of a sample set after download.

Step 5 — Disconnect the drive and observe behaviour

A safe test answers:

• does the cloud copy remain accessible?
• does the app report a normal "source unavailable" state or a destructive error?
• when you reconnect, does the job resume without rebuilding everything?
• does the drive return at the same mount point?

Step 6 — Only then scale up

Once you understand the state model, move the larger archive.

If you are also trying to keep the computer SSD mostly empty, combine this with our Big Five local-disk-space comparison rather than assuming external storage and cloud-only storage solve the same constraint.

What not to do

Do not put the only copy on a drive and then reformat it to satisfy the cloud client

Create another verified copy first.

Do not use symbolic links or filesystem tricks just to bypass a provider restriction unless the provider documents that setup

A configuration can appear to work while sitting outside the provider's supported sync model. That becomes dangerous during updates, recovery or path changes.

Do not unplug a drive during an active migration and assume the client will infer your intent

Pause/stop the transfer first where possible, then confirm the app is idle.

Do not delete the original immediately after the progress bar reaches 100%

Verify the remote files independently and test restore/download.

Do not call two-way sync a backup

If deletion or ransomware can propagate to the cloud, your recovery depends on version history, Trash, Rewind and retention.

For the conceptual distinction, see Cloud Backup vs Cloud Storage.

Which service is the better fit for an external-drive workflow?

Choose OneDrive if...

Your external disk is really a persistent larger local home for the OneDrive root, not a removable archive shuttle. Microsoft 365 / Windows integration is doing enough work that keeping the OneDrive model is valuable.

Choose Google Drive if...

You want detachable USB-device backup integrated into Drive for desktop and your cloud workflow already lives around Google. It is especially reasonable when the device backup is a secondary copy rather than a new bidirectional My Drive workspace.

Choose Dropbox if...

You want a mature, clearly documented external-drive Backup product and recovery controls matter more than minimizing the number of Dropbox-specific workflows.

Choose iCloud if...

The external disk is mainly an independent local/Time Machine/manual-copy layer and your real cloud workflow remains Apple-native. Do not migrate merely because another provider exposes more external-drive knobs.

Choose pCloud if...

You are the user who keeps several different storage roles separate:

• an external SSD for active/offline media;
• a remote archive that should live in a virtual drive;
• occasional USB drives that need one-way ingestion;
• selected folders that genuinely need Sync or Backup.

That identity matters because pCloud's advantage here is not "it supports USB." Dropbox and Google also support external-drive backup workflows. The advantage is that pCloud gives you a clean one-way Uploads path for removable archive ingestion while keeping pCloud Drive, Sync and Backup as separate tools.

If you already know your external drives are mostly archive sources rather than permanent live sync roots, the missing decision is now capacity: how much remote storage do you need once those drives stop being the only long-term copy?

pCloud decision checkpoint If you want a storage-first cloud where external-drive ingestion, virtual-drive access and selected Sync/Backup jobs can stay separate, compare the current personal plans before you migrate the full archive. See which pCloud capacity fits the archive you actually have → Affiliate link · sponsored · Opens pCloud's current personal plans. Verify current capacity, pricing and terms before choosing.

The decision most people still have not finished

If your USB SSD "won't sync," you may not have a provider problem at all.

You may be trying to make one drive perform three incompatible jobs:

• active working disk;
• disconnected backup;
• continuously synchronized cloud source.

Those jobs should often be separated.

A live two-way sync relationship is useful when you want the same evolving state in two places. A backup relationship is useful when you want recoverability. A one-way upload is useful when you want migration/archive ingestion without a permanent relationship.

Once you label the job correctly, the provider comparison becomes much smaller — and you stop trying increasingly dangerous workarounds just to make a removable disk behave like an internal cloud-sync root.

Related reading

• Can cloud storage back up folders outside the sync folder? — use this when the external disk should remain the source rather than become the cloud root.
• How long do cloud services keep deleted files? — understand the recovery window before trusting a live Backup/Sync relationship.
• Which cloud storage uses the least local disk space? — separate external-drive capacity from cloud-only/virtual-drive local-space behaviour.

More reading

• Cloud Storage vs External Hard Drive
• Can Cloud Storage Protect Against Ransomware?
• How pCloud Drive Cache Actually Works

Sources and verification

Primary-source checks completed 21 August 2026:

1. Microsoft Support — Install OneDrive on an external drive: qualifying non-ejectable external storage is supported; removable USB drives are not supported for the OneDrive root; filesystem requirements apply.
2. Microsoft Support — Choose which OneDrive folders you want to sync: folders outside OneDrive, including external USB-drive folders, cannot simply be added through Choose Folders.
3. Google Drive Help — Stream & mirror files with Drive for desktop: backed-up USB devices are a distinct supported source and remain streamable; My Drive has separate Stream/Mirror semantics.
4. Google Drive Help — Customize Drive for desktop settings: Drive can prompt to back up detected USB devices.
5. Dropbox Help — Dropbox Backup FAQs: external hard-drive backup is supported; filesystem and plan-specific limits apply; the Dropbox folder cannot reside on the external drive being backed up.
6. Apple Support — How to back up your Mac and Archive or make copies of iCloud data: Apple documents iCloud Drive and external storage as separate storage/copy paths and recommends independent copies.
7. pCloud Help — Uploading, Downloading, and Organizing Files: Uploads supports USB drives, external hard drives and CDs; pCloud Drive upload still uses cache.
8. pCloud Help — Troubleshooting Sync, Back up and Upload issues: missing/disconnected external, network or mapped drives are recognized failure conditions for configured Sync/Backup paths.

Internal link map

1. Cloud Storage vs External Hard Drive → /articles/cloud-storage-vs-external-hard-drive/ → opening diagnosis → Upstream.
2. OneDrive files can re-download after Free up space → /articles/onedrive-files-keep-downloading-after-free-up-space/ → OneDrive section → Horizontal.
3. Can cloud storage back up folders outside the sync folder? → /articles/cloud-backup-folders-outside-sync-folder/ → Google section → Horizontal.
4. large-file sharing without recipient accounts → /articles/share-large-files-without-account/ → Dropbox section → Horizontal/downstream.
5. iCloud Optimize Storage diagnosis → /articles/icloud-drive-optimize-mac-storage-disk-space/ → iCloud section → Horizontal.
6. how long cloud services keep deleted files → /articles/cloud-storage-deleted-file-recovery-retention/ → pCloud Backup section → Horizontal.
7. ransomware and cloud sync comparison → /articles/can-cloud-storage-protect-against-ransomware/ → sync-vs-archive section → Horizontal.
8. Big Five local-disk-space comparison → /articles/cloud-storage-without-using-local-disk-space/ → migration sequence → Downstream.
9. Cloud Backup vs Cloud Storage → /articles/backup-vs-cloud-storage/ → What not to do → Upstream education.
10. How pCloud Drive Cache Actually Works → /articles/pcloud-drive-cache-explained/ → More reading → Downstream product education.

Reverse internal-link suggestions

After this batch goes live, add contextual links to this article from:

1. /articles/cloud-storage-vs-external-hard-drive/ — section discussing two-layer cloud + external-drive architectures.
2. /articles/cloud-backup-folders-outside-sync-folder/ — external removable-drive edge case.
3. /articles/cloud-storage-without-using-local-disk-space/ — clarify external-drive capacity vs virtual-drive capacity.
4. /articles/pcloud-drive-cache-explained/ — when discussing external archive ingestion versus pCloud Drive copy/paste.
5. /articles/backup-vs-cloud-storage/ — example of removable-drive Sync vs Backup semantics.

Image metadata

1. Hero

• Purpose: Compare the three meanings of external-drive cloud support across the Big Five.
• Placement: After introduction.
• Filename: external-drive-cloud-sync-big5-hero.svg
• Alt: Comparison of OneDrive, Google Drive, Dropbox, iCloud and pCloud external-drive sync, backup and upload models
• Caption: External-drive support can mean root relocation, backup, two-way sync or one-way ingestion — the five services do not implement the same model.
• Source: CloudScope original conceptual diagram based on cited vendor documentation.
• Format: SVG.
• Dimensions: 1200 × 760.

2. Workflow model

• Purpose: Separate Sync, Backup and Upload for removable storage.
• Placement: Before the five-provider comparison table.
• Filename: external-drive-sync-backup-upload-models.svg
• Alt: Diagram showing two-way sync, backup and one-way upload relationships between an external hard drive and cloud storage
• Caption: Choose the relationship first. Two-way sync propagates state; backup preserves a protection copy; one-way upload is suited to archive ingestion.
• Source: CloudScope original conceptual diagram.
• Format: SVG.
• Dimensions: 1200 × 760.

3. Diagnostic tree

• Purpose: Help readers diagnose why an external drive is not working with a cloud client.
• Placement: Safe migration / troubleshooting section.
• Filename: external-drive-cloud-sync-diagnostic-tree.svg
• Alt: Decision tree for diagnosing external hard drive cloud sync failures based on drive availability, workflow type and mount path
• Caption: A missing drive letter or mount path is a different failure from an unsupported sync model. Diagnose the layer before resetting the client.
• Source: CloudScope original technical decision tree.
• Format: SVG.
• Dimensions: 1200 × 860.

CTA specification

• Position: After provider-fit comparison, before conclusion.
• Context: Reader has identified that the external drives are archive sources and wants separate Upload / Virtual Drive / Sync / Backup roles.
• Copy: See which pCloud capacity fits the archive you actually have →
• Destination: https://partner.pcloud.com/r/156919
• Plan Match: Plans & Pricing.
• Attribute on publish: rel="sponsored noopener".
• Density: One commercial CTA only; problem/comparison intent does not justify repeated buttons.

Structured data / social

• Structured data: Article, BreadcrumbList.
• Canonical: https://cloudscope.org/articles/sync-external-hard-drive-cloud-storage/
• OG title: External Hard Drive Cloud Sync: What OneDrive, Google, Dropbox, iCloud and pCloud Actually Support
• OG description: Root relocation, USB backup, two-way sync and one-way upload are not the same feature. Compare the Big Five before building an external-drive cloud workflow.
• OG image: /assets/external-drive-cloud-sync-big5-hero.svg