OneDrive Files Keep Downloading After Free Up Space? Find What Is Rehydrating Them

Short answer: Free up space is not a permanent "never download this file again" rule. It changes the file's current hydration state back to online-only. Microsoft documents that an online-only file downloads again when you open it, and Windows can also let an application automatically download online-only files. A parent folder marked Always keep on this device, locally created files, or a broad Download all files setting can also put content back on disk.

The safest first move is therefore not to delete the file, unlink OneDrive, or reset the sync client. First check the file's status icon and identify what touched the file immediately before it became local again.

If you only remember one distinction from this article, make it this:

OneDrive being allowed to dehydrate a file is not the same thing as OneDrive being forbidden from hydrating it again.

That mental model explains most cases where people say "Free up space worked, then OneDrive downloaded everything again."

First confirm which state the file is actually in

Before troubleshooting, look at the OneDrive status icon in File Explorer.

Microsoft's current Files On-Demand model has three states that matter here:

The critical difference is between locally available and always available.

A locally available file may simply be a file you opened five minutes ago. It does not necessarily mean somebody deliberately pinned it. Microsoft says that opening an online-only file downloads it and makes it locally available. You can then right-click it and use Free up space again.

An always-available file is stronger. It was explicitly marked to stay on the device, and Storage Sense is not supposed to dehydrate files marked Always keep on this device.

If you are trying to recover SSD capacity safely, also read why deleting a OneDrive file is not the same thing as freeing local disk space. Delete changes cloud state and can propagate everywhere; Free up space changes local availability while keeping the cloud file.

The most common cause: something opened the file

The simplest explanation is also the one many users overlook.

Microsoft states that when you open an online-only file, OneDrive downloads it to the device and it becomes locally available. That is the normal design of Files On-Demand.

This can happen even when you did not consciously double-click the file in File Explorer.

Windows has a separate feature called Automatic file download notifications. Microsoft explains that some applications can automatically download online-only files. Its example is a media player downloading online-only music so the application can play it.

That creates a useful diagnostic clue:

1. You use Free up space.
2. The file shows the blue cloud icon.
3. Later, an application requests the file contents.
4. Windows allows the online-only file to download.
5. The file now shows as locally available and consumes local space again.

This is not necessarily a OneDrive sync failure. It can be a successful application read.

How to prove this branch

On Windows 10 or 11, watch for the Automatic file downloads notification. Microsoft says the notification identifies the source and shows download progress when an application automatically downloads cloud-only files.

If the same application appears every time the files return, you have evidence for the trigger instead of guessing.

Do not immediately block the application just because you found it. Microsoft warns that blocking automatic downloads can make an app unstable. First decide whether the application genuinely needs the file contents.

Examples where rehydration can be expected include:

• a media application that needs the full audio or video file;
• an editor opening a project asset;
• another program explicitly reading a cloud file rather than only listing its filename.

The deeper lesson is that an online-only filesystem entry can still be part of a live application workflow. If software repeatedly needs the bytes, fighting every re-download may be the wrong storage design.

Check whether a parent folder is pinned with Always keep on this device

The next high-probability cause is inheritance from the folder you are working inside.

Microsoft documents an important Files On-Demand behavior:

If you mark a folder as Always keep on this device, new files in that folder download to the device as always-available files.

That means checking one individual file is not enough.

Walk up the folder tree and inspect whether a parent OneDrive folder has been marked Always keep on this device.

A common failure pattern looks like this:

• Projects is pinned as Always keep.
• You use Free up space on an older subfolder.
• New files arrive in Projects from the cloud or another device.
• Because the parent is pinned, those new items are downloaded.
• Disk usage grows again and it looks as if Free up space was ignored.

The important distinction is that the old files may have been successfully dehydrated. The local disk is growing because new items are being hydrated under the folder's current availability policy.

Safest fix

If the folder does not actually need full offline availability:

1. confirm the cloud copy is complete on OneDrive.com;
2. right-click the relevant folder in File Explorer;
3. use Free up space instead of deleting the folder;
4. verify that the blue cloud status returns for files that should be online-only.

Do not use this procedure on files that exist only locally and have not finished syncing. If OneDrive is currently stuck or still uploading changes, resolve that first using the OneDrive Sync Pending diagnostic guide.

