Dropbox Online-Only Files Keep Downloading Again? Diagnose What Rehydrated Them

Short answer: making a Dropbox file online-only removes the local file data while keeping the item visible in your Dropbox folder, but it does not mean the file can never become local again. Dropbox documents that opening an online-only file downloads it automatically. A file can also end up local because an application opened it, because you or a workflow marked it available offline, or because the file was created locally and then moved into Dropbox. On macOS, Dropbox on Apple's File Provider framework also changes how third-party applications can open online-only files.

The safest first action is therefore not to reinstall Dropbox, delete the folder, clear application state, or assume sync is broken. First identify which files changed state, when they changed, and what process or user action accessed them immediately beforehand.

The important mental model is:

Online-only is a current storage state, not a permanent prohibition on local access.

That distinction explains most cases where a user frees hundreds of gigabytes, works normally for a few days, and then discovers that the Dropbox folder is consuming local disk again.

First confirm whether the file actually became local again

Before changing settings, inspect the file state in Finder or File Explorer.

Dropbox distinguishes between:

• Online-only — the file remains visible but its full contents are not stored locally.
• Available offline — the file has a local copy and can be opened without an internet connection.

If the item is still online-only but your SSD is filling, the problem may be something else: Dropbox cache, another application's working files, local copies elsewhere, or files that were never converted to online-only in the first place. That is a different diagnostic path from true rehydration.

If your real symptom is "I deleted Dropbox files but the disk space did not come back," use the Dropbox deletion-and-disk-space diagnostic instead. If Dropbox itself is stuck or not synchronizing, use the broader Dropbox sync troubleshooting guide.

A quick evidence check

Pick one representative file that you know is online-only.

1. Note its sync icon and local disk usage.
2. Do not open it yet.
3. Watch whether its state changes by itself over a short controlled period.
4. Then deliberately open it once.
5. Check whether it becomes locally available.

Dropbox explicitly documents the second half of this test: opening an online-only file downloads it and makes it available locally. If the state changes before you deliberately open it, then you have evidence that another application, automation, user action, or configuration is involved.

That difference matters because it stops you blaming Dropbox for behaviour that may actually be initiated by another process.

Cause 1: you opened the file — and Dropbox behaved as designed

This is the most common case and the easiest to misinterpret.

Dropbox's current help documentation says that when you open an online-only file from the Dropbox folder, it automatically downloads to the computer and becomes available offline. The file needs local data because the application opening it needs actual bytes to read.

That means this sequence is normal:

Online-only → open file → download → locally available

It is not evidence that Dropbox ignored your online-only setting.

What to do

After you finish with the file, make it online-only again if you no longer need offline access.

Why it works

You are changing the file from a hydrated local state back to a cloud-only state while keeping the remote Dropbox copy.

What it does not do

It does not prevent the file from downloading again the next time it is opened.

How to verify

Confirm the file returns to the online-only/cloud state and that its local space is reclaimed after the operating system and Dropbox finish the state change.

If you repeatedly open the same 30 GB project every day, manually cycling it online-only and local may be the wrong workflow. In that case, the problem is not a broken setting. Your active working set genuinely needs local storage.

Cause 2: a third-party application accessed the file

A file can be opened without you double-clicking it in Finder or File Explorer.

Applications may request a file when you:

• open a recent-project list;
• launch an editor that restores the previous workspace;
• ask a media application to inspect a project;
• use a workflow that resolves linked assets;
• open a file through a third-party application's own file picker.

Dropbox documents that its desktop integration allows online-only files to be opened from Finder/File Explorer and third-party applications. On macOS, Dropbox's File Provider integration was specifically designed to improve how online-only files work with third-party apps.

That does not prove that every antivirus scanner, indexer, thumbnail generator, or backup tool will automatically hydrate every Dropbox file. Do not diagnose an unnamed background process without evidence.

The defensible conclusion is narrower:

If an application actually opens or requests the content of an online-only file, that access can cause the file to download.

How to prove this instead of guessing

Use one test folder containing a few online-only files.

1. Close the application you suspect.
2. Confirm the files remain online-only.
3. Launch the application but do not open the project.
4. Observe whether anything changes.
5. Open the project or file through that application.
6. Check exactly which files become local.

This isolates application access from vague claims such as "Dropbox downloads things randomly."

If only project-linked files hydrate after you open an editor, Dropbox is likely responding to normal file access. If unrelated folders hydrate without access, continue down the diagnostic tree.

Cause 3: the file was created locally, so it never started as cloud-only

This is a subtle but important distinction.

Dropbox lets you set a default for new files so newly added content in the Dropbox root can default to online-only. But Dropbox also documents an exception: if you create a document directly on the computer and then move it into the Dropbox folder, that file remains available offline unless you manually make it online-only.

That can produce a misleading pattern:

• old archive files are online-only;
• you create 200 GB of video exports locally;
• you move those exports into Dropbox;
• they upload successfully;
• they still occupy 200 GB locally.

Nothing "downloaded again." The files were local from the start.

How to verify

Sort the affected files by creation or modification time. If the disk growth tracks newly created local files rather than previously online-only files, you are diagnosing the wrong mechanism.

Fix

After Dropbox confirms the upload is complete and the remote files exist, make those uploaded files online-only if you no longer need the local copies.

Do not do this before upload verification. A large local-only export that has not finished uploading may still be the only complete copy.

If you are routinely ingesting large external-drive archives, this is also where external-drive cloud workflows matter. Upload, backup, sync, and permanent local mirroring are not the same job.

Cause 4: the file or folder was made available offline on purpose

Dropbox supports an explicit Make available offline state. That state is supposed to consume local storage.

This can be triggered intentionally when you know you will be disconnected, when a project folder must remain local, or when another user with access to the same computer changes the local state.

For teams, administrators can also set defaults controlling whether new files are online-only or local. Dropbox additionally exposes a team setting that can make files not opened for a few months automatically become online-only.

Notice the direction of that automation: it can help dehydrate old files. It does not mean Dropbox promises that recently accessed files remain cloud-only forever.

What to check

• Is the affected folder intentionally available offline?
• Is a team administrator controlling default sync behaviour?
• Is the disk growth concentrated in one working folder rather than the entire account?

If yes, fix the policy or folder state rather than reinstalling the client.

Cause 5: macOS File Provider changed the behaviour you were used to

Dropbox on macOS now uses Apple's File Provider framework for supported systems. Dropbox says this integration improves compatibility with online-only files in third-party applications and changes some desktop behaviour to match macOS requirements.

If the problem appeared after a macOS or Dropbox migration, first check whether you are using Dropbox on File Provider before comparing the behaviour with an older Mac, an older help article, or a pre-File-Provider setup.

This matters because a troubleshooting article that assumes "Dropbox on Mac behaves exactly like it did years ago" can send you in the wrong direction.

What not to do

Do not opt out of File Provider merely because local disk usage changed unless you have identified a real File Provider-specific problem. Dropbox warns that opting out after migration can require offline files to be downloaded again. That can create the exact disk-pressure event you were trying to avoid.

If you do change File Provider state for a legitimate reason, first verify that your new Dropbox location is synchronized and that any local-only work is protected.

Cause 6: you are counting the wrong local storage

Not every byte related to Dropbox is the hydrated file itself.

The Dropbox folder may coexist with:

• application caches;
• editor proxies;
• exported render files;
• downloaded attachments;
• duplicate project folders;
• the Dropbox cache used for file operations;
• other local folders that contain copies of the same media.

This is why "Dropbox is using 300 GB" is not enough evidence to conclude "300 GB of online-only files came back."

Use file-state icons and filesystem size to prove which Dropbox items are actually local.

If you only need a large cloud library visible without keeping the whole library offline, compare the state model in cloud storage without using all your local disk. If you are seeing similar behaviour in another service, OneDrive rehydration after Free up space is a useful parallel because the same mental mistake appears under different product terminology.

The diagnostic tree: do not reset Dropbox until you know which branch you are on

Use this order:

1. Confirm the file really changed from online-only to local.
2. Ask whether you opened it. If yes, normal hydration is the likely explanation.
3. Ask whether a third-party app opened it. Reproduce the access with a controlled file.
4. Check whether it was newly created locally. If yes, it may never have been online-only.
5. Check available-offline state and team policy.
6. On macOS, confirm File Provider status.
7. Only then investigate unusual client behaviour.

Reinstalling Dropbox before this sequence destroys useful diagnostic context and may create new download work without proving the original cause.

Why selective sync solves a different problem