Files you create locally are local by default

Another misleading pattern is expecting every new OneDrive file to start as cloud-only.

Microsoft's current Files On-Demand documentation says that with the modern default behavior, new files from the cloud are online-only by default, but files created on the device are available offline by default.

That difference matters.

Suppose you keep a 500 GB project archive in OneDrive and periodically create new exports inside the OneDrive folder. Those exports originate on your computer. They are therefore already real local files before OneDrive uploads them.

Uploading them does not automatically mean Windows should immediately discard the local copy afterwards.

So if disk usage keeps rising because you are generating new files inside OneDrive, the problem is not that old cloud-only files were "randomly downloaded." You may simply be creating new local working data faster than you are dehydrating completed work.

A useful workflow is:

active project → keep local while editing

finished project → confirm upload → Free up space

cold archive → leave online-only until needed

That is much safer than repeatedly dehydrating files that your applications are still actively using.

If you are deciding whether a multi-terabyte archive should live inside the same active-work filesystem at all, compare the five major cloud models for minimizing local disk use.

Check whether OneDrive is set to Download all files

Microsoft has been changing the advanced Files On-Demand controls. Its current support page describes two broad choices for users with Files On-Demand enabled:

• Free up disk space — the recommended on-demand model;
• Download all files — effectively making the OneDrive content available locally, similar to applying Always keep on this device broadly.

If a large part of the library keeps appearing locally, inspect OneDrive's Files On-Demand setting before diagnosing individual files.

The exact interface can vary by current OneDrive build, Windows version, and organization policy, so the correct test is the resulting file state rather than relying only on a screenshot from an older support article.

After changing the setting, verify three things:

1. a test file that is not actively used can be made online-only;
2. it stays online-only while nothing accesses it;
3. opening it intentionally causes it to become local again.

If those three tests pass, Files On-Demand itself is behaving normally.

Storage Sense does not instantly remove every local OneDrive file

Some users expect Windows Storage Sense to act like an immediate cache purge. It does not.

Microsoft describes Storage Sense as a policy that can make inactive locally available cloud content online-only after a selected time period. On current Windows 11 documentation, OneDrive cloud files can be configured to become online-only after they have not been opened for a chosen period; files marked Always keep on this device are exempt.

Microsoft also states that Storage Sense operates on the system drive. If your cloud content is on another drive, do not assume the same automatic dehydration behavior will apply there.

That leads to two practical consequences:

1. Recently accessed files can legitimately stay local

If you opened a 20 GB video yesterday, Windows may keep it locally available until it crosses the inactivity threshold you configured.

2. Pinned files are intentionally excluded

If the folder is marked Always keep, turning Storage Sense on harder will not fix the policy conflict.

So the correct sequence is:

check pinning → identify access → configure Storage Sense → verify after the inactivity window

not:

Free up space → immediately assume OneDrive is broken if any local file later appears.

Known Folder Backup can make the problem feel random

OneDrive can back up common Windows folders such as Desktop, Documents, and Pictures. When that feature is enabled, files in those folders are part of the OneDrive-backed filesystem and can roam across devices.

This does not mean Known Folder Backup itself automatically downloads every file. The important interaction is that these are high-activity folders.

Applications constantly save documents, exports, screenshots, project files, and other working data into Desktop, Documents, or Pictures. Files created locally there are local by definition, and software that needs a cloud-only item may rehydrate it.

That is why a storage policy that works for a cold archive can behave very differently in Documents.

Do not turn off folder backup blindly

Microsoft's current "Back up your folders with OneDrive" workflow warns that stopping folder backup can involve choices about whether files remain in OneDrive or on the PC. Cloud-only files may need to be downloaded before some moves can complete.

If your problem is merely disk pressure, do not disable Known Folder Backup as a first troubleshooting step.

Instead:

1. determine whether the files are active working files or old archive data;
2. move long-term archive content only after confirming its cloud state and intended destination;
3. keep the backup setting intact until you understand what will happen to Desktop/Documents/Pictures.

For a broader distinction between protecting arbitrary local folders and ordinary sync behavior, see cloud backup folders outside a sync folder.

What not to do when OneDrive keeps filling the SSD

Several common "fixes" can create more risk than the original disk-space problem.

Do not delete files just to make them disappear locally

A synced delete is a cloud change. It can propagate to OneDrive and other devices. If your goal is local-space reclamation, use Free up space, not Delete. The difference is explained in why a OneDrive delete can remove the file everywhere.

Do not reset or reinstall OneDrive before proving the client is broken

If files rehydrate because an application opens them, reinstalling OneDrive will not remove that application requirement.

A reset is appropriate only after you have evidence that sync state is malfunctioning, not because the product successfully downloaded a file somebody requested.

Do not clear local state while unsynced work may exist

If a local file has changes that are still pending upload, aggressive cache/state cleanup can turn a storage problem into a data-loss investigation.

Do not assume cloud-only means zero disk usage forever

Cloud-on-demand systems still need local resources when you actually use remote content. This is not unique to OneDrive.

Google Drive Stream uses a content cache for files you work on and for recently/frequently used content. Dropbox online-only files download when opened. iCloud Drive can remove a local download but will download content again when the Mac needs it. pCloud Drive is a virtual drive but also uses a configurable local cache during access and transfers.

The practical comparison is therefore how clearly each service separates remote archive, local working data, and offline pinning — not whether any provider can promise literal zero-byte local use.

How the Big 5 handle the same local-space problem

The table exposes an important decision point.

If your archive is only occasionally opened, OneDrive Files On-Demand can work very well. If the same archive sits inside folders that applications continually scan, edit, render, or export from, repeated hydration may be the expected consequence of using the archive as a live working filesystem.

Why pCloud can feel different without pretending it uses zero local disk

pCloud's structural advantage for this specific problem is not magic compression and it is not "no cache."

pCloud documents two deliberately separate desktop concepts:

• pCloud Drive — a virtual drive for cloud-first access;
• Sync — a two-way mirrored relationship when you intentionally want a local folder copy.

That separation can be useful if your real frustration with OneDrive is not a bug but a mixed storage model: the same OneDrive-backed filesystem is being asked to be a cold archive, a live workspace, an offline library, and a Windows backup target at the same time.

With pCloud, a cleaner architecture can be:

pCloud Drive → multi-terabyte archive you normally leave remote

Sync → selected active folders that genuinely need an always-local working copy

local-only scratch space → render cache, temporary exports, or application working files that should not be treated as the archive itself

But there is a caveat CloudScope will not hide: pCloud Drive still uses local cache when files are opened or transferred. pCloud's current settings documentation describes configurable cache and minimum free-space requirements, and its low-disk-space support page specifically explains that copy/paste uploads can use temporary local cache.

So switching providers does not repeal physics. A 40 GB remote video still needs local working space if your editor needs the whole 40 GB file.

The actual advantage is role separation, not zero disk use.

For the technical details, read how pCloud Drive cache actually works before assuming a virtual drive means no SSD impact.

When you should stay with OneDrive

Do not migrate just because files occasionally rehydrate.

Stay with OneDrive if:

• Microsoft 365 is already central to your workflow;
• Word, Excel, Teams, SharePoint, and Windows integration save more time than the local-space behavior costs;
• most files become local because you actually use them frequently;
• Storage Sense and a clear Always-keep policy are enough to control disk usage;
• the archive is not large enough to justify another storage layer.

In those cases, repeated hydration is often a workload signal, not a provider failure.

You may get more value from separating finished projects from active folders than from changing cloud providers.

If your OneDrive account is also close to its cloud quota, diagnose that separately. Local SSD usage and cloud quota are different failure domains; what happens when cloud storage is full explains why mixing those two symptoms leads to bad fixes.

When a storage-first model deserves a serious comparison

Some users reach this article because they are already fighting the same pattern every month:

• a 512 GB laptop;
• a 2–5 TB photo/video/project archive;
• old files that are rarely needed;
• applications that keep touching content inside the main cloud folder;
• constant manual Free up space cleanup.

If that description feels familiar, the unfinished decision is not "How do I click Free up space more often?"

It is:

Should the archive still live inside the same filesystem that your daily applications treat as active working storage?