Dropbox often recommends selective sync when you do not want a folder synchronized to a particular computer at all.

That is different from online-only.

• Online-only: the item remains visible in the local Dropbox namespace and can download when accessed.
• Selective sync: the selected folder is removed from that computer's Dropbox folder while remaining in the Dropbox account online.

If a giant archive should never be visible to local applications on a particular machine, selective sync can reduce accidental access because the folder is not presented there in the same way.

If you need to browse the archive from the desktop and occasionally open files, online-only is the intended model.

Choosing the wrong mechanism is one reason users keep fighting the same disk-space problem.

Dropbox vs pCloud: the useful difference is architecture, not "zero local storage"

Dropbox is strong when you want one synchronized filesystem namespace where files can move between online-only and available-offline states. That model is convenient, mature, and entirely rational for many cross-platform workflows.

pCloud uses a somewhat different desktop model. pCloud documents pCloud Drive as a virtual drive for on-demand cloud access, while Sync is a separate feature that explicitly creates a local mirrored relationship.

For a user with a small SSD and a large mostly-cold archive, that separation can be easier to reason about:

• keep the archive in pCloud Drive;
• use Sync only for folders that genuinely need a permanent local working copy;
• make selected pCloud content available offline only when required.

That is a structural advantage for some storage-first workflows, but it is not magic. pCloud still uses local working data/cache when files are accessed, and offline files consume disk space. A virtual drive does not mean "zero local disk under all circumstances."

If your real requirement is Dropbox's collaboration, team workflow, or existing sharing ecosystem, switching providers just to avoid rehydration may create more friction than it removes.

If your real requirement is a multi-terabyte archive that should stay cloud-first while a much smaller working set stays local, the pCloud Drive/Sync separation is worth comparing.

Do not confuse cloud-first storage with backup

Making a file online-only does not create an additional independent backup. It changes where the active synchronized copy is stored.

If a file is deleted or corrupted and that change synchronizes to the cloud, your recovery depends on the provider's retained history and recovery controls. Use cloud backup vs cloud storage before treating online-only files as a resilience strategy.

For mass corruption or encryption, cloud-storage ransomware recovery is the next technical layer. For deleted-file retention, compare cloud deleted-file recovery windows.

This matters because many people move files online-only to solve SSD pressure and accidentally start thinking "the cloud has it, therefore I am backed up." Those are two separate decisions.

A safe fix sequence for a Dropbox folder that keeps growing locally

Use this order so you do not destroy unsynced work while chasing disk space.

1. Verify remote state first

Confirm important files exist on dropbox.com and that the desktop client is not reporting unfinished synchronization.

2. Identify the actual hydrated files

Use Dropbox status icons and filesystem size. Do not infer from a single top-level storage number.

3. Reproduce the trigger on one file

Open it deliberately, launch the suspected app, or repeat the workflow that caused the disk growth.

4. Decide whether the file should really be cloud-only

Active video projects, databases, large editing catalogs, and other frequently accessed working sets may simply need local space.

5. Make inactive content online-only

Only after confirming the cloud copy is complete.

6. Use selective sync if the folder should not appear on this computer at all

This prevents the local machine from presenting the whole folder as part of the active Dropbox namespace.

7. Reinstall only when the evidence points to a broken client state

Reinstallation is not a diagnostic substitute for identifying file access.

How to verify that you actually fixed the problem

A successful fix is not "the disk meter went down once."

Verify all four of these:

• the target archive files show as online-only;
• normal work does not unexpectedly hydrate unrelated files;
• files that you intentionally open become local in a predictable way;
• after returning inactive files online-only, the local storage remains stable over several normal work cycles.

If only files you actively use become local, Dropbox is behaving as designed.

If large unrelated folders repeatedly become available offline without any reproducible access path or policy change, document the exact affected paths, timestamps, OS version, Dropbox version, File Provider state, and sync status before escalating. That evidence is much more useful than "Dropbox keeps downloading everything."

The decision is not whether online-only works — it is whether the model matches your working set

Choose Dropbox online-only if you want the whole library visible in Dropbox, routinely open files from that namespace, and are comfortable with accessed files becoming local.

Use selective sync if a folder should not participate on a particular computer at all.

Consider pCloud Drive if the main problem is a very large storage-first archive and you prefer a clearer architectural separation between remote virtual-drive data and folders you explicitly choose to Sync locally.