OneDrive can remain the better choice when Microsoft integration is the point. But if the archive itself is the product — large files, cross-platform access, long retention, less dependence on an office suite — pCloud's virtual-drive-plus-selective-Sync model is worth comparing as a different storage architecture.

Affiliate link. This is a general pCloud plan comparison, not a claim that switching providers will eliminate all local cache use.

A safe diagnostic sequence before you change anything

Use this order because it protects data and isolates the trigger:

1. Verify the cloud copy exists on OneDrive.com.
2. Check the status icon: online-only, locally available, or always available.
3. Inspect parent folders for Always keep on this device.
4. Use Free up space on one test file that you know is safely uploaded.
5. Do nothing with that file for several minutes and confirm it remains online-only.
6. Open the file intentionally and confirm it becomes local. That proves basic Files On-Demand hydration is working.
7. Repeat with the real problem file and watch for Automatic file download notifications or a specific application access pattern.
8. Check Storage Sense only after pinning and app access have been understood.
9. Avoid reset/reinstall unless the state transitions themselves are failing.
10. If the workload inherently requires repeated full-file access, redesign where active files and archive files live.

That sequence distinguishes a real OneDrive fault from expected Files On-Demand behavior without putting unsynced data at risk.

Related reading

• Google Drive Stream still uses local disk space — useful if you are considering Google's streaming model as an alternative.
• Why iCloud Optimize Storage can still leave files on your Mac — the Apple version of the same cloud-first/local-cache misunderstanding.
• Cloud storage vs external hard drive — use this if the archive may not belong in an always-connected cloud filesystem at all.

More reading

• Can cloud storage protect against ransomware? — understand why sync state and recovery state are separate problems.
• Cloud storage without using local disk space — compare Dropbox, Google Drive, iCloud, OneDrive, and pCloud directly.
• pCloud Drive cache explained — see where virtual-drive cache still uses SSD space.

Sources and verification

Product behavior can change by operating system, OneDrive build, administrator policy, and cloud-provider client version. Material claims in this draft were checked against current primary documentation on 21 August 2026.

1. 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

1. Microsoft Support — Automatic file download notifications in Windows

https://support.microsoft.com/en-us/windows/experience/automatic-file-download-notifications-in-windows

1. Microsoft Support — Manage drive space with Storage Sense

https://support.microsoft.com/en-us/windows/experience/storage-filemanagement/manage-drive-space-with-storage-sense

1. Microsoft Support — Back up your folders with OneDrive

https://support.microsoft.com/en-us/onedrive/back-up-your-folders-with-onedrive

1. Dropbox Help — Free Up Space with Online-Only Files

https://help.dropbox.com/sync/make-files-online-only

1. Google Drive Help — Stream & mirror files with Drive for desktop

https://support.google.com/drive/answer/13401938

1. Google Drive Help — Customize Drive for desktop settings / content cache

https://support.google.com/drive/answer/13470231

1. Apple Support — Work with folders and files in iCloud Drive

https://support.apple.com/guide/mac-help/mchl1a02d711/mac

1. pCloud Help — pCloud Drive vs (pCloud) Sync

https://help.pcloud.com/article/pcloud-drive-vs-pcloud-sync

1. pCloud Help — Low disk space warning in pCloud Drive

https://help.pcloud.com/article/low-disk-space-warning-in-pcloud-drive

<!-- DRAFT PRODUCTION NOTES

Article fingerprint

• Primary question: Why do OneDrive files become local again after the user runs Free up space?
• Unique angle: Treat re-download as a hydration-trigger investigation, not a generic sync failure.
• Why this page deserves to exist: Existing #001 explains deletion propagation, #005 covers Sync Pending, and #014 compares local-disk models. This page diagnoses the distinct state transition "online-only -> local again" and identifies app-triggered automatic downloads, folder pinning, local creation, and Storage Sense policy.
• Main trade-off: OneDrive's deep Windows/app integration is useful for active work but can make a cold archive rehydrate more often than a storage-first virtual-drive workflow.
• Commercial exit: General pCloud Plans & Pricing, not Lifetime/Crypto/Business/Family.

Internal link map