Choose neither as your only backup if the files are irreplaceable.

Most people who keep repeating "make online-only → disk fills → make online-only again" do not have a checkbox problem. They have a working-set design problem. Once you decide which folders deserve permanent local bytes and which should remain archive-only, the correct provider and feature become much easier to choose.

Related reading

• How pCloud Drive cache actually works — understand why a virtual drive can still use some local storage.
• Google Drive streaming still uses disk space — compare another cloud-first model and its cache boundary.
• Cloud storage vs external hard drive — decide whether the archive should be remote, local, or both.

More reading

• Which cloud storage uses the least local disk space?
• Why OneDrive files download again after Free up space
• External hard drive to cloud: sync, backup, or upload?

Sources and verification

Product behaviour changes. We checked these primary sources on 21 August 2026:

1. Dropbox Help — How to use Dropbox to save hard drive space: online-only vs available offline, opening an online-only file downloads it, new-file defaults, and the local-file exception.
2. Dropbox Help — How to open online-only files on macOS: opening behaviour and third-party application requirements.
3. Dropbox Help — Support for Dropbox on File Provider: macOS File Provider integration and migration behaviour.
4. Dropbox Help — How to make a file or folder available offline in Dropbox: offline-state semantics.
5. pCloud Help — pCloud Drive vs (pCloud) Sync: virtual-drive versus mirrored local-folder model.

Internal-link map

Reverse internal-link suggestions for batch publish

Add a contextual link to this article from:

1. 002-dropbox-deleted-files-disk-space.md — where local disk use is caused by file state rather than deletion.
2. 004-dropbox-not-syncing.md — separate normal hydration from actual sync failure.
3. 014-cloud-storage-without-using-local-disk-space.md — link from the Dropbox online-only section.
4. 025-onedrive-files-keep-downloading-after-free-up-space.md — cross-provider hydration comparison.
5. 026-sync-external-hard-drive-cloud-storage.md — when locally ingested Dropbox content remains offline after upload.

Image metadata

Hero

• Purpose: show the state transition that creates the user's symptom.
• Filename: dropbox-online-only-download-again-hero.svg
• Alt: Dropbox online-only file state changing to a local copy after the file is opened or accessed by an application.
• Caption: Online-only is a current state. Access can legitimately hydrate the file again.
• Placement: after opening diagnosis.
• Source: CloudScope original technical diagram based on Dropbox documented behaviour.
• Dimensions: 1200 × 630.

Diagnostic tree

• Purpose: distinguish normal opening, application access, locally created files, offline policy, and unusual client behaviour.
• Filename: dropbox-online-only-rehydration-tree.svg
• Alt: Diagnostic decision tree for Dropbox files that become local after being set online-only.
• Caption: Diagnose the trigger before resetting the client.
• Placement: near the diagnostic-tree section.
• Source: CloudScope original technical diagram.
• Dimensions: 1200 × 760.

Architecture comparison

• Purpose: compare Dropbox state switching with pCloud Drive plus explicit Sync.
• Filename: dropbox-vs-pcloud-local-storage-model.svg
• Alt: Dropbox online-only and available-offline state model compared with pCloud Drive and separate Sync folders.
• Caption: Both services can reduce local storage, but the desktop architecture exposes the decision differently.
• Placement: Dropbox vs pCloud section.
• Source: CloudScope original technical diagram based on documented product models.
• Dimensions: 1200 × 760.

CTA specification

• Position: after Dropbox vs pCloud architecture analysis.
• Copy: See whether the storage model fits the archive →
• Destination: https://partner.pcloud.com/r/156919
• Plan Match: Plans & Pricing / General.
• Rel: sponsored noopener.
• Reason: reader is evaluating storage architecture, not yet a Lifetime, Family, Business, or Crypto-specific purchase.

Structured data and social metadata

• Schema: Article + BreadcrumbList.
• Canonical: https://cloudscope.org/articles/dropbox-online-only-files-download-again/
• OG title: Dropbox Online-Only Files Keep Downloading? Diagnose the Trigger
• OG description: Opening files, application access and local file creation can make Dropbox cloud-only content local again. Find the cause before resetting Dropbox.
• OG image: /assets/dropbox-online-only-download-again-hero.svg