1. "why deleting a OneDrive file is not the same thing as freeing local disk space" -> /articles/onedrive-delete-file-everywhere/ -> early diagnostic -> horizontal
2. "OneDrive Sync Pending diagnostic guide" -> /articles/onedrive-sync-pending/ -> before destructive changes -> horizontal
3. "five major cloud models for minimizing local disk use" -> /articles/cloud-storage-without-using-local-disk-space/ -> model comparison -> down
4. "cloud backup folders outside a sync folder" -> /articles/cloud-backup-folders-outside-sync-folder/ -> Known Folder Backup context -> horizontal
5. "how pCloud Drive cache actually works" -> /articles/pcloud-drive-cache-explained/ -> pCloud caveat -> down
6. "what happens when cloud storage is full" -> /articles/what-happens-when-cloud-storage-is-full/ -> separate quota failure domain -> horizontal
7. "Google Drive Stream still uses local disk space" -> /articles/google-drive-streaming-uses-disk-space/ -> paired reading -> horizontal
8. "Why iCloud Optimize Storage can still leave files on your Mac" -> /articles/icloud-drive-optimize-mac-storage-disk-space/ -> paired reading -> horizontal
9. "Cloud storage vs external hard drive" -> /articles/cloud-storage-vs-external-hard-drive/ -> storage architecture -> up
10. "Can cloud storage protect against ransomware?" -> /articles/can-cloud-storage-protect-against-ransomware/ -> more reading -> horizontal

Reverse-link suggestions for batch wiring

• 001-onedrive-delete-file-everywhere.md: link from Free up space section to this hydration guide.
• 005-onedrive-sync-pending.md: link from local disk / Files On-Demand branch to this guide.
• 014-cloud-storage-without-using-local-disk-space.md: link OneDrive Files On-Demand paragraph to this troubleshooting page.
• 019-cloud-backup-folders-outside-sync-folder.md: link Known Folder Backup discussion to this page.
• existing pcloud-drive-cache-explained: link OneDrive comparison sentence to this page if context supports it.

Images

1. /draft-assets/onedrive-files-download-again-hero.svg

Purpose: Hero explaining online-only -> access/app -> local hydration -> Free up space loop. Placement: After opening diagnostic distinction. Alt: OneDrive Files On-Demand flow showing an online-only file becoming local again after an application accesses it. Caption: Free up space changes the current local state; later access can hydrate the file again. Source: Original conceptual diagram based on Microsoft Files On-Demand documentation. Format: SVG Dimensions: 1200x630

1. /draft-assets/onedrive-rehydration-diagnostic-tree.svg

Purpose: Diagnostic decision tree for pinning, app access, local creation, and Storage Sense. Placement: After application-trigger section. Alt: Decision tree for diagnosing why OneDrive files download again after Free up space. Caption: Diagnose the trigger before resetting OneDrive. Source: Original editorial diagram derived from cited Microsoft documentation. Format: SVG Dimensions: 1200x760

1. /draft-assets/onedrive-vs-pcloud-local-storage-model.svg

Purpose: Compare OneDrive Files On-Demand with pCloud Drive + Sync role separation. Placement: pCloud comparison section. Alt: Architecture comparison of OneDrive Files On-Demand and pCloud Drive with separate Sync folders. Caption: Both use local storage when data is accessed; pCloud separates virtual-drive access from intentionally mirrored Sync folders. Source: Original editorial diagram based on Microsoft and pCloud documentation. Format: SVG Dimensions: 1200x760

CTA

• Position: Late article, after stay-with-OneDrive criteria and before final diagnostic sequence.
• Copy: "Check whether pCloud's storage-first layout matches the part of your OneDrive workflow that keeps rehydrating →"
• Destination: https://partner.pcloud.com/r/156919
• Plan Match: Plans & Pricing
• Attribute: rel="sponsored noopener"

SEO / publishing

• Structured data: Article + BreadcrumbList
• Self-canonical: https://cloudscope.org/articles/onedrive-files-keep-downloading-after-free-up-space/
• OG title: OneDrive Files Keep Downloading After Free Up Space? Find the Trigger
• OG description: Diagnose why Files On-Demand files rehydrate after Free up space, including app-triggered downloads, Always keep folders, local creation, and Storage Sense behavior.
• OG image: /assets/onedrive-files-download-again-hero.svg
• Publication state for this batch: keep DRAFT until batch 50/50 wiring + QA.

-